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.
Created attachment 627170[details]
the xml of guest
Description of problem:
libvirtd crashes when both <boot dev='...'/> and <boot order='...'/> are used in one domain XML
Version-Release number of selected component (if applicable):
libvirt-0.10.2-2.el6.x86_64
qemu-kvm-0.12.1.2-2.316.el6.x86_64
kernel-2.6.32-312.el6.x86_64
How reproducible:
100%
1 prepare the domain xml,for detail you can see the attachment
create a new domain XML with both <boot dev='...'/> and <boot order='...'/>
elements
2. define the guest
# virsh define testfull.xml
error: Failed to define domain from testfull.xml
error: End of file while reading data: Input/output error
error: Failed to reconnect to the hypervisor
3 it works well on following pkg,and there was a bug like this issue 751287,however this bug had already been closed.
libvirt-0.10.1-1.el6.x86_64
Actual results:
the libvirtd crashed,while defined the guest
Expected results:
The guest should be defined successfully and the libvirtd should keep running
Additional info
Test this with: libvirt-0.10.2-4.el6.x86_64
I use attached guest xml https://bugzilla.redhat.com/attachment.cgi?id=627170
virsh # edit qemu-ga
error: unsupported configuration: per-device boot elements cannot be used together with os/boot elements
Failed. Try again? [y,n,f,?]:
[root@pengzhimoutest ~]# virsh define test.xml
error: Failed to define domain from test.xml
error: unsupported configuration: per-device boot elements cannot be used together with os/boot elements
# service libvirtd status
libvirtd (pid 7295) is running...
So, this bug is verified.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHSA-2013-0276.html
Created attachment 627170 [details] the xml of guest Description of problem: libvirtd crashes when both <boot dev='...'/> and <boot order='...'/> are used in one domain XML Version-Release number of selected component (if applicable): libvirt-0.10.2-2.el6.x86_64 qemu-kvm-0.12.1.2-2.316.el6.x86_64 kernel-2.6.32-312.el6.x86_64 How reproducible: 100% 1 prepare the domain xml,for detail you can see the attachment create a new domain XML with both <boot dev='...'/> and <boot order='...'/> elements 2. define the guest # virsh define testfull.xml error: Failed to define domain from testfull.xml error: End of file while reading data: Input/output error error: Failed to reconnect to the hypervisor 3 it works well on following pkg,and there was a bug like this issue 751287,however this bug had already been closed. libvirt-0.10.1-1.el6.x86_64 Actual results: the libvirtd crashed,while defined the guest Expected results: The guest should be defined successfully and the libvirtd should keep running Additional info