Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Seabios now can boot from virtio natively, so extboot is no longer needed. Libvirt relies on qemu help output to see check for extboot support. Qemu should drop boon=on from the help string.
*** Bug 614869 has been marked as a duplicate of this bug. ***
Comment 6Ritesh Raj Sarraf
2010-12-09 12:05:24 UTC
Sorry for asking in this bugzilla. I will open a new one if you want to.
What interface do you expect the user to use to specify the bootable device in virt-manager? I see no way to specify 'boot=on' in the GUI.
I have 4 virtio disks attached to my Guest VM but I have _no_ way to tell it to boot off of, say, the fourth disk.
Juggling around with the ordering of the disks in virt-manager doesn't look the best way to deal with.
I've verified this with virt stack on RHEL5.4 and also separately with kvm version:
17:26:18 rrs@champaran:~$ kvm -version
QEMU PC emulator version 0.12.5 (qemu-kvm-0.12.5), Copyright (c) 2003-2008 Fabrice Bellard
(In reply to comment #6)
> Sorry for asking in this bugzilla. I will open a new one if you want to.
>
> What interface do you expect the user to use to specify the bootable device in
> virt-manager? I see no way to specify 'boot=on' in the GUI.
> I have 4 virtio disks attached to my Guest VM but I have _no_ way to tell it to
> boot off of, say, the fourth disk.
>
> Juggling around with the ordering of the disks in virt-manager doesn't look the
> best way to deal with.
For now that is the only way to deal with it. There is work going on to provide better option.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHSA-2011-0534.html
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHSA-2011-0534.html