Bug 2086499

Summary: dmesg warn and error when boot a rhel9.1.0 guest
Product: Red Hat Enterprise Linux 9 Reporter: Yiqian Wei <yiwei>
Component: kernelAssignee: Virtualization Maintenance <virt-maint>
kernel sub component: KVM QA Contact: Yiqian Wei <yiwei>
Status: CLOSED MIGRATED Docs Contact:
Severity: low    
Priority: low CC: bhu, chayang, coli, jinzhao, juzhang, nilal, virt-maint, vkuznets, yanghliu, yiwei
Version: 9.1Keywords: MigratedToJIRA, Triaged
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-08-09 16:20:38 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: 2004876    
Bug Blocks:    

Description Yiqian Wei 2022-05-16 10:55:49 UTC
Description of problem:
Boot a rhel9.1.0 guest,check dmesg with "dmesg --level=err,warn" in guest and found warn and error messages

Version-Release number of selected component (if applicable):
host version:
kernel-5.14.0-92.el9.x86_64
qemu-kvm-7.0.0-1.el9.x86_64
edk2-ovmf-20220221gitb24306f15d-1.el9.noarch
guest: rhel9.1.0(kernel-5.14.0-92.el9.x86_64)

How reproducible:
2/2

Steps to Reproduce:
1.boot a guest with q35 + edk2-ovmf
/usr/libexec/qemu-kvm \
    -name 'avocado-vt-vm1'  \
    -sandbox on  \
    -blockdev node-name=file_ovmf_code,driver=file,filename=/usr/share/edk2/ovmf/OVMF_CODE.secboot.fd,auto-read-only=on,discard=unmap \
    -blockdev node-name=drive_ovmf_code,driver=raw,read-only=on,file=file_ovmf_code \
    -blockdev node-name=file_ovmf_vars,driver=file,filename=/home/OVMF_VARS.fd,auto-read-only=on,discard=unmap \
    -blockdev node-name=drive_ovmf_vars,driver=raw,read-only=off,file=file_ovmf_vars \
    -machine q35,memory-backend=mem-machine_mem,pflash0=drive_ovmf_code,pflash1=drive_ovmf_vars \
    -device pcie-root-port,id=pcie-root-port-0,multifunction=on,bus=pcie.0,addr=0x1,chassis=1 \
    -device pcie-pci-bridge,id=pcie-pci-bridge-0,addr=0x0,bus=pcie-root-port-0  \
    -device i6300esb,id=wdt0,bus=pcie-pci-bridge-0 \
    -watchdog-action reset \
    -nodefaults \
    -device VGA,bus=pcie.0,addr=0x2 \
    -m 12G \
    -object memory-backend-ram,size=12G,id=mem-machine_mem  \
    -smp 10,maxcpus=10,cores=5,threads=1,sockets=2  \
    -cpu IvyBridge,enforce \
    -device pcie-root-port,id=pcie-root-port-1,port=0x1,addr=0x1.0x1,bus=pcie.0,chassis=2 \
    -device qemu-xhci,id=usb1,bus=pcie-root-port-1,addr=0x0 \
    -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \
    -device pcie-root-port,id=pcie-root-port-2,port=0x2,addr=0x1.0x2,bus=pcie.0,chassis=3 \
    -device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pcie-root-port-2,addr=0x0 \
    -blockdev node-name=file_image1,driver=file,auto-read-only=on,discard=unmap,aio=threads,filename=/home/rhel9.1-ovmf.qcow2,cache.direct=on,cache.no-flush=off \
    -blockdev node-name=drive_image1,driver=qcow2,read-only=off,cache.direct=on,cache.no-flush=off,file=file_image1 \
    -device scsi-hd,id=image1,drive=drive_image1,write-cache=on \
    -device pcie-root-port,id=pcie-root-port-3,port=0x3,addr=0x1.0x3,bus=pcie.0,chassis=4 \
    -device virtio-net-pci,mac=9a:df:ca:53:c2:69,id=idz43iXV,netdev=idPOEPyA,bus=pcie-root-port-3,addr=0x0  \
    -netdev tap,id=idPOEPyA,vhost=on   \
    -vnc :0  \
    -rtc base=utc,clock=host,driftfix=slew  \
    -boot menu=off,order=cdn,once=c,strict=off \
    -enable-kvm \
    -monitor stdio  \
    -qmp tcp:0:4444,server=on,wait=off \

2.check dmesg in guest
# dmesg --level=err,warn 
OR
# dmesg -T -l 0,1,2,3,4 | grep .

Actual results:
After step2, found the following message: 
# dmesg --level=err,warn
[    0.161379]   #2
[    0.163582]   #3
[    0.165382]   #4
[    0.167371]   #5
[    0.170017]   #6
[    0.172375]   #7
[    0.174380]   #8
[    0.176373]   #9
[    0.499586] shpchp 0000:01:00.0: pci_hp_register failed with error -16
[    0.500039] shpchp 0000:01:00.0: Slot initialization failed
[    1.892030] device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
[    2.165834] sd 0:0:0:0: Power-on or device reset occurred

Expected results:
After step2, There should not have warn and fail in dmesg

Additional info:
1) boot a guest with max memory, also hit the same issue.
2) There is a similar error:
Bug 2004876 - Failed message when boot guest with pcie-pci-bridge

Comment 5 Nitesh Narayan Lal 2022-05-31 13:26:18 UTC
Keeping this in the backlog.
We will wait for Julia to do the initial investigation for Bug 2004876 before deciding the next steps for this.

Comment 8 Nitesh Narayan Lal 2023-07-18 08:22:34 UTC
Migrating this issue to JIRA.