Bug 643681 – Do not advertise boot=on capability to libvirt

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 643681 - Do not advertise boot=on capability to libvirt

Summary:	Do not advertise boot=on capability to libvirt

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	qemu-kvm (Show other bugs)
Sub Component:
Version:	6.1
Hardware:	All Linux

Priority	low Severity medium
Target Milestone:	rc
Target Release:	---
Assigned To:	Gleb Natapov
QA Contact:	Virtualization Bugs
Docs Contact:

URL:
Whiteboard:
Keywords:

Duplicates:	614869 (view as bug list)
Depends On:
Blocks:	580954
	Show dependency tree / graph

Reported:	2010-10-17 06:15 EDT by Gleb Natapov
Modified:	2013-12-08 19:51 EST (History)
CC List:	11 users (show)

See Also:
Fixed In Version:	qemu-kvm-0.12.1.2-2.117.el6
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2011-05-19 07:32:57 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2011:0534	normal	SHIPPED_LIVE	Important: qemu-kvm security, bug fix, and enhancement update	2011-05-19 07:20:36 EDT

Groups: None (edit)

Description Gleb Natapov 2010-10-17 06:15:09 EDT

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.

Comment 5 Gleb Natapov 2010-11-04 14:49:03 EDT

*** Bug 614869 has been marked as a duplicate of this bug. ***

Comment 6 Ritesh Raj Sarraf 2010-12-09 07:05:24 EST

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

Comment 7 Gleb Natapov 2010-12-10 12:56:35 EST

(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.

Comment 9 Keqin Hong 2011-01-12 04:51:50 EST

Verified, PASS.
Steps:
1. # /usr/libexec/qemu-kvm --help | grep "boot=on"

Make sure above cmd gives empty output.

Comment 11 errata-xmlrpc 2011-05-19 07:32:57 EDT

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

Comment 12 errata-xmlrpc 2011-05-19 08:49:32 EDT

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

Note You need to log in before you can comment on or make changes to this bug.