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
Bugs, which is subscribed to Ub
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.
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 Ubuntu
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!
** Package changed: qemu-kvm (Ubuntu) => libvirt (Ubuntu)
--
lucid qemu: could not open disk image
https://bugs.launchpad.net/bug
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
Bugs, which is subscribed to Ubun
I am using virsh:
# virsh start
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@l
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 t
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/38356525/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/38356526/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/38356527/Dependencies.txt
** A
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
Bugs, which is subscr