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.
Descriptionvvyazmin@redhat.com
2013-03-07 14:04:52 UTC
Created attachment 706608[details]
## Logs vdsm, rhevm, libvirt, messages, dump
Description of problem:
Service Libvirt crashed during power off multiple VM's action
Version-Release number of selected component (if applicable):
RHEVM 3.1.3 - SI27.3 environment:
RHEVM: rhevm-3.1.0-50.el6ev.noarch
VDSM: vdsm-4.10.2-1.6.el6.x86_64
LIBVIRT: libvirt-0.10.2-18.el6.x86_64
QEMU & KVM: qemu-kvm-rhev-0.12.1.2-2.355.el6_4.1.x86_64
SANLOCK: sanlock-2.6-2.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
My environment:
DC: FC
Hosts: Servers x 4 (tigris[01-02].environment)
SD: XIO connected via FC switch (8Gbit)
VM's: Pool with 1000 VM's (automatic pool)
1. Create a pool with multiple VM's (VM's in state “UP”
2. Power off multiple VM's, with bulk 20-30 VM's
Actual results:
Service libvirt crashed (in my scenarios it's happened on both host's)
[root@tigris02 ~]# initctl status libvirtd
libvirtd stop/waiting
Expected results:
Successfully delete VM's
Additional info:
/var/log/ovirt-engine/engine.log
/var/log/vdsm/vdsm.log
Hi, vvyazmin
I can not reproduce this bug with
libvirt-0.10.2-18.el6.x86_64
vdsm-4.10.2-1.8.el6ev.x86_64
1) add HOST and FC Storage Domain to rhevm
2) create 40 vms
3) start vms and destroy vms and restart vms it works well
4) check libvirtd works well
# service libvirtd status
libvirtd (pid 3755) is running...
So can you provide some core method to reproduce it or if there is a new package fixed this bug, can you verify it ?
Thanks very much
Wenlong
(In reply to comment #0)
>
> 1. Create a pool with multiple VM's (VM's in state “UP”
> 2. Power off multiple VM's, with bulk 20-30 VM's
How are you powering off VMs? Is it with virDomainDestroy (forceful, should always work) or virDomainShutdown (graceful, but guest interaction required)?
I didn't see any crash message in the libvirt.log.9.gz included in your log capture, and still haven't reproduced anything locally, so I'm trying to figure out what API was involved just before the crash.
bug 924756 mentions another heap smashing bug seen when shutting down a domain; I suspect they are the same cause but have not yet found where the heap smashing is happening.
bug 915353 describes a crash on shutdown; it was fixed for libvirt-0.10.2-18.el6_4.1 - I'm starting to think that this particular fix is the one that solves the problem at hand.
I'm closing as a duplicate of bug 915353; we can reopen if we find more relevant information to prove that it is an independent issue.
*** This bug has been marked as a duplicate of bug 915353 ***
Created attachment 706608 [details] ## Logs vdsm, rhevm, libvirt, messages, dump Description of problem: Service Libvirt crashed during power off multiple VM's action Version-Release number of selected component (if applicable): RHEVM 3.1.3 - SI27.3 environment: RHEVM: rhevm-3.1.0-50.el6ev.noarch VDSM: vdsm-4.10.2-1.6.el6.x86_64 LIBVIRT: libvirt-0.10.2-18.el6.x86_64 QEMU & KVM: qemu-kvm-rhev-0.12.1.2-2.355.el6_4.1.x86_64 SANLOCK: sanlock-2.6-2.el6.x86_64 How reproducible: 100% Steps to Reproduce: My environment: DC: FC Hosts: Servers x 4 (tigris[01-02].environment) SD: XIO connected via FC switch (8Gbit) VM's: Pool with 1000 VM's (automatic pool) 1. Create a pool with multiple VM's (VM's in state “UP” 2. Power off multiple VM's, with bulk 20-30 VM's Actual results: Service libvirt crashed (in my scenarios it's happened on both host's) [root@tigris02 ~]# initctl status libvirtd libvirtd stop/waiting Expected results: Successfully delete VM's Additional info: /var/log/ovirt-engine/engine.log /var/log/vdsm/vdsm.log