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 2026834 - [ppc64le]Hardly install a rhel8.6 guest with iso by manual
Summary: [ppc64le]Hardly install a rhel8.6 guest with iso by manual
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: qemu-kvm
Version: 8.6
Hardware: All
OS: All
high
high
Target Milestone: rc
: ---
Assignee: Greg Kurz
QA Contact: Min Deng
URL:
Whiteboard:
Depends On: 2027716
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-26 05:31 UTC by Min Deng
Modified: 2022-05-10 13:37 UTC (History)
10 users (show)

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:
Clone Of:
Environment:
Last Closed: 2022-05-10 13:24:19 UTC
Type: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-104006 0 None None None 2021-11-26 05:31:54 UTC

Description Min Deng 2021-11-26 05:31:11 UTC 
Description of problem:
Hardly install a rhel8.6 guest with iso by manual 

Version-Release number of selected component (if applicable):
kernel-4.18.0-352.el8.ppc64le
qemu-kvm-6.2.0-1.rc1.scrmod+el8.6.0+13325+d4e3491c.wrb21117.ppc64le
SLOF-20210217-1.module+el8.6.0+12861+13975d62.noarch

How reproducible:
6/6
Steps to Reproduce:
1.wanted to install a guest by manual , tried several time but it wasn't successfully.
/usr/libexec/qemu-kvm -name avocado-vt-vm1 -sandbox on -machine pseries,cap-htm=on -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,nowait,path=/tmp/tt,id=chardev_serial0 -device spapr-vty,id=serial0,reg=0x30000000,chardev=chardev_serial0 -device virtio-scsi-pci,id=scsi0 -drive file=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=RHEL-8.6.0-20211124.0-ppc64le-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=0x3 -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

2.select minimal installation, and also you can choose to install development tools and so on so forth

3.click next -> start the installation

Actual results:
Tried at least 6 times with both rhel79 and rhel86 iso, I never succeeded in doing it since every time the installation hung up.

Expected results:
Installation finished successfully

Additional info:
It should be a regression issue because it's not reproducible after I relegated build to qemu-kvm-6.1.0-4.module+el8.6.0+13039+4b81a1dc.ppc64le on the *same* host. The installation completed on the old build successfully.
Comment 2 Min Deng 2021-11-26 05:35:29 UTC 
didn't try it on x86 yet and will update the result here.
Comment 3 Min Deng 2021-11-29 03:08:57 UTC 
Hi yiwei,
Could you please help to check it on x86 side ? Thanks a lot !

Best regards
Min
Comment 4 Yiqian Wei 2021-11-30 03:11:44 UTC 
(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 \
Comment 5 Min Deng 2021-11-30 03:15:05 UTC 
(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.
Comment 6 David Gibson 2021-12-13 04:48:01 UTC 
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)
Comment 7 Min Deng 2021-12-13 06:49:16 UTC 
Working on it now.
Comment 8 Min Deng 2021-12-16 08:55:14 UTC 
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
Comment 9 Min Deng 2021-12-16 09:10:39 UTC 
(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.
Comment 10 David Gibson 2021-12-20 02:12:16 UTC 
> 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?
Comment 11 Greg Kurz 2021-12-22 10:31:57 UTC 
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>
Comment 12 Greg Kurz 2021-12-22 10:59:39 UTC 
(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.
Comment 13 John Ferlan 2021-12-22 18:01:48 UTC 
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.
Comment 14 Min Deng 2021-12-23 01:50:30 UTC 
QE will try it on qemu-kvm 6.2 build, thanks.
Comment 15 Yanan Fu 2021-12-24 02:49:20 UTC 
QE bot(pre verify): Set 'Verified:Tested,SanityOnly' as gating/tier1 test pass.
Comment 16 Min Deng 2021-12-24 07:59:07 UTC 
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.
Comment 19 Min Deng 2022-01-07 03:30:32 UTC 
Base on comment 16 and move it to be verified, thanks a lot
Comment 21 errata-xmlrpc 2022-05-10 13:24:19 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 (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
Note You need to log in before you can comment on or make changes to this bug.