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.
DescriptionFrancesco Romani
2014-12-16 16:11:54 UTC
Description of problem:
During an automated test of oVirt involving automated migration of some VMs, libvirtd crashed.
Logs and coredump attached.
How reproducible:
Not really sure. Seems more likely with consecutive migration, but failed to find a common cause yet.
Steps to Reproduce:
1. run 5 VMs on a node
2. migrate all of them at the same time
3.
Actual results:
In still unclear circumstances, libvirt crashes
Expected results:
No crash
Looking at the stacktrace.txt:
#0 __strchr_sse42 () at ../sysdeps/x86_64/multiarch/strchr.S:136
#1 0x00007fd471e744d0 in virParseOwnershipIds (label=0x0, uidPtr=uidPtr@entry=0x7fd462dad818, gidPtr=gidPtr@entry=0x7fd462dad81c) at util/virutil.c:2072
#2 0x00007fd45b20521e in qemuOpenFile (driver=driver@entry=0x7fd454161dd0, vm=vm@entry=0x7fd43400cc60,
path=path@entry=0x7fd434013e10 "/rhev/data-center/e57f317b-010a-40fe-832a-88801dd2f2b4/9345b29e-0551-4bee-9f88-de9b86612079/images/d2bae584-09f2-426e-83a9-655c42552c25/6abb9336-2b13-4627-bead-937e595208ba", oflags=oflags@entry=0,
needUnlink=needUnlink@entry=0x0, bypassSecurityDriver=bypassSecurityDriver@entry=0x0) at qemu/qemu_driver.c:2780
#3 0x00007fd45b20e21e in qemuDomainGetBlockInfo (dom=0x7fd438015710,
path=0x7fd434013e10 "/rhev/data-center/e57f317b-010a-40fe-832a-88801dd2f2b4/9345b29e-0551-4bee-9f88-de9b86612079/images/d2bae584-09f2-426e-83a9-655c42552c25/6abb9336-2b13-4627-bead-937e595208ba", info=0x7fd462dadb40,
flags=<optimized out>) at qemu/qemu_driver.c:10124
This is the same crash as in bug 1162208 and bug 1171124