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 1209813 - libvirtd crashes after memory device hot-plug crashes qemu
Summary: libvirtd crashes after memory device hot-plug crashes qemu
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.2
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Peter Krempa
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-08 09:23 UTC by Luyao Huang
Modified: 2015-11-19 06:27 UTC (History)
6 users (show)

Fixed In Version: libvirt-1.2.15-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 06:27:30 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2202 0 normal SHIPPED_LIVE libvirt bug fix and enhancement update 2015-11-19 08:17:58 UTC

Description Luyao Huang 2015-04-08 09:23:30 UTC 
description of problem:
libvirtd crashes after memory device hot-unplug crashes qemu

Version-Release number of selected component (if applicable):
libvirt-1.2.14-1.el7.x86_64
qemu-kvm-rhev-2.2.0-8.el7.x86_64

How reproducible:
60%(cannot reproduce it every time, this issue just like bug
https://bugzilla.redhat.com/show_bug.cgi?id=1161024)

Steps to Reproduce:
1.prepare a dom have maxmemory setttings (prepare for memdevice)
# virsh dumpxml test3

  <maxMemory slots='16' unit='KiB'>1524288</maxMemory>
  <memory unit='KiB'>1024000</memory>
  <currentMemory unit='KiB'>1024000</currentMemory>
  <vcpu placement='static' cpuset='0-1' current='2'>4</vcpu>
...
  <cpu>
    <numa>
      <cell id='0' cpus='0-1' memory='512000' unit='KiB'/>
      <cell id='1' cpus='2-3' memory='512000' unit='KiB'/>
    </numa>
  </cpu>
...


2. start it

# virsh start test3
Domain test3 started

3.hotplug memdevice

# cat memdevice.xml
    <memory model='dimm'>
      <target>
        <size unit='KiB'>500000</size>
        <node>1</node>
      </target>
    </memory>

# virsh attach-device test3 memdevice.xml
error: Failed to attach device from memdevice.xml
error: End of file while reading data: Input/output error



Actual results:
libvirtd crashes after memory device hot-unplug crashes qemu

Expected results:
fix it

infomation:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f6aa252d700 (LWP 15528)]
qemuMonitorDelObject (mon=0x0, objalias=0x7f6a8c000b00 "memdimm0") at qemu/qemu_monitor.c:3268
3268            if (mon->json)
(gdb) bt
#0  qemuMonitorDelObject (mon=0x0, objalias=0x7f6a8c000b00 "memdimm0") at qemu/qemu_monitor.c:3268
#1  0x00007f6a99af3ecc in qemuDomainAttachMemory (driver=driver@entry=0x7f6a90184a70, vm=vm@entry=0x7f6a901e6470, mem=0x7f6a8c000c00) at qemu/qemu_hotplug.c:1735
#2  0x00007f6a99b5eca9 in qemuDomainAttachDeviceLive (dom=<optimized out>, dev=0x7f6a8c000b80, vm=0x7f6a901e6470) at qemu/qemu_driver.c:7672
#3  qemuDomainAttachDeviceFlags (dom=<optimized out>, xml=<optimized out>, flags=<optimized out>) at qemu/qemu_driver.c:8379
#4  0x00007f6ab21a9386 in virDomainAttachDevice (domain=domain@entry=0x7f6a8c001560,
    xml=0x7f6a8c001370 "    <memory model='dimm'>\n      <target>\n        <size unit='KiB'>500000</size>\n        <node>1</node>\n      </target>\n    </memory>\n") at libvirt-domain.c:8334
#5  0x00007f6ab2c55e9f in remoteDispatchDomainAttachDevice (server=0x7f6ab48d3ef0, msg=0x7f6ab48ec460, args=0x7f6a8c000c70, rerr=0x7f6aa252cc70, client=<optimized out>) at remote_dispatch.h:2732
#6  remoteDispatchDomainAttachDeviceHelper (server=0x7f6ab48d3ef0, client=<optimized out>, msg=0x7f6ab48ec460, rerr=0x7f6aa252cc70, args=0x7f6a8c000c70, ret=0x7f6a8c000920) at remote_dispatch.h:2708
#7  0x00007f6ab220b152 in virNetServerProgramDispatchCall (msg=0x7f6ab48ec460, client=0x7f6ab48ed290, server=0x7f6ab48d3ef0, prog=0x7f6ab48e8920) at rpc/virnetserverprogram.c:437
#8  virNetServerProgramDispatch (prog=0x7f6ab48e8920, server=server@entry=0x7f6ab48d3ef0, client=0x7f6ab48ed290, msg=0x7f6ab48ec460) at rpc/virnetserverprogram.c:307
#9  0x00007f6ab2c63efd in virNetServerProcessMsg (msg=<optimized out>, prog=<optimized out>, client=<optimized out>, srv=0x7f6ab48d3ef0) at rpc/virnetserver.c:172
#10 virNetServerHandleJob (jobOpaque=<optimized out>, opaque=0x7f6ab48d3ef0) at rpc/virnetserver.c:193
#11 0x00007f6ab2107615 in virThreadPoolWorker (opaque=opaque@entry=0x7f6ab48cee70) at util/virthreadpool.c:145
#12 0x00007f6ab2106b38 in virThreadHelper (data=<optimized out>) at util/virthread.c:206
#13 0x00007f6aaf53fdf5 in start_thread (arg=0x7f6aa252d700) at pthread_create.c:308
#14 0x00007f6aaf2661ad in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113
Additional info:
Comment 1 Peter Krempa 2015-04-16 12:53:35 UTC 
Fixed upstream:

commit c44108522bea406a0e1a726807a687f313687a42
Author: Peter Krempa <pkrempa>
Date:   Tue Apr 14 17:52:48 2015 +0200

    qemu: monitor: Refactor and fix monitor checking
    
    Among all the monitor APIs some where checking if mon is NULL and some
    were not. Since it's possible to have mon equal to NULL in case a second
    call is attempted once entered the monitor. This requires that every
    single API checks for the monitor.
    
    This patch adds a macro that helps checking the state of the monitor and
    either refactors existing checking code to use the macro or adds it in
    case it was missing.

v1.2.14-200-gc441085
Comment 3 Luyao Huang 2015-07-07 07:51:49 UTC 
Verify this bug with libvirt-1.2.16-1.el7.x86_64 and qemu-kvm-rhev-2.2.0-8.el7.x86_64:

1.
# virsh dumpxml r6

  <maxMemory slots='16' unit='KiB'>1524288</maxMemory>
  <memory unit='KiB'>1024000</memory>
  <currentMemory unit='KiB'>1024000</currentMemory>

  <cpu>
    <numa>
      <cell id='0' cpus='0' memory='512000' unit='KiB'/>
      <cell id='1' cpus='1-2' memory='512000' unit='KiB'/>
    </numa>
  </cpu>

2. start it :

# virsh start r6
Domain r6 started

3. attach memory device:

# virsh attach-device r6 memdevice.xml
error: Failed to attach device from memdevice.xml
error: Unable to read from monitor: Connection reset by peer

4. repeat step 2 and 3 1000 times, no libvirtd crashed, and we can find log in libvirtd.log:

2015-07-07 07:40:21.645+0000: 32479: error : qemuMonitorIORead:606 : Unable to read from monitor: Connection reset by peer
2015-07-07 07:40:21.646+0000: 32480: error : qemuMonitorDelObject:3005 : invalid argument: monitor must not be NULL
2015-07-07 07:45:09.856+0000: 32479: error : qemuMonitorIORead:606 : Unable to read from monitor: Connection reset by peer
2015-07-07 07:45:13.288+0000: 32479: error : qemuMonitorIORead:606 : Unable to read from monitor: Connection reset by peer
2015-07-07 07:45:13.290+0000: 32484: error : qemuMonitorDelObject:3005 : invalid argument: monitor must not be NULL
2015-07-07 07:45:16.301+0000: 32479: error : qemuMonitorIORead:606 : Unable to read from monitor: Connection reset by peer
2015-07-07 07:45:16.302+0000: 32483: error : qemuMonitorDelObject:3005 : invalid argument: monitor must not be NULL
Comment 5 errata-xmlrpc 2015-11-19 06:27:30 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.

https://rhn.redhat.com/errata/RHBA-2015-2202.html
Note You need to log in before you can comment on or make changes to this bug.