VMDK will not start after restore

P

Petrus4

Member
Feb 18, 2009
249
0
16
I have had to restore a backup of a vmdk disk that was running with no issues on another proxmox-ve installation that has now been wiped. I have not had issues restoring a ide w2k3 vm but this vmdk is showing problems.

Here is the error:

Code: 
qm[12467]: VM 108 start failed: command '/usr/bin/kvm -monitor unix:/var/run/qemu-server/108.mon,server,nowait -vnc unix:/var/run/qemu-server/108.vnc,password -pidfile /var/run/qemu-server/108.pid -daemonize -usbdevice tablet -name KABLINK -smp 8 -vga cirrus -tdf -k en-us -drive if=ide,index=2,media=cdrom -drive file=/var/lib/vz/images/108/vm-108-disk-1.vmdk,if=scsi,index=0,boot=on -m 2048 -net tap,vlan=0,ifname=vmtab108i0,script=/var/lib/qemu-server/bridge-vlan -net nic,vlan=0,model=e1000,macaddr=0E:77:F9:06:9E:3A -id 108 -cpuunits 1000' failed with exit code 1

Old proxmox-ve environment used kernel 2.6.24

New environment to which I restored runs 2.6.18

pveversion -v


pve-manager: 1.5-9 (pve-manager/1.5/4728)
running kernel: 2.6.18-2-pve
proxmox-ve-2.6.18: 1.5-5
pve-kernel-2.6.18-2-pve: 2.6.18-5
qemu-server: 1.1-14
pve-firmware: 1.0-5
libpve-storage-perl: 1.0-13
vncterm: 0.9-2
vzctl: 3.0.23-1pve11
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm-2.6.18: 0.9.1-5


It seems from other posts I might have to run this on the 2.6.24 kernel? I would rather not as I am using openVZ on this machine and want to keep the stable 2.6.18 kernel.
 
dietmar said:
2.6.18 does not support scsi disks - change that to ide instead.
Click to expand...

Thanks Dietmar, but changing to IDE does not work in this case. It is a SUSE Linux VMDK (sorry I might have confused everyone with mentioning W2K3).

Is OpenVZ supporting the 2.6.24 kernel yet.. or still is this still on hold?
 
dietmar said:
OpenVZ always worked with 2.6.24 kernel - or what is the question?
Click to expand...

In this post Tom wrote "I used the current stable ISO. 2.6.18 is the only stable openvz kernel and has quite good driver support (more or less RHEL 5.4 based) the development of openvz for 2.6.24 is frozen by the openvz team. " When referring to using ProxMox-VE on the Intel modular server. If it is just as good to use the 2.6.24 kernel on this server I will just do that. I will be running both openVZ and KVM VM's.
 
So my questions are: 1. how can I can get the vmdk to work with the 2.6.18 kernel.

2. Is it now OK to run the 2.6.24 kernel on a production system with OpenVZ?
 
Last edited:
dietmar said:
Please can you post the error message you get?
Click to expand...

Here is the error message:

Jun 2 09:35:13 proxmox-flex-1 qm[10888]: VM 108 start failed: command '/usr/bin /kvm -monitor unix:/var/run/qemu-server/108.mon,server,nowait -vnc unix:/var/run /qemu-server/108.vnc,password -pidfile /var/run/qemu-server/108.pid -daemonize - usbdevice tablet -name KABLINK -smp 8 -boot cad -vga cirrus -tdf -k en-us -drive file=/var/lib/vz/images/108/vm-108-disk-1.vmdk,if=ide,index=0,boot=on -m 2048 - net none -id 108 -cpuunits 1000' failed with exit code 1

Jun 2 09:35:13 proxmox-flex-1 pvedaemon[10887]: VM 108 start failed - Transport endpoint is not connected
 
dietmar said:
What output do you get when starting manually:

# qm start 108
Click to expand...

Here is the output: (just to be clear: this vmdk worked fine with the 2.6.24 kernel and SCSI, It is a SUSE LINUX VM)

Code: 
qemu: could not open disk image /var/lib/vz/images/108/vm-108-disk-1.vmdk
start failed: command '/usr/bin/kvm -monitor unix:/var/run/qemu-server/108.mon,server,nowait -vnc unix:/var/run/qemu-server/108.vnc,password -pidfile /var/run/qemu-server/108.pid -daemonize -usbdevice tablet -name KABLINK -smp 8 -boot cad -vga cirrus -tdf -k en-us -drive file=/var/lib/vz/images/108/vm-108-disk-1.vmdk,if=ide,index=0,boot=on -m 2048 -net none -id 108 -cpuunits 1000' failed with exit code 1
 
Petrus4;22740 [CODE said:
qemu: could not open disk image /var/lib/vz/images/108/vm-108-disk-1.vmdk
[/CODE]
Click to expand...

You already verified that the file exists?

If so, I guess the vmdk is not compatible with the kvm version shipped with 2.6.18. I suggest to convert it to raw (best using vmware tools).
 
dietmar said:
You already verified that the file exists?
Click to expand...

yes
proxmox-flex-1:/var/lib/vz/images/108# ls -ilh
total 2.3G
4136963 -rw-r--r-- 1 root root 2.3G May 31 19:31 vm-108-disk-1.vmdk


dietmar said:
If so, I guess the vmdk is not compatible with the kvm version shipped with 2.6.18. I suggest to convert it to raw (best using vmware tools).
Click to expand...

ok will give that a shot. thanks
 
ok converted to Raw, and now the disk will boot but hangs after a while with this error:

Could not find /dev/disk/by-id/scsi-0QEMU_QEMU_HARDDISK-scsi0-hd0-part1

Want me to fall back to /dev/disk/by-id/scsi-0QEMU_QEMU_HARDDISK-scsi0-hd0-part1 ? Y/N
Click to expand...

if yes or no both fall back to a command prompt.

I have read that I should edit both /etc/fstab and /boot/grub/menu.lst using a live CD and change all instances of sda to hda but there are no instances of sda or any othe sd drives in these files.

Any ideas on what I can do next?
 
dietmar said:
I do not know suse - but that looks like an udev issue. On Debian, the udev config resides in /etc/udev/rules.d/*
Click to expand...

No sda in udev/rules.d/* the only sda entry I could find was in mtab after changing this to hda I can mount the drive as ide with a live cd but still can't boot the drive fully.

This vmdk was made with SUSEstudio an appliance builder..
 
You must log in or register to reply here.
Top Bottom