after a power outage we decided it would be a good time to update the server, we've been having some issues though.
I use .vmdk's as personal hard drives, these are stored on an NTFS nas box, this has been working up until the update. the web interface gives me the error "Error: unexpected status" when i manually use qm start (vmid) i get this error:
"kvm: -drive file=/root/CloudStorage/images/101/mark@something.com.vmdk,if=none,id=drive-ide1,aio=native,cache=none: could not open disk image /root/CloudStorage/images/101/mark@something.com.vmdk: Invalid argument
start failed: command '/usr/bin/kvm -id 107 -chardev 'socket,id=qmp,path=/var/run/qemu-server/107.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/107.vnc,x509,password -pidfile /var/run/qemu-server/107.pid -daemonize -name vm107 -smp 'sockets=1,cores=2' -nodefaults -boot 'menu=on' -vga std -no-hpet -k en-us -m 4096 -cpuunits 1000 -vnc :7,password -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -drive 'file=/root/CloudStorage/images/101/mark@something.com.vmdk,if=none,id=drive-ide1,aio=native,cache=none' -device 'ide-hd,bus=ide.0,unit=1,drive=drive-ide1,id=ide1' -drive 'file=/var/lib/vz/images/103/vm-103-disk-1.qcow2,if=none,id=drive-ide0,snapshot=on,aio=native,cache=none' -device 'ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=101' -netdev 'type=tap,id=net0,ifname=tap107i0,script=/var/lib/qemu-server/pve-bridge' -device 'rtl8139,mac=DA:B0:8A:EB:A4:FB,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -rtc 'driftfix=slew,base=localtime' -global 'kvm-pit.lost_tick_policy=discard'' failed: exit code 1 "
when I copied the .vmdk to the "local" storage (/var/lib/vz/images/107/mark@something.com.vmdk) and used that as my second hard drive it started just fine.
my network routing is no longer working either but that's a bit more confusing
here is my info i believe it was PVE 2.1 before the update
pveversion -v
pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-19-pve
proxmox-ve-2.6.32: 2.3-95
pve-kernel-2.6.32-19-pve: 2.6.32-95
pve-kernel-2.6.32-6-pve: 2.6.32-55
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-20
pve-firmware: 1.0-21
libpve-common-perl: 1.0-49
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-7
vncterm: 1.0-4
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-10
ksm-control-daemon: 1.1-1
I use .vmdk's as personal hard drives, these are stored on an NTFS nas box, this has been working up until the update. the web interface gives me the error "Error: unexpected status" when i manually use qm start (vmid) i get this error:
"kvm: -drive file=/root/CloudStorage/images/101/mark@something.com.vmdk,if=none,id=drive-ide1,aio=native,cache=none: could not open disk image /root/CloudStorage/images/101/mark@something.com.vmdk: Invalid argument
start failed: command '/usr/bin/kvm -id 107 -chardev 'socket,id=qmp,path=/var/run/qemu-server/107.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/107.vnc,x509,password -pidfile /var/run/qemu-server/107.pid -daemonize -name vm107 -smp 'sockets=1,cores=2' -nodefaults -boot 'menu=on' -vga std -no-hpet -k en-us -m 4096 -cpuunits 1000 -vnc :7,password -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -drive 'file=/root/CloudStorage/images/101/mark@something.com.vmdk,if=none,id=drive-ide1,aio=native,cache=none' -device 'ide-hd,bus=ide.0,unit=1,drive=drive-ide1,id=ide1' -drive 'file=/var/lib/vz/images/103/vm-103-disk-1.qcow2,if=none,id=drive-ide0,snapshot=on,aio=native,cache=none' -device 'ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=101' -netdev 'type=tap,id=net0,ifname=tap107i0,script=/var/lib/qemu-server/pve-bridge' -device 'rtl8139,mac=DA:B0:8A:EB:A4:FB,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -rtc 'driftfix=slew,base=localtime' -global 'kvm-pit.lost_tick_policy=discard'' failed: exit code 1 "
when I copied the .vmdk to the "local" storage (/var/lib/vz/images/107/mark@something.com.vmdk) and used that as my second hard drive it started just fine.
my network routing is no longer working either but that's a bit more confusing
here is my info i believe it was PVE 2.1 before the update
pveversion -v
pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-19-pve
proxmox-ve-2.6.32: 2.3-95
pve-kernel-2.6.32-19-pve: 2.6.32-95
pve-kernel-2.6.32-6-pve: 2.6.32-55
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-20
pve-firmware: 1.0-21
libpve-common-perl: 1.0-49
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-7
vncterm: 1.0-4
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-10
ksm-control-daemon: 1.1-1
Last edited:
