vms with vmdk disk format wont start

[soomon]

hi all,

i am totally new to proxmox, but it looks quite easy.
i tried to create a vm with a vmdk file, but it won't start.
raw and qcow2 work fine.

/usr/sbin/qm start 106
qemu: could not open disk image /var/lib/vz/images/106/vm-106-disk-1.vmdk
start failed: command '/usr/bin/kvm -monitor unix:/var/run/qemu-server/106.mon,server,nowait -vnc unix:/var/run/qemu-server/106.vnc,password -pidfile /var/run/qemu-server/106.pid -daemonize -usbdevice tablet -name test4 -smp 1 -vga cirrus -tdf -k de -drive file=/var/lib/vz/template/iso/ubuntu-10.04-desktop-amd64.iso,if=ide,index=2,media=cdrom -drive file=/var/lib/vz/images/106/vm-106-disk-1.vmdk,if=virtio,index=0,boot=on -m 2048 -net tap,vlan=0,ifname=vmtab106i0,script=/var/lib/qemu-server/bridge-vlan -net nic,vlan=0,model=rtl8139,macaddr=EA:60:72:5B:09:CA' failed with exit code 1
VM 106 start failed -

the file exists...

what's the difference anyway?

thanks & greets,
soomon

 

[dietmar]

How do you create that vmdk file?

 

[Mrdude]

What kernel are you running?
with Kernel 2.6.18 i was not able to start vmdk files but when i updated the Kernel to 2.6.24 or 2.6.32 the same vmdk files started up with no problems.

Hope that helps,

 

[iprigger]

Hi All,

@Dietmar: Same problem here:

syslog:May 12 10:21:58 oestersund qm[30447]: VM 400 start failed: command '/usr/bin/kvm -monitor unix:/var/run/qemu-server/400.mon,server,nowait -vnc unix:/var/run/qemu-server/400.vnc,password -pidfile /var/run/qemu-server/400.pid -daemonize -usbdevice tablet -name quality -smp 2 -boot c -vga cirrus -tdf -localtime -rtc-td-hack -k de-ch -drive file=/mnt/pve/qemudsk/images/400/quality.auditq.com.vmdk,if=ide,index=0,boot=on -m 768 -net tap,vlan=0,ifname=vmtab400i0,script=/var/lib/qemu-server/bridge-vlan -net nic,vlan=0,model=virtio,macaddr=EE5:C4:EC:5F:A8' failed with exit code 1

Fun thing is: I have two servers running both kernel 2.6.24-10-pve, one corei7 860, one coirei7 930. Both set up from the same disk. On the one server it's running with VMDKs, too - on the other it isn't.

No idea why.

Not that it's tragic (I wanted to migrate the images to qcow2 anyways) but I'd like to know why this happens...

That's all
Thanks!

Tobias

 

[udo]

Hi Tobias,
i think there are differences between the vmdk-files? Can you test the running vmdk-file on the non-running server?

Udo

 

[iprigger]

Hi Udo,

Hi Tobias,
i think there are differences between the vmdk-files? Can you test the running vmdk-file on the non-running server?

Udo

The named file runs fine on the other server...

I have a cluster with 2 systems running... on machine 1 it runs fine, on machine 2 it produces the posted error. No idea why.

Server it runs:
pve-manager/1.5/4674
Linux 2.6.24-10-pve #1 SMP PREEMPT Tue Dec 29 10:16:15 CET 2009

Server it isn't running:
pve-manager/1.5/4674
Linux 2.6.24-10-pve #1 SMP PREEMPT Tue Dec 29 10:16:15 CET 2009

Additional Info: The VMDK File lies on an NFS Store - so it's not being copied between tries. It IS the absolute identical file.

CU
Tobias

 

[tom]

compare the output of 'pveversion -v' from both servers - any difference?

 

[iprigger]

Hi Tom,

compare the output of 'pveversion -v' from both servers - any difference?

Here you are:

stockholm:~# pveversion -v
pve-manager: 1.5-8 (pve-manager/1.5/4674)
running kernel: 2.6.24-10-pve
proxmox-ve-2.6.24: 1.5-21
pve-kernel-2.6.24-10-pve: 2.6.24-21
pve-kernel-2.6.18-1-pve: 2.6.18-4
qemu-server: 1.1-11
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-10
vncterm: 0.9-2
vzctl: 3.0.23-1pve8
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.11.1-2

stockholm:~# cat /etc/apt/sources.list
deb http://ftp.ch.debian.org/debian lenny main contrib

# PVE packages provided by proxmox.com
deb http://download.proxmox.com/debian lenny pve

# security updates
deb http://security.debian.org/ lenny/updates main contrib


oestersund:~# pveversion -v
pve-manager: 1.5-8 (pve-manager/1.5/4674)
running kernel: 2.6.24-10-pve
proxmox-ve-2.6.18: 1.5-5
pve-kernel-2.6.24-10-pve: 2.6.24-21
pve-kernel-2.6.18-2-pve: 2.6.18-5
qemu-server: 1.1-11
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-10
vncterm: 0.9-2
vzctl: 3.0.23-1pve8
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm-2.6.18: 0.9.1-5

oestersund:~# cat /etc/apt/sources.list
deb http://ftp.ch.debian.org/debian lenny main contrib

# PVE packages provided by proxmox.com
deb http://download.proxmox.com/debian lenny pve

# security updates
deb http://security.debian.org/ lenny/updates main contrib

on stockholm it's working - on oestersund it isn't.

I have posted the /etc/apt/sources.list because I just saw there is a difference - and have no idea where this comes from...

if I run apt-get update && apt-get upgrade it doesn't show me any updates on neither of the machines!

Thanks
Tobias

 

[udo]

...
oestersund:~# pveversion -v
pve-manager: 1.5-8 (pve-manager/1.5/4674)
running kernel: 2.6.24-10-pve
proxmox-ve-2.6.18: 1.5-5
...

Hi,
kernel-version and pve-version don't match!

Perhaps "apt-get install pve-qemu-kvm"

Udo

 

[iprigger]

Hi Udo,

Hi,
kernel-version and pve-version don't match!

Perhaps "apt-get install pve-qemu-kvm"

Udo

just did that, it now works.

fun thing is that pveversion -v gives funny output!

oestersund:~# pveversion -v
pve-manager: 1.5-8 (pve-manager/1.5/4674)
running kernel: 2.6.24-10-pve
pve-kernel-2.6.24-10-pve: 2.6.24-21
pve-kernel-2.6.18-2-pve: 2.6.18-5
qemu-server: 1.1-11
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-10
vncterm: 0.9-2
vzctl: 3.0.23-1pve8
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1

stockholm:~# pveversion -v
pve-manager: 1.5-8 (pve-manager/1.5/4674)
running kernel: 2.6.24-10-pve
proxmox-ve-2.6.24: 1.5-21
pve-kernel-2.6.24-10-pve: 2.6.24-21
pve-kernel-2.6.18-1-pve: 2.6.18-4
qemu-server: 1.1-11
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-10
vncterm: 0.9-2
vzctl: 3.0.23-1pve8
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.11.1-2

I'm missing pve-qemu-kvm - line on one system...

CU
Tobias

 

[soomon]

ok was the kernel issue!

thanks!

what's the big difference between those formats?
is there anything that shoud be preferred?