Search results

Can't risk a list-upgrade at this point, so i went with apt-get install --only-upgrade pve-qemu-kvm and voila, it worked. Thanks a million for your kind help.

Nope. I've just upgraded PVE through apt-get. How can I force an upgrade of that particular package?

root@ns428897:~# pveversion -v proxmox-ve-2.6.32: 3.3-139 (running kernel: 2.6.32-34-pve) pve-manager: 3.3-5 (running version: 3.3-5/bfebec03) pve-kernel-2.6.32-29-pve: 2.6.32-126 pve-kernel-2.6.32-34-pve: 2.6.32-140 pve-kernel-2.6.32-26-pve: 2.6.32-114 lvm2: 2.02.98-pve4 clvm: 2.02.98-pve4...

Interestingly, the volume is actually mounted and (apparently) populated, but then vanishes when the task is aborted.

After upgrading PVE to 3.3, I am still facing the same issue. Here's the verbose it spews.

root@ns428897:~# qm start 111 kvm: -drive file=/var/lib/vz/images/111/vm-111-disk-1.qcow2,if=none,id=drive-ide1,format=qcow2,cache=writethrough,aio=native,detect-zeroes=on: could not open disk image /var/lib/vz/images/111/vm-111-disk-1.qcow2: Block format 'qcow2' used by device 'drive-ide1'...

After upgrading from PVE 3.2 to 3,3, my KVM guests ceased to boot. Tried a few suggestions fond on a few related threads, but none really worked for me. The task error message reads as follows: TASK ERROR: start failed: command '/usr/bin/kvm -id 111 -chardev...

vzdump is apparently unable to mount the LVM snapshot. The lvm snapshot is successfully created under /dev/mapper/pve-data, but then it is not mounted on /mnt/vzsnap0/102. This error effectively prevents the backup from being generated and sent to the storage device. Any options other than...

My physical server has one single NIC, currently holding the "public" IP address in the context of the LAN. The device is identified as eth0 and has the following settings to allow routed networking: auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.0.7 netmask...

Trying to set up a bridged connection from the web GUI alone is proving to be a daunting task. The newly created device, name eth0, shows up under the Network tab, but is nowhere to be found in the container itself. root@dzerzhinsky:/# ifconfig lo Link encap:Local Loopback...

Well observed :) What a silly oversight of me.

Although there is a wealth of threads dealing wit this topic, none I've found seems to address the specificities of my case. Proxmox 3 has been successfully installed on my HP Proliant Microserver N54L and it can be pinged from my laptop in the same LAN. Moreover, I can telnet port 8006, ssh...