registry team mailing list archive

[Jamie Strandboge <jamie@xxxxxxxxxx>]

Public bug reported:

Upstream QEmu does not support boot=on when using -no-kvm, so libvirt qemu domains fail to boot. This is:
https://bugzilla.redhat.com/show_bug.cgi?id=594068

Patch:
https://www.redhat.com/archives/libvir-list/2010-July/msg00690.html

This definitely affects Lucid, but does not affect maverick. I don't
know about earlier releases.

** Affects: libvirt (Ubuntu)
     Importance: Undecided
         Status: Invalid

** Affects: libvirt (Ubuntu Lucid)
     Importance: Medium
         Status: Triaged

** Affects: libvirt (Fedora)
     Importance: Unknown
         Status: Unknown

** Bug watch added: Red Hat Bugzilla #594068
   https://bugzilla.redhat.com/show_bug.cgi?id=594068

** Also affects: libvirt (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=594068
   Importance: Unknown
       Status: Unknown

** Summary changed:

- libvirt/qemu guests don't boot with --no-kvm
+ libvirt/qemu guests don't boot with -no-kvm

** Changed in: libvirt (Ubuntu)
       Status: New => Triaged

** Also affects: libvirt (Ubuntu Lucid)
   Importance: Undecided
       Status: New

** Changed in: libvirt (Ubuntu Lucid)
       Status: New => Triaged

** Changed in: libvirt (Ubuntu)
       Status: Triaged => Invalid

** Changed in: libvirt (Ubuntu Lucid)
   Importance: Undecided => Medium

** Changed in: libvirt (Ubuntu Lucid)
    Milestone: None => lucid-updates

-- 
libvirt/qemu guests don't boot with -no-kvm
https://bugs.launchpad.net/bugs/665359
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for Fedora.