qemu: could not open disk image

[frantek]

Hi,

I've upgraded to the latest 1.8 and wanted to add a disk to one old KVM VM. When I try to start the VM I get:

#qm start 101

qemu: could not open disk image /var/lib/vz/images/101/vm-101-disk-1.vmdk

start failed: command '/usr/bin/kvm -monitor unix:/var/run/qemu-server/101.mon,server,nowait -vnc unix:/var/run/qemu-server/101.vnc,password -pidfile /var/run/qemu-server/101.pid -daemonize -usbdevice tablet -name oracle -smp 1 -boot c -vga cirrus -tdf -k de -drive if=ide,index=2,media=cdrom -drive file=/var/lib/vz/images/101/oracle-pve-flat.vmdk,if=scsi,index=0,boot=on -drive file=/var/lib/vz/images/101/vm-101-disk-1.vmdk,if=scsi,index=1 -m 1024 -net tap,vlan=0,ifname=tap101i0,script=/var/lib/qemu-server/bridge-vlan -net nic,vlan=0,model=rtl8139,macaddr=B2:BE:85:6D:9F:15 -id 101 -cpuunits 1000' failed with exit code 1

The config looks like this:

# cat 101.conf 

name: oracle
ide2: none,media=cdrom
vlan0: rtl8139=B2:BE:85:6D:9F:15
bootdisk: scsi0
ostype: l26
memory: 1024
sockets: 1
onboot: 0
cores: 1
scsi0: local:101/oracle-pve-flat.vmdk
boot: c
freeze: 0
cpuunits: 1000
acpi: 1
kvm: 1
scsi1: local:101/vm-101-disk-1.vmdk

It's an old VMware VM I've migrate to KVM about a year ago.

Can some one help ?
TIA

 

[tom]

can you boot whiteout the second disk? how did you create this disk (vm-101-disk-1.vmdk)

why do you use scsi, can´t you use virtio? which guest OS?

also post 'pveversion -v'

 

[frantek]

can you boot whiteout the second disk?

YES

how did you create this disk (vm-101-disk-1.vmdk)

Proxmox Web-GUI

why do you use scsi, can´t you use virtio?

No special reason. I'm just used to use SCSI and it allways worked. What is the advantage of virtio ?

which guest OS?

Ubnutu 8.04.1

also post 'pveversion -v'

# pveversion -v
pve-manager: 1.8-18 (pve-manager/1.8/6070)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.18: 1.8-15
pve-kernel-2.6.32-4-pve: 2.6.32-33
pve-kernel-2.6.18-6-pve: 2.6.18-15
qemu-server: 1.1-30
pve-firmware: 1.0-11
libpve-storage-perl: 1.0-17
vncterm: 0.9-2
vzctl: 3.0.28-1pve1
vzdump: 1.2-14
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm-2.6.18: 0.9.1-15

 

[tom]

# pveversion -v
pve-manager: 1.8-18 (pve-manager/1.8/6070)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.18: 1.8-15
pve-kernel-2.6.32-4-pve: 2.6.32-33
pve-kernel-2.6.18-6-pve: 2.6.18-15
qemu-server: 1.1-30
pve-firmware: 1.0-11
libpve-storage-perl: 1.0-17
vncterm: 0.9-2
vzctl: 3.0.28-1pve1
vzdump: 1.2-14
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm-2.6.18: 0.9.1-15

you got an unsupported mix of running kernel and kvm. see http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_to_1.8 and http://pve.proxmox.com/wiki/Proxmox_VE_Kernel

if you decide to use 2.6.32 you need to install the virtual package for 2.6.32:

aptitude install proxmox-ve-2.6.32

 

[frantek]

thanx, fixed the problem !