lucid qemu: could not open disk image

[hernad-b-out-ba]

Binary package hint: qemu-kvm

after upgrade to 2.6.32-11 kernel cannot start any of kvm sessions:

internal error unable to start guest: qemu: could not open disk image : No such file or directory

I can access disk images directly.

ProblemType: Bug
Architecture: amd64
Date: Mon Jan 25 11:01:15 2010
DistroRelease: Ubuntu 10.04
KvmCmdLine: Error: command ['ps', '-C', 'kvm', '-F'] failed with exit code 1: UID PID PPID C SZ RSS PSR STIME TTY TIME CMD
Lsusb:
 Bus 002 Device 002: ID 0000:0000
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP ProLiant ML115 G5
Package: kvm 1:84+dfsg-0ubuntu16+0.12.2+0ubuntu1
ProcCmdLine: BOOT_IMAGE=//vmlinuz-2.6.32-10-generic root=/dev/mapper/smraka--2-root ro quiet splash
ProcEnviron:
 LANG=bs_BA.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
SourcePackage: qemu-kvm
Uname: Linux 2.6.32-10-generic x86_64
dmi.bios.date: 05/26/2008
dmi.bios.vendor: HP
dmi.bios.version: O18
dmi.chassis.type: 7
dmi.chassis.vendor: HP
dmi.modalias: dmi:bvnHP:bvrO18:bd05/26/2008:svnHP:pnProLiantML115G5:pvr:cvnHP:ct7:cvr:
dmi.product.name: ProLiant ML115 G5
dmi.sys.vendor: HP

[hernad-b-out-ba (hernad-b-out-ba)]

I have tried to boot previous kernel 2.6.32-10, but the same results - couldn't open qemu image

The images are qcow2 format.

[Dustin Kirkland  (kirkland)]

What is the command line you're using to launch your KVM's?

:-Dustin

[hernad-b-out-ba (hernad-b-out-ba)]

I am using virsh:

# virsh start <kvm_session>

That worked fine until upgrade.

[Torsten Spindler (tspindler)]

I upgraded from Karmic to Lucid alpha 3 and cannot reproduce your problem. virsh start works fine for my old VMs.

[Dustin Kirkland  (kirkland)]

I cannot reproduce this problem either, with KVM.

There may well still be a problem with virsh or libvirt. I'm going to move the bug over to virsh for now. Thanks!

[Jamie Strandboge (jdstrand)]

There is nothing in the dmesg suggesting it is AppArmor.

hernad-b-out-ba, did you disable the AppArmor or the AppArmor security driver in libvirt?

[hernad-b-out-ba (hernad-b-out-ba)]

after system update everything is ok

[Jamie Strandboge (jdstrand)]

Marking Fix Released per user's comment.