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 1528178 - qemu-kvm quits with early memory unplug
Summary: qemu-kvm quits with early memory unplug
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm-rhev
Version: 7.5
Hardware: ppc64le
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Serhii Popovych
QA Contact: Min Deng
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-21 08:20 UTC by Min Deng
Modified: 2018-06-13 03:12 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-13 03:12:05 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Min Deng 2017-12-21 08:20:35 UTC 
Description of problem:
qemu-kvm quit since Detaching after fork from child process 53251

Version-Release number of selected component (if applicable):
kernel-3.10.0-823.el7.ppc64le (host and guest)
qemu-kvm-rhev-2.10.0-13.el7.ppc64le

How reproducible:
30%

Steps to Reproduce:
1./usr/libexec/qemu-kvm -name guest=nrs,debug-threads=on -machine pseries,accel=kvm,usb=off,dump-guest-core=off -m size=8388608k,slots=256,maxmem=419430400k -realtime mlock=off -smp 4,sockets=4,cores=1,threads=1 -numa node,nodeid=0,cpus=0-1,mem=4096 -numa node,nodeid=1,cpus=2-3,mem=4096 -uuid d7987973-2467-43ff-b8d2-acefc6ac59e5 -display none -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/tmp/qmp,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -boot strict=on -device qemu-xhci,id=usb,bus=pci.0,addr=0x3 -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x2 -drive file=rhel75-ppc64le-virtio-scsi.qcow2,format=qcow2,if=none,id=drive-scsi0-0-0-0 -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=1 -netdev tap,script=/etc/qemu-ifup,downscript=/etc/qemu-ifdown,id=hostnet0,vhost=on -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:89:8a:8b,bus=pci.0,addr=0x1 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on -monitor stdio -chardev socket,id=serial_id_serial0,path=/tmp/S,server,nowait -device spapr-vty,reg=0x30000000,chardev=serial_id_serial0 -monitor unix:/tmp/monitor3,server,nowait
2.during early booting stage
(qemu) object_add memory-backend-ram,id=mem1,size=10G
(qemu) device_add pc-dimm,id=dimm1,memdev=mem1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
3.

Actual results:
QEMU-KVM quit,in a word,there wasn't qemu-kvm process on host.
/usr/libexec/qemu-kvm -name guest=nrs,debug-threads=on -machine pseries,accel=kvm,usb=off,dump-guest-core=off -m size=8388608k,slots=256,maxmem=419430400k -realtime mlock=off -smp 4,sockets=4,cores=1,threads=1 -numa node,nodeid=0,cpus=0-1,mem=4096 -numa node,nodeid=1,cpus=2-3,mem=4096 -uuid d7987973-2467-43ff-b8d2-acefc6ac59e5 -display none -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/tmp/qmp,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -boot strict=on -device qemu-xhci,id=usb,bus=pci.0,addr=0x3 -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x2 -drive file=rhel75-ppc64le-virtio-scsi.qcow2,format=qcow2,if=none,id=drive-scsi0-0-0-0 -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=1 -netdev tap,script=/etc/qemu-ifup,downscript=/etc/qemu-ifdown,id=hostnet0,vhost=on -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:89:8a:8b,bus=pci.0,addr=0x1 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on -monitor stdio -chardev socket,id=serial_id_serial0,path=/tmp/S,server,nowait -device spapr-vty,reg=0x30000000,chardev=serial_id_serial0 -monitor unix:/tmp/monitor3,server,nowait
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x3fffb5c3ead0 (LWP 53155)]
Detaching after fork from child process 53159.
[New Thread 0x3fffb532ead0 (LWP 53170)]
QEMU 2.10.0 monitor - type 'help' for more information
(qemu) [New Thread 0x3fffb46eead0 (LWP 53171)]
[New Thread 0x3fffb3ecead0 (LWP 53172)]
[New Thread 0x3fffb36aead0 (LWP 53173)]
[New Thread 0x3fffb2e8ead0 (LWP 53174)]

(qemu) object_add memory-backend-ram,id=mem1,size=10G
(qemu) device_add pc-dimm,id=dimm1,memdev=mem1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu)  device_del dimm1
(qemu) Detaching after fork from child process 53251.
[Thread 0x3fffb2e8ead0 (LWP 53174) exited]
[Thread 0x3fffb36aead0 (LWP 53173) exited]
[Thread 0x3fffb3ecead0 (LWP 53172) exited]
[Thread 0x3fffb46eead0 (LWP 53171) exited]
[Thread 0x3fffb5c3ead0 (LWP 53155) exited]
[Thread 0x3fffb67ed090 (LWP 53152) exited]
[Inferior 1 (process 53152) exited normally]

Expected results:
Guest works well

Additional info:
Comment 2 Min Deng 2017-12-21 08:21:56 UTC 
QE will test it on x86 and update results as soon as possible.
Comment 3 David Gibson 2017-12-22 01:09:13 UTC 
What exactly is the symptom in the guest?

The messages you show look as if you're running qemu under gdb.  What happens if you don't use gdb?
Comment 4 Min Deng 2017-12-22 06:43:54 UTC 

(In reply to Min Deng from comment #2)
> QE will test it on x86 and update results as soon as possible.

  QE couldn't reproduce the issue on x86 platform 
  kernel-3.10.0-823.el7.x86_64
  qemu-kvm-rhev-2.10.0-12.el7.x86_64
Comment 5 Min Deng 2017-12-22 06:47:25 UTC 
> The messages you show look as if you're running qemu under gdb.  What
> happens if you don't use gdb?

  QE just wanted to grab more information for this issue so use gdb,and there wasn't any difference between them in my opinions.
Comment 7 David Gibson 2018-01-03 02:45:41 UTC 
Because this only happens sometimes, with repeated unplug during an early boot stage, this isn't vital enough to get the exception or blocker flags.

Therefore, postponing to 7.6.
Comment 8 Serhii Popovych 2018-06-05 16:05:56 UTC 
Retesting conditions from comment 0 on current components:

Host : kernel-3.10.0-862.el7.ppc64le
Qemu : qemu-kvm-rhev-2.12.0-3.el7.ppc64le
Guest: kernel-3.10.0-897.el7.ppc64le and kernel-4.14.0-66.el7a.ppc64le

I'm not able to reproduce described issue reliably. However I can reproduce most of times (2/3) memory hot-unplug failures that applied to both 4.14 and 3.10 kernels.

They look as bz1432302, except for error message, that is duplicate of bz1245892.

After guest reboot qemu gets notified about DEVICE_DELETE and dimm1 device removed. Both guest and qemu via HMP "info numa" reports that memory removed.

So after initial hot plug memory is used by guest kernel for some reason.
------------------------------------------------------------------------------

QEMU 2.12.0 monitor - type 'help' for more information
(qemu)
Red Hat Enterprise Linux Server 7.6 Beta (Maipo)
Kernel 4.14.0-66.el7a.ppc64le on an ppc64le

localhost login:
(qemu)
(qemu) object_add memory-backend-ram,id=mem1,size=10G
(qemu) device_add pc-dimm,id=dimm1,memdev=mem1
(qemu) [   15.113583] pseries-hotplug-mem: Attempting to hot-add 40 LMB(s) at index 80000020
[   15.162212] lpar: Attempting to resize HPT to shift 24
[   15.358036] lpar: Hash collision while resizing HPT
[   15.358156] Unable to resize hash page table to target order 24: -28
[   15.396661] Built 2 zonelists, mobility grouping on.  Total pages: 126077
[   15.396718] Policy zone: Normal
[   15.396976] lpar: Attempting to resize HPT to shift 24
[   15.570240] lpar: Hash collision while resizing HPT
[   15.570373] Unable to resize hash page table to target order 24: -28
[   15.608050] lpar: Attempting to resize HPT to shift 24
[   15.766930] lpar: Hash collision while resizing HPT
[   15.767051] Unable to resize hash page table to target order 24: -28
[   15.804494] lpar: Attempting to resize HPT to shift 24
[   15.984056] lpar: Hash collision while resizing HPT
[   15.984172] Unable to resize hash page table to target order 24: -28
[   16.021835] lpar: Attempting to resize HPT to shift 24
[   16.199397] lpar: Hash collision while resizing HPT
[   16.199505] Unable to resize hash page table to target order 24: -28
[   16.237830] lpar: Attempting to resize HPT to shift 24
[   16.388882] lpar: Hash collision while resizing HPT
[   16.388997] Unable to resize hash page table to target order 24: -28
[   16.427306] lpar: Attempting to resize HPT to shift 24
[   16.597805] lpar: Hash collision while resizing HPT
[   16.597919] Unable to resize hash page table to target order 24: -28
[   16.635939] lpar: Attempting to resize HPT to shift 24
[   16.794841] lpar: Hash collision while resizing HPT
[   16.794954] Unable to resize hash page table to target order 24: -28
[   16.832693] lpar: Attempting to resize HPT to shift 24
[   17.013998] lpar: Hash collision while resizing HPT
[   17.014112] Unable to resize hash page table to target order 24: -28
[   17.051680] lpar: Attempting to resize HPT to shift 24
[   17.222303] lpar: Hash collision while resizing HPT
[   17.222428] Unable to resize hash page table to target order 24: -28
[   17.259540] lpar: Attempting to resize HPT to shift 24
[   17.412989] lpar: Hash collision while resizing HPT
[   17.413502] Unable to resize hash page table to target order 24: -28
[   17.450431] lpar: Attempting to resize HPT to shift 24
[   17.612244] lpar: Hash collision while resizing HPT
[   17.612397] Unable to resize hash page table to target order 24: -28
[   17.649777] lpar: Attempting to resize HPT to shift 24
[   17.802082] lpar: Hash collision while resizing HPT
[   17.802193] Unable to resize hash page table to target order 24: -28
[   17.840878] lpar: Attempting to resize HPT to shift 24
[   17.997120] lpar: Hash collision while resizing HPT
[   17.997235] Unable to resize hash page table to target order 24: -28
[   18.035753] lpar: Attempting to resize HPT to shift 24
[   18.195585] lpar: Hash collision while resizing HPT
[   18.195706] Unable to resize hash page table to target order 24: -28
[   18.234865] lpar: Attempting to resize HPT to shift 24
[   18.396867] lpar: Hash collision while resizing HPT
[   18.396986] Unable to resize hash page table to target order 24: -28
[   18.434821] lpar: Attempting to resize HPT to shift 24
[   18.612423] lpar: Hash collision while resizing HPT
[   18.612514] Unable to resize hash page table to target order 24: -28
[   18.649944] lpar: Attempting to resize HPT to shift 24
[   18.796310] lpar: Hash collision while resizing HPT
[   18.796408] Unable to resize hash page table to target order 24: -28
[   18.834245] lpar: Attempting to resize HPT to shift 24
[   18.984514] lpar: Hash collision while resizing HPT
[   18.984616] Unable to resize hash page table to target order 24: -28
[   19.022863] lpar: Attempting to resize HPT to shift 24
[   19.173941] lpar: Hash collision while resizing HPT
[   19.174047] Unable to resize hash page table to target order 24: -28
[   19.212657] lpar: Attempting to resize HPT to shift 24
[   19.363605] lpar: Hash collision while resizing HPT
[   19.363703] Unable to resize hash page table to target order 24: -28
[   19.402957] lpar: Attempting to resize HPT to shift 24
[   19.569392] lpar: Hash collision while resizing HPT
[   19.569512] Unable to resize hash page table to target order 24: -28
[   19.607091] lpar: Attempting to resize HPT to shift 24
[   19.769003] lpar: Hash collision while resizing HPT
[   19.769112] Unable to resize hash page table to target order 24: -28
[   19.806755] lpar: Attempting to resize HPT to shift 24
[   19.959782] lpar: Hash collision while resizing HPT
[   19.959901] Unable to resize hash page table to target order 24: -28
[   19.997405] lpar: Attempting to resize HPT to shift 24
[   20.149505] lpar: Hash collision while resizing HPT
[   20.149632] Unable to resize hash page table to target order 24: -28
[   20.187113] lpar: Attempting to resize HPT to shift 24
[   20.341638] lpar: Hash collision while resizing HPT
[   20.341744] Unable to resize hash page table to target order 24: -28
[   20.378898] lpar: Attempting to resize HPT to shift 24
[   20.527972] lpar: Hash collision while resizing HPT
[   20.528072] Unable to resize hash page table to target order 24: -28
[   20.564706] lpar: Attempting to resize HPT to shift 24
[   20.720252] lpar: Hash collision while resizing HPT
[   20.720401] Unable to resize hash page table to target order 24: -28
[   20.758219] lpar: Attempting to resize HPT to shift 24
[   20.916414] lpar: Hash collision while resizing HPT
[   20.916543] Unable to resize hash page table to target order 24: -28
[   20.954624] lpar: Attempting to resize HPT to shift 24
[   21.106385] lpar: Hash collision while resizing HPT
[   21.106509] Unable to resize hash page table to target order 24: -28
[   21.144648] lpar: Attempting to resize HPT to shift 24
[   21.310382] lpar: Hash collision while resizing HPT
[   21.310489] Unable to resize hash page table to target order 24: -28
[   21.348800] lpar: Attempting to resize HPT to shift 24
[   21.497243] lpar: Hash collision while resizing HPT
[   21.497375] Unable to resize hash page table to target order 24: -28
[   21.837664] pseries-hotplug-mem: Memory at 200000000 (drc index 80000020) was hot-added
[   21.837745] pseries-hotplug-mem: Memory at 210000000 (drc index 80000021) was hot-added
[   21.837807] pseries-hotplug-mem: Memory at 220000000 (drc index 80000022) was hot-added
[   21.837868] pseries-hotplug-mem: Memory at 230000000 (drc index 80000023) was hot-added
[   21.837930] pseries-hotplug-mem: Memory at 240000000 (drc index 80000024) was hot-added
[   21.837990] pseries-hotplug-mem: Memory at 250000000 (drc index 80000025) was hot-added
[   21.838051] pseries-hotplug-mem: Memory at 260000000 (drc index 80000026) was hot-added
[   21.838383] pseries-hotplug-mem: Memory at 270000000 (drc index 80000027) was hot-added
[   21.838452] pseries-hotplug-mem: Memory at 280000000 (drc index 80000028) was hot-added
[   21.838515] pseries-hotplug-mem: Memory at 290000000 (drc index 80000029) was hot-added
[   21.838576] pseries-hotplug-mem: Memory at 2a0000000 (drc index 8000002a) was hot-added
[   21.838638] pseries-hotplug-mem: Memory at 2b0000000 (drc index 8000002b) was hot-added
[   21.838700] pseries-hotplug-mem: Memory at 2c0000000 (drc index 8000002c) was hot-added
[   21.838764] pseries-hotplug-mem: Memory at 2d0000000 (drc index 8000002d) was hot-added
[   21.838824] pseries-hotplug-mem: Memory at 2e0000000 (drc index 8000002e) was hot-added
[   21.838886] pseries-hotplug-mem: Memory at 2f0000000 (drc index 8000002f) was hot-added
[   21.838947] pseries-hotplug-mem: Memory at 300000000 (drc index 80000030) was hot-added
[   21.839008] pseries-hotplug-mem: Memory at 310000000 (drc index 80000031) was hot-added
[   21.839285] pseries-hotplug-mem: Memory at 320000000 (drc index 80000032) was hot-added
[   21.839349] pseries-hotplug-mem: Memory at 330000000 (drc index 80000033) was hot-added
[   21.839410] pseries-hotplug-mem: Memory at 340000000 (drc index 80000034) was hot-added
[   21.839470] pseries-hotplug-mem: Memory at 350000000 (drc index 80000035) was hot-added
[   21.839531] pseries-hotplug-mem: Memory at 360000000 (drc index 80000036) was hot-added
[   21.839592] pseries-hotplug-mem: Memory at 370000000 (drc index 80000037) was hot-added
[   21.839653] pseries-hotplug-mem: Memory at 380000000 (drc index 80000038) was hot-added
[   21.839713] pseries-hotplug-mem: Memory at 390000000 (drc index 80000039) was hot-added
[   21.839774] pseries-hotplug-mem: Memory at 3a0000000 (drc index 8000003a) was hot-added
[   21.839834] pseries-hotplug-mem: Memory at 3b0000000 (drc index 8000003b) was hot-added
[   21.839895] pseries-hotplug-mem: Memory at 3c0000000 (drc index 8000003c) was hot-added
[   21.839956] pseries-hotplug-mem: Memory at 3d0000000 (drc index 8000003d) was hot-added
[   21.840017] pseries-hotplug-mem: Memory at 3e0000000 (drc index 8000003e) was hot-added
[   21.840077] pseries-hotplug-mem: Memory at 3f0000000 (drc index 8000003f) was hot-added
[   21.840138] pseries-hotplug-mem: Memory at 400000000 (drc index 80000040) was hot-added
[   21.840199] pseries-hotplug-mem: Memory at 410000000 (drc index 80000041) was hot-added
[   21.840259] pseries-hotplug-mem: Memory at 420000000 (drc index 80000042) was hot-added
[   21.840320] pseries-hotplug-mem: Memory at 430000000 (drc index 80000043) was hot-added
[   21.840381] pseries-hotplug-mem: Memory at 440000000 (drc index 80000044) was hot-added
[   21.840442] pseries-hotplug-mem: Memory at 450000000 (drc index 80000045) was hot-added
[   21.840503] pseries-hotplug-mem: Memory at 460000000 (drc index 80000046) was hot-added
[   21.840563] pseries-hotplug-mem: Memory at 470000000 (drc index 80000047) was hot-added

(qemu)
(qemu)
(qemu)
(qemu)
(qemu) info numa
2 nodes
node 0 cpus: 0 1
node 0 size: 14336 MB
node 0 plugged: 10240 MB
node 1 cpus: 2 3
node 1 size: 4096 MB
node 1 plugged: 0 MB
(qemu) device_del dimm1
(qemu) [   41.438153] pseries-hotplug-mem: Attempting to hot-remove 40 LMB(s) at 80000020
[   41.438253] pseries-hotplug-mem: Memory indexed-count-remove failed, adding any removed LMBs

(qemu)
(qemu)
(qemu)
(qemu) info numa
2 nodes
node 0 cpus: 0 1
node 0 size: 14336 MB
node 0 plugged: 10240 MB
node 1 cpus: 2 3
node 1 size: 4096 MB
node 1 plugged: 0 MB
(qemu) device_del dimm1
Memory unplug already in progress for device dimm1
(qemu)
(qemu)
(qemu) device_add pc-dimm,id=dimm1,memdev=mem1
Duplicate ID 'dimm1' for device
Try "help device_add" for more information
(qemu)

*** after guest reboot ****

Red Hat Enterprise Linux Server 7.6 Beta (Maipo)
Kernel 4.14.0-66.el7a.ppc64le on an ppc64le

localhost log
(qemu) 
(qemu) device_del dimm1
Device 'dimm1' not found
(qemu) info numa
2 nodes
node 0 cpus: 0 1
node 0 size: 4096 MB
node 0 plugged: 0 MB
node 1 cpus: 2 3
node 1 size: 4096 MB
node 1 plugged: 0 MB
(qemu) device_add pc-dimm,id=dimm1,memdev=mem1
Comment 9 Qunfang Zhang 2018-06-06 00:40:04 UTC 
Hi, Min

Any tips to reproduce this bug in comment 0?  Thanks.
Comment 10 Min Deng 2018-06-08 02:27:11 UTC 
Hi Serhii,
   It looks like you used the newer builds so could you please try  the following old builds mentioned in comment0 ? Thanks,any issues please let me know.
   kernel-3.10.0-823.el7.ppc64le (host and guest)
   qemu-kvm-rhev-2.10.0-13.el7.ppc64le
Min
Comment 11 Min Deng 2018-06-08 05:01:44 UTC 


(In reply to Min Deng from comment #10)
> Hi Serhii,
>    It looks like you used the newer builds so could you please try  the
> following old builds mentioned in comment0 ? Thanks,any issues please let me
> know.
>    kernel-3.10.0-823.el7.ppc64le (host and guest)
>    qemu-kvm-rhev-2.10.0-13.el7.ppc64le
> Min

Besides that,the original problem do happen with the old builds.But now,I have to say it could *not* be reproducible with the latest builds any more.Thanks,any problem let me know.
kernel-3.10.0-901.el7.ppc64le - guest
kernel- 3.10.0-900.el7.ppc64le - host
qemu-kvm-rhev-2.12.0-3.el7.ppc64le
Comment 12 Min Deng 2018-06-11 05:23:24 UTC 
Hi developer.
   QE reported a bug which was similar with comment 8's and please feel free to update it,Bug 1589647,thanks.
Min
Comment 13 David Gibson 2018-06-13 03:12:05 UTC 
Based on comment 11, this no longer reproduces.

It's probably been fixed upstream, and we've collected the fix with our rebase.
Note You need to log in before you can comment on or make changes to this bug.