I'm not sure if this is any help, if it's related, or at all relevant
but I thought I'd throw out something that I noticed. I recently did a
clean install on my system and upgraded to Maverick. I have had a heck
of a time getting my vm's back up and running. I was able to get them
to boot if I interfaced with KVM directly however when I used virt-
manager I would consistently get an error, "Boot failed: not a bootable
disk" followed by "No bootable device." as if there wasn't a boot device
at all.
I found this bug and at random tried changing the
"allow_disk_format_probing" to 1 and my vm booted. I tested by
disabling the disk format probing and my problem returned. My thought
was that maybe the vm wasn't able to read the boot sector of the image.
It was just a random guess after I've pounded on this problem for about
a week.
I'm not terribly experienced with these things but I'd be happy to offer
some logs or whatever I can if it would be of service. You might have
to help me out with how to obtain them but I'd love to be able to
contribute something. Kudos to all of you work on these things, it's
greatly appreciated!
Thanks!
--
libvirt no longer supports format=host_device
https://bugs.launchpad.net/bugs/665531
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.ubuntu.com/mailman/listinfo/ubuntu-bugs
