Search results

  1. A

    Backus to an /backup Directory not working

    It's not easy to read your pveverion -v, as each program is not displayed on its own line, as it appears in a console... Nevertheless, I see this : vzprocps: not correctly installed ksm-control-daemon: not correctly installed And, as tom said, postfix should be installed by default. So, there...
  2. A

    Backus to an /backup Directory not working

    Can you post your pveversion -v ? It works for me... did you use the button 'Backup now' ? you have postfix errors... Alain
  3. A

    Insufficient free extents (0) in volume group pve: 256 required: can't solve this ?

    Re: Insufficient free extents (0) in volume group pve: 256 required: can't solve this Meanwhile, you can do your backup by stopping your VM : vzdump --stop .... Alain
  4. A

    Insufficient free extents (0) in volume group pve: 256 required: can't solve this ?

    Re: Insufficient free extents (0) in volume group pve: 256 required: can't solve this Hi, It seems that there is no free space to do a snapshot : Free PE / Size 0 / 0 I would bet that it is not a standard proxmox-ve installation (with the CD), but an installation on top of squeeze...
  5. A

    Proxmox 1.9 & NIC bnx2

    Hi Tom, It is nevertheless worrying, due to the delay of PVE 2.0 (stable in Q1 2012 ?). Squeeze has been released on February 6th, 2011. I hope to be able to upgrade to 2.0 before the end of Lenny support, or that a 1.x (1.10 ?) version with squeeze will be available at that time... Alain
  6. A

    VirtIO Win2003 warnings, errors, reboots

    Hi Fortechit, Sorry for the delay of my answer. As noted by linum, you say you are using 1.9, but the version shows 1.8. Is it an error ? And as you said, boot disk seems to be IDE, not virtio. Did you verify ? Also, I note that you use kernel 2.6.35, it is also my case. I had a look at...
  7. A

    VirtIO Win2003 warnings, errors, reboots

    Hi, Could you post exactly which Proxmox-ve version you use (pveversion -v) ? I run myself several 2003 R2 (and 2008 R2) with virtio drivers, and have no problem... Could you post also at least one of your VM configuration (in /etc/qemu-server), to see which configuration they have ? Alain
  8. A

    qmrestore problem

    Yes, and build your own snapshot first (otherwise your VM will change during your backup...)
  9. A

    qmrestore problem

    Hi, I thought it was not implemented via web interface, but available through CLI, but it is not the case : # which vzdump /usr/sbin/vzdump # vzdump --snapshot --storage lx-ape2 --maxfiles 1 101 Undefined subroutine &PVE::Storage::load_config called at /usr/share/perl5/PVE/VZDump.pm line...
  10. A

    Active Directory Authentication

    Hi all, I just set up a little test server with Proxmox 2.0 beta. In the announcement, it is said that the new Web GUI supports MS ADS authentication. I have an Active Directory Domain, and would like to use this authentication. But I don't see anywhere in the Web GUI (authentication Tab ?)...
  11. A

    Proxmox VE 2.0 beta released!

    Hi Zatmania, Remember it is a beta version, not ready for production. It would not be advisable to upgrade a production system to Proxmox 2.0 beta. If your Proxmox 1.9 is a test machine, it is possible to backup your VMs, and reinstall from scratch with 2.0... Just my advice. Alain
  12. A

    Roadmap for Proxmox VE 2.0

    It should. See post #15. Alain
  13. A

    Updated Fedora Windows guest drivers available

    Hi Biagio, I can only say that I am now using exclusively the latest virtio-win drivers, that is virtio-win-0.1-mm34.iso, signed by RedHat, on my windows VMs (2008 R2). I use them for networking, and also for storage, but not for C: (I stick currently with IDE because for me performance is...
  14. A

    Proxmox crash

    Hi, Is it a problem with KSM ? Aug 31 18:50:55 vps5 kernel: BUG: unable to handle kernel paging request at 0000000000002438 ... Aug 31 18:50:55 vps5 kernel: last sysfs file: /sys/kernel/mm/ksm/run I am also running 4 pve hosts with 2.6.35-1 kernel without problem, but, as they don't use more...
  15. A

    IP Address for fully virtualized (KVM)

    Yes, I think you are right, a simple ifup vmbr1 should suffice... Is your second interface, eth1, in the same VLAN as the first ? I would try to give vmbr1 an IP address, just for test, and try to ping it, just to be sure it is reachable on your network...
  16. A

    IP Address for fully virtualized (KVM)

    It seems correct to me, but does it appears in the Proxmox web interface ? I think it will be better to remove your manual configuration, and configure this second bridge through the web interface, as it is explained in this video tutorial ...
  17. A

    IP Address for fully virtualized (KVM)

    It should work. What do you see if you type : # ifconfig vmbr1 # brctl show I found this reference : http://www.faqs.org/docs/Linux-HOWTO/BRIDGE-STP-HOWTO.html#BRCTL-SYNOPSIS
  18. A

    IP Address for fully virtualized (KVM)

    That's OK. I suppose you restarted the host network after configuring the bridge ? Do you see messages in your logs concerning this bridge or other network errors ?
  19. A

    IP Address for fully virtualized (KVM)

    So you are using the second interface, eth1, for the bridge, and not the first, eth0 ? Did you associate your VM interface with this bridge, and not vmbr0 ? It should appear in the web interface, I suppose (never did it). Alain
  20. A

    IP Address for fully virtualized (KVM)

    Hi, Just configure an IP address as you would do with a real physical machine. The Proxmox ve host is configured as a bridge (br0, using eth0), that is like a switch, so your KVM VM machine will be seen on your LAN as would be any other machine... There is no NAT, as it is the case by default...