Description of problem: Qemu-kvm core dumped when boot up the guest with "-object memory-backend-ram,host-nodes=0,policy=bind,id=mem-0,size=8192M,prealloc=yes -numa node,memdev=mem-0 ..." Version-Release number of selected component (if applicable): 3.10.53-2020.1.pkvm2_1_1.49.ppc64 qemu-kvm-2.0.0-2.1.pkvm2_1_1.20.40.ppc64 How reproducible: 100% Steps to Reproduce: 1. Start a guest with numa as follows: /usr/bin/qemu-system-ppc64 -name spaprqcow-0209 -machine pseries-2.2,accel=kvm,usb=off -m 32768 -smp 4,sockets=1,cores=4,threads=2 -object memory-backend-ram,host-nodes=0,policy=bind,id=mem-0,size=8192M,prealloc=yes -numa node,memdev=mem-0 -object memory-backend-ram,host-nodes=1,policy=bind,id=mem-1,size=10240M,prealloc=yes -numa node,memdev=mem-1 -object memory-backend-ram,host-nodes=2,policy=bind,id=mem-2,size=11264M,prealloc=yes -numa node,memdev=mem-2 -object memory-backend-ram,host-nodes=3,policy=bind,id=mem-3,size=3072M,prealloc=yes -numa node,memdev=mem-3 -monitor stdio -vnc 0:04 ...-msg timestamp=on ** ERROR:qom/object.c:437:object_new_with_type: assertion failed: (type != NULL) Aborted (core dumped) Actual results: Qemu-kvm 'Aborted (core dumped) as above Expected results: There is an prompt to say that the the object is not supported Additional info: The bug only occurred on qemu 2.0 while not on qemu 2.1/2.2 and it's just bz 1031978 on x86
------- Comment From fnovak.com 2015-02-12 20:05 EDT------- reverse mirror of RHBZ 1190980 - [PowerKVM] qemu-kvm core dumped when boot up guest with undefined object numa memdev
This one only affects the IBM versions of qemu, not RHEL qemu-kvm-rhev versions, so removing from the RHEL7.2 tracker. Also clearing release flags, since they're meaningless for an IBM bug.
Frank, Any news on this backport?
------- Comment From seg.com 2015-12-10 15:54 EDT------- I see that someone on the Red Hat side changed the severity to "urgent", which is puzzling, since this was closed nine months ago as WONTFIX.
(In reply to IBM Bug Proxy from comment #6) > ------- Comment From seg.com 2015-12-10 15:54 EDT------- > I see that someone on the Red Hat side changed the severity to "urgent", > which is puzzling, since this was closed nine months ago as WONTFIX. The Red Hat side of this bug hasn't been closed yet, also there is no comment why it won't be fixed at this side ... seems like the tickets got out of sync? I guess we should close the Red Hat ticket as well? Could you maybe post the reasons for the WONTFIX again?
------- Comment From seg.com 2016-01-18 16:16 EDT------- It was marked as WONTFIX because it's not a problem in the current version of PowerKVM
According to comment 8, the mirrored bug on the IBM site has been closed as WONTFIX, so I think we should do this with the RH side of the bug ticket as well.