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.
Bug 817078 - libvirtd crashing on rhel 6.3 beta vm
Summary: libvirtd crashing on rhel 6.3 beta vm
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jiri Denemark
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-27 15:33 UTC by Derek Higgins
Modified: 2012-06-20 06:57 UTC (History)
9 users (show)

Fixed In Version: libvirt-0.9.10-16.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 06:57:50 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:0748 0 normal SHIPPED_LIVE Low: libvirt security, bug fix, and enhancement update 2012-06-19 19:31:38 UTC

Description Derek Higgins 2012-04-27 15:33:15 UTC 
Description of problem:
While starting a vm on rhel 6.3 Beta (which itself is a vm), libvirtd crashes

Version-Release number of selected component (if applicable):
libvirt-0.9.10-11.el6.x86_64

How reproducible:
every time

Steps to Reproduce:
1. create a rhel 6.3 vm
2. using this vm as a host attempt to start another vm
3.
  
Actual results:
libvird crashes

Expected results:
nested vm should start

Additional info:

this symbolic link was created on the virtual host 
/usr/bin/qemu-system-x86_64 -> /usr/libexec/qemu-kvm

output from gdb attached to libvirtd
Program received signal SIGSEGV, Segmentation fault.
0x0000000000476292 in qemuBuildCpuArgStr (conn=0x7f0118000bd0, driver=0x7f0128006430, def=0x7f0128133590, monitor_chr=0x7f012804e5d0, monitor_json=true, qemuCaps=0x7f0128133a30, migrateFrom=0x0, migrateFd=-1,
    snapshot=0x0, vmop=VIR_NETDEV_VPORT_PROFILE_OP_CREATE) at qemu/qemu_command.c:3824
3824        cpuDataFree(host->arch, data);



As discussed with danpb this is fixed upstream

commit 2ccc4a607f6e122aff2e3b9d133d6e6b4b661a1e
Author: Jiri Denemark <jdenemar>
Date:   Wed Feb 15 12:18:25 2012 +0100

    qemu: Fix segfault when host CPU is empty
    
    In case libvirtd cannot detect host CPU model (which may happen if it
    runs inside a virtual machine), the daemon is likely to segfault when
    starting a new qemu domain. It segfaults when domain XML asks for host
    (either model or passthrough) CPU or does not ask for any specific CPU
    model at all.
Comment 3 Jiri Denemark 2012-04-30 07:29:54 UTC 
In post: http://post-office.corp.redhat.com/archives/rhvirt-patches/2012-April/msg00881.html
Comment 12 errata-xmlrpc 2012-06-20 06:57:50 UTC 
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-2012-0748.html
Note You need to log in before you can comment on or make changes to this bug.