After the upgrade 3.0 can not open all the VMDK

[bd5hty]

kvm: -drive file=/var/lib/vz/images/137/vm-137-disk-2.vmdk,if=none,id=drive-virtio1,format=vmdk,aio=native,cache=none: could not open disk image /var/lib/vz/images/137/vm-137-disk-2.vmdk: not in vmdk format
TASK ERROR: start failed: command '/usr/bin/kvm -id 137 -chardev 'socket,id=qmp,path=/var/run/qemu-server/137.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/137.vnc,x509,password -pidfile /var/run/qemu-server/137.pid -daemonize -name 122.225.196.174 -smp 'sockets=1,cores=2' -cpu host -nodefaults -boot 'menu=on' -vga cirrus -k en-us -m 2048 -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=/var/lib/vz/images/137/vm-137-disk-2.vmdk,if=none,id=drive-virtio1,format=vmdk,aio=native,cache=none' -device 'virtio-blk-pci,drive=drive-virtio1,id=virtio1,bus=pci.0,addr=0xb' -drive 'file=/mnt/pve/xtemplates/template/iso/CactiEZ-10.1-x86_64.iso,if=none,id=drive-ide2,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -drive 'file=/var/lib/vz/images/137/vm-137-disk-1.vmdk,if=none,id=drive-virtio0,format=vmdk,aio=native,cache=none' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=101' -netdev 'type=tap,id=net0,ifname=tap137i0,script=/var/lib/qemu-server/pve-bridge' -device 'e1000,mac=C22:B0:F0:44B,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -rtc 'driftfix=slew,base=localtime'' failed: exit code

pve-manager: 3.0-23 (pve-manager/3.0/957f0862)
running kernel: 2.6.32-20-pve
proxmox-ve-2.6.32: 3.0-100
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-18-pve: 2.6.32-88
lvm2: 2.02.95-pve3
clvm: 2.02.95-pve3
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-1
pve-cluster: 3.0-4
qemu-server: 3.0-20
pve-firmware: 1.0-22
libpve-common-perl: 3.0-4
libpve-access-control: 3.0-4
libpve-storage-perl: 3.0-8
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-13
ksm-control-daemon: 1.1-1

 

[bd5hty]

All transfers from VMware can not start over. Other RAW, QCOW2 are normal, the new VMDK also normal!

 

[bd5hty]

# file vm-136-disk-1.vmdkvm-136-disk-1.vmdk: x86 boot sector, Microsoft Windows XP MBR, Serial 0x48174817; partition 1: ID=0x7, active, starthead 1, startsector 63, 31455207 sectors, code offset 0xc0

 

[Beastie]

I had the same problem I have a temporarily fix by starting it manually adapting a parameter.
When I did

qemu-img info /var/lib/vz/images/3004/vm-3004-disk-1.vmdk

I got in the info that it was actually raw format according to the info
see output below

image: /var/lib/vz/images/3004/vm-3004-disk-1.vmdk
file format: raw
virtual size: 40G (42949672960 bytes)
disk size: 15G

so I tried to start on the console with qm start 3004 copied the command and replaced format=vmdk with format=raw and it booted.

I adapted /etc/pve/nodes/<servername>/qemu-server/3004.conf and changed there the vmdk to raw and now it boots again from the interface.

it's not a nice fix but I needed to get the machine up quickly so for now I'm saved.

kind regards
Joan Lavrijs

 

[bd5hty]

I had the same problem I have a temporarily fix by starting it manually adapting a parameter.
When I did

qemu-img info /var/lib/vz/images/3004/vm-3004-disk-1.vmdk

I got in the info that it was actually raw format according to the info
see output below

image: /var/lib/vz/images/3004/vm-3004-disk-1.vmdk
file format: raw
virtual size: 40G (42949672960 bytes)
disk size: 15G

so I tried to start on the console with qm start 3004 copied the command and replaced format=vmdk with format=raw and it booted.

I adapted /etc/pve/nodes/<servername>/qemu-server/3004.conf and changed there the vmdk to raw and now it boots again from the interface.

it's not a nice fix but I needed to get the machine up quickly so for now I'm saved.

kind regards
Joan Lavrijs

Sorry. Can you elaborate? My English is not very good.

 

[bd5hty]

I had the same problem I have a temporarily fix by starting it manually adapting a parameter.
When I did

qemu-img info /var/lib/vz/images/3004/vm-3004-disk-1.vmdk

I got in the info that it was actually raw format according to the info
see output below

image: /var/lib/vz/images/3004/vm-3004-disk-1.vmdk
file format: raw
virtual size: 40G (42949672960 bytes)
disk size: 15G

so I tried to start on the console with qm start 3004 copied the command and replaced format=vmdk with format=raw and it booted.

I adapted /etc/pve/nodes/<servername>/qemu-server/3004.conf and changed there the vmdk to raw and now it boots again from the interface.

it's not a nice fix but I needed to get the machine up quickly so for now I'm saved.

kind regards
Joan Lavrijs

OK, very grateful! Have the opportunity to come to China to play, ha ha!

 

[Beastie]

Sorry. Can you elaborate? My English is not very good.

use an editor like vi or nano
open /etc/pve/nodes/<servername>/qemu-server/<id of server>.conf
change vmdk to raw
save it
it will work

 

[Beastie]

been there before ... who knows