Marking Fix Released per user's comment.
** Changed in: libvirt (Ubuntu)
Status: Incomplete = Fix Released
--
lucid qemu: could not open disk image
https://bugs.launchpad.net/bugs/512259
You received this bug notification because you are a member of Ubuntu
Server Team, which is
after system update everything is ok
--
lucid qemu: could not open disk image
https://bugs.launchpad.net/bugs/512259
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Ubuntu-server-bugs mailing list
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?
--
lucid qemu: could not open disk image
https://bugs.launchpad.net/bugs/512259
You received this bug notification because you are a member of
I upgraded from Karmic to Lucid alpha 3 and cannot reproduce your
problem. virsh start works fine for my old VMs.
--
lucid qemu: could not open disk image
https://bugs.launchpad.net/bugs/512259
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
I am using virsh:
# virsh start kvm_session
That worked fine until upgrade.
--
lucid qemu: could not open disk image
https://bugs.launchpad.net/bugs/512259
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
What is the command line you're using to launch your KVM's?
:-Dustin
** Changed in: qemu-kvm (Ubuntu)
Status: New = Incomplete
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided = Low
--
lucid qemu: could not open disk image
https://bugs.launchpad.net/bugs/512259
You received
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.
--
lucid qemu: could not open disk image
https://bugs.launchpad.net/bugs/512259
You received this bug notification because you are a member of Ubuntu
Server Team, which
