Bug 2026834
| Summary: | [ppc64le]Hardly install a rhel8.6 guest with iso by manual | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Min Deng <mdeng> |
| Component: | qemu-kvm | Assignee: | Greg Kurz <gkurz> |
| qemu-kvm sub component: | General | QA Contact: | Min Deng <mdeng> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | high | ||
| Priority: | high | CC: | dgibson, gkurz, jinzhao, jmaloy, lijin, mdeng, ngu, virt-maint, xuma, yiwei |
| Version: | 8.6 | Keywords: | Regression, Triaged |
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | qemu-kvm-6.2.0-1.module+el8.6.0+13725+61ae1949 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-05-10 13:24:19 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 2027716 | ||
| Bug Blocks: | |||
|
Description
Min Deng
2021-11-26 05:31:11 UTC
didn't try it on x86 yet and will update the result here. Hi yiwei, Could you please help to check it on x86 side ? Thanks a lot ! Best regards Min (In reply to Min Deng from comment #3) > Hi yiwei, > Could you please help to check it on x86 side ? Thanks a lot ! Cannot reproduce this bug on x86 side. host version: kernel-4.18.0-353.el8.x86_64 qemu-kvm-6.2.0-1.rc1.scrmod+el8.6.0+13325+d4e3491c.wrb21117.x86_64 seabios-1.14.0-1.module+el8.6.0+12861+13975d62.x86_64 guest: rhel8.6.0 boot guest with cli /usr/libexec/qemu-kvm \ -name avocado-vt-vm1 \ -sandbox on \ -machine pc \ -nodefaults \ -device VGA,bus=pci.0,addr=0x2 \ -m 8192 \ -smp 8,maxcpus=8,cores=4,threads=1,sockets=2 \ -cpu host \ -chardev socket,server=on,wait=off,path=/tmp/tt,id=chardev_serial0 \ -device virtio-scsi-pci,id=scsi0 \ -drive file=/home/rhel86.qcow2,if=none,id=drive-scsi-disk0,format=qcow2,werror=stop,rerror=stop,aio=native,cache=none \ -device scsi-hd,bus=scsi0.0,drive=drive-scsi-disk0,id=scsi-disk0,bootindex=0 \ -drive file=/root/RHEL-8.6.0-20211124.0-x86_64-dvd1.iso,if=none,id=drive-data-disk,format=raw,media=cdrom,cache=none,aio=native,werror=stop,rerror=stop \ -device scsi-cd,bus=scsi0.0,drive=drive-data-disk,id=iso-disk,bootindex=1 \ -vnc :11 \ -rtc base=utc,clock=host \ -boot menu=off,order=cdn,once=c,strict=off \ -enable-kvm \ -monitor stdio \ -device qemu-xhci,id=usb1,bus=pci.0,addr=0x9 \ -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \ -device usb-kbd,id=usbkbd,bus=usb1.0 \ -device virtio-net-pci,mac=9a:11:0a:0b:0c:0d,id=idLLoQ97,vectors=4,netdev=hostnet0,bus=pci.0,addr=05,bootindex=2 \ -netdev tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup,downscript=/etc/qemu-ifdown \ (In reply to Yiqian Wei from comment #4) > (In reply to Min Deng from comment #3) > > Hi yiwei, > > Could you please help to check it on x86 side ? Thanks a lot ! > > > Cannot reproduce this bug on x86 side. > > host version: > kernel-4.18.0-353.el8.x86_64 > qemu-kvm-6.2.0-1.rc1.scrmod+el8.6.0+13325+d4e3491c.wrb21117.x86_64 > seabios-1.14.0-1.module+el8.6.0+12861+13975d62.x86_64 > guest: rhel8.6.0 > > boot guest with cli > /usr/libexec/qemu-kvm \ > -name avocado-vt-vm1 \ > -sandbox on \ > -machine pc \ > -nodefaults \ > -device VGA,bus=pci.0,addr=0x2 \ > -m 8192 \ > -smp 8,maxcpus=8,cores=4,threads=1,sockets=2 \ > -cpu host \ > -chardev socket,server=on,wait=off,path=/tmp/tt,id=chardev_serial0 \ > -device virtio-scsi-pci,id=scsi0 \ > -drive > file=/home/rhel86.qcow2,if=none,id=drive-scsi-disk0,format=qcow2,werror=stop, > rerror=stop,aio=native,cache=none \ > -device > scsi-hd,bus=scsi0.0,drive=drive-scsi-disk0,id=scsi-disk0,bootindex=0 \ > -drive > file=/root/RHEL-8.6.0-20211124.0-x86_64-dvd1.iso,if=none,id=drive-data-disk, > format=raw,media=cdrom,cache=none,aio=native,werror=stop,rerror=stop \ > -device > scsi-cd,bus=scsi0.0,drive=drive-data-disk,id=iso-disk,bootindex=1 \ > -vnc :11 \ > -rtc base=utc,clock=host \ > -boot menu=off,order=cdn,once=c,strict=off \ > -enable-kvm \ > -monitor stdio \ > -device qemu-xhci,id=usb1,bus=pci.0,addr=0x9 \ > -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \ > -device usb-kbd,id=usbkbd,bus=usb1.0 \ > -device > virtio-net-pci,mac=9a:11:0a:0b:0c:0d,id=idLLoQ97,vectors=4,netdev=hostnet0, > bus=pci.0,addr=05,bootindex=2 \ > -netdev > tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup,downscript=/etc/qemu-ifdown \ Thanks for Yiqian's effort. I mark it as ppc only now. Unfortunately the screenshot doesn't tell us much about what's going wrong. Here are some things to check: 1. Does the problem occur if you install in text mode (e.g. with no VGA device attached to the VM) 2. Does the problem occur if you increase the amount of memory given to the gest (say to 32G) Working on it now. At first, I still can reproduce the issue on host > 1. Does the problem occur if you install in text mode (e.g. with no VGA > device attached to the VM) The text mode installation menu isn't available in this iso while trying it by manual. > > 2. Does the problem occur if you increase the amount of memory given to the > guest (say to 32G) with 8G/32 memory, I can still reproduce the problem. Server: RHEL-8/RHEL-8.6.0-20211211.3/ [root@ibm-p9wr-06 ~]# uname -r 4.18.0-353.el8.ppc64le [root@ibm-p9wr-06 ~]# rpm -qa|grep qemu-kvm qemu-kvm-docs-6.2.0-1.rc1.scrmod+el8.6.0+13325+d4e3491c.wrb21117.ppc64le qemu-kvm-block-curl-6.2.0-1.rc1.scrmod+el8.6.0+13325+d4e3491c.wrb21117.ppc64le qemu-kvm-core-6.2.0-1.rc1.scrmod+el8.6.0+13325+d4e3491c.wrb21117.ppc64le qemu-kvm-common-6.2.0-1.rc1.scrmod+el8.6.0+13325+d4e3491c.wrb21117.ppc64le qemu-kvm-block-iscsi-6.2.0-1.rc1.scrmod+el8.6.0+13325+d4e3491c.wrb21117.ppc64le qemu-kvm-block-ssh-6.2.0-1.rc1.scrmod+el8.6.0+13325+d4e3491c.wrb21117.ppc64le qemu-kvm-6.2.0-1.rc1.scrmod+el8.6.0+13325+d4e3491c.wrb21117.ppc64le qemu-kvm-block-rbd-6.2.0-1.rc1.scrmod+el8.6.0+13325+d4e3491c.wrb21117.ppc64le (In reply to Min Deng from comment #8) > At first, I still can reproduce the issue on host > > > 1. Does the problem occur if you install in text mode (e.g. with no VGA > > device attached to the VM) > > The text mode installation menu isn't available in this iso while trying it > by manual. > > > > 2. Does the problem occur if you increase the amount of memory given to the > > guest (say to 32G) > > with 8G/32 memory, I can still reproduce the problem. > > Server: RHEL-8/RHEL-8.6.0-20211211.3/ > [root@ibm-p9wr-06 ~]# uname -r > 4.18.0-353.el8.ppc64le > [root@ibm-p9wr-06 ~]# rpm -qa|grep qemu-kvm > qemu-kvm-docs-6.2.0-1.rc1.scrmod+el8.6.0+13325+d4e3491c.wrb21117.ppc64le > qemu-kvm-block-curl-6.2.0-1.rc1.scrmod+el8.6.0+13325+d4e3491c.wrb21117. > ppc64le > qemu-kvm-core-6.2.0-1.rc1.scrmod+el8.6.0+13325+d4e3491c.wrb21117.ppc64le > qemu-kvm-common-6.2.0-1.rc1.scrmod+el8.6.0+13325+d4e3491c.wrb21117.ppc64le > qemu-kvm-block-iscsi-6.2.0-1.rc1.scrmod+el8.6.0+13325+d4e3491c.wrb21117. > ppc64le > qemu-kvm-block-ssh-6.2.0-1.rc1.scrmod+el8.6.0+13325+d4e3491c.wrb21117.ppc64le > qemu-kvm-6.2.0-1.rc1.scrmod+el8.6.0+13325+d4e3491c.wrb21117.ppc64le > qemu-kvm-block-rbd-6.2.0-1.rc1.scrmod+el8.6.0+13325+d4e3491c.wrb21117.ppc64le by the way, at this time, qemu-kvm process stuck and had to kill it on the host. Thanks. > The text mode installation menu isn't available in this iso while trying it by manual.
That seems concerning: it would be typical for power VMs not to use a graphics device at all. What happens if you remove the VGA device from the VM?
I've reproduced the issue at last. QEMU's main event loop thread is looping forever in notifier_list_notify() : (gdb) bt #0 0x0000000136618888 in vnc_clipboard_notify (notifier=0x149953bd8, data=0x148ec9c30) at ../ui/vnc-clipboard.c:193 #1 0x0000000136b3290c in notifier_list_notify (list=<optimized out>, data=0x148ec9c30) at ../util/notify.c:39 #2 0x00000001365ec5f0 in qemu_clipboard_update (info=<optimized out>) at ../ui/clipboard.c:50 #3 0x0000000136618c78 in vnc_client_cut_text_ext (vs=<optimized out>, len=<optimized out>, flags=<optimized out>, data=<optimized out>) at ../ui/vnc-clipboard.c:256 #4 0x00000001366027a0 in protocol_client_msg (vs=0x1499438e0, data=0x149953c20 "\006", len=<optimized out>) at ../ui/vnc.c:2459 #5 0x00000001365ffa7c in vnc_client_read (vs=0x1499438e0) at ../ui/vnc.c:1621 #6 vnc_client_io (ioc=<optimized out>, condition=<optimized out>, opaque=0x1499438e0) at ../ui/vnc.c:1649 #7 0x0000000136974ff8 in qio_channel_fd_source_dispatch (source=<optimized out>, callback=<optimized out>, user_data=<optimized out>) at ../io/channel-watch.c:84 #8 0x00007fff99d8945c in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #9 0x0000000136b51e88 in glib_pollfds_poll () at ../util/main-loop.c:232 #10 os_host_main_loop_wait (timeout=<optimized out>) at ../util/main-loop.c:255 #11 main_loop_wait (nonblocking=<optimized out>) at ../util/main-loop.c:531 #12 0x0000000136836e98 in qemu_main_loop () at ../softmmu/runstate.c:726 #13 0x00000001365dfe60 in main (argc=<optimized out>, argv=<optimized out>, envp=<optimized out>) at ../softmmu/main.c:50 (gdb) p notifier $8 = (Notifier *) 0x149953bd8 (gdb) p notifier->node.le_next $9 = (struct Notifier *) 0x149953bd8 It is likely the issue mentioned here: https://patchwork.ozlabs.org/project/qemu-devel/patch/20211110103800.2266729-1-vsementsov@virtuozzo.com/ Fix is now upstream and should be backported : commit 2e572baf659f5a457c876c6b2d02a217afb401c5 Author: Vladimir Sementsov-Ogievskiy <vsementsov> Date: Wed Nov 10 11:38:00 2021 +0100 ui/vnc-clipboard: fix adding notifier twice vnc_server_cut_text_caps() is not guaranteed to be called only once. If it called twice, we finally call notifier_list_add() twice with same element. Which leads to loopback QLIST. So, on next notifier_list_notify() we'll loop forever and QEMU stuck. So, let's only register new notifier if it's not yet registered. Note, that similar check is used in vdagent_chr_recv_caps() (before call qemu_clipboard_peer_register()), and also before qemu_clipboard_peer_unregister() call in vdagent_disconnect() and in vnc_disconnect_finish(). Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov> Message-Id: <20211110103800.2266729-1-vsementsov> Signed-off-by: Gerd Hoffmann <kraxel> (In reply to Greg Kurz from comment #11) > > Fix is now upstream and should be backported : > > commit 2e572baf659f5a457c876c6b2d02a217afb401c5 > Author: Vladimir Sementsov-Ogievskiy <vsementsov> > Date: Wed Nov 10 11:38:00 2021 +0100 > > ui/vnc-clipboard: fix adding notifier twice > No need to backport, it came with the 6.2 rebase and is already present in the rhel-8.6.0 branch. Also change HW to All as this isn't ppc specific. Mass update of DTM/ITM to +3 values since the rebase of qemu-6.2 into RHEL 8.6 has been delayed or slowed due to process roadblocks (authentication changes, gating issues). This avoids the DevMissed bot and worse the bot that could come along and strip release+. The +3 was chosen mainly to give a cushion. Also added the qemu-6.2 rebase bug 2027716 as a dependent. QE will try it on qemu-kvm 6.2 build, thanks. QE bot(pre verify): Set 'Verified:Tested,SanityOnly' as gating/tier1 test pass. Tried the bug with the target build qemu-kvm-common-6.2.0-1.module+el8.6.0+13725+61ae1949.ppc64le Following the steps from description of this bug The original issue has gone and the installation could finish successfully. So the bug has been fixed on the target build. Actually, we can move it to be verified. Thanks. Base on comment 16 and move it to be verified, thanks a lot 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 (Moderate: virt:rhel and virt-devel:rhel security, bug fix, and enhancement update), 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://access.redhat.com/errata/RHSA-2022:1759 |