Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
When continue a suspended vm, qemu core dump with info: /hw/core/cpu-sysemu.c:77: int cpu_asidx_from_attrs(CPUState *, MemTxAttrs): Assertion `ret < cpu->num_ases && ret >= 0'
Description of problem: When continue a suspended vm, qemu core dump with info: /hw/core/cpu-sysemu.c:77: int cpu_asidx_from_attrs(CPUState *, MemTxAttrs): Assertion `ret < cpu->num_ases && ret >= 0' Version-Release number of selected component (if applicable): kernel version:5.14.0-160.el9.x86_64 qemu-kvm version:qemu-kvm-7.1.0-11.rc4.el9.preview How reproducible: random Steps to Reproduce: 1.Start guest witch qemu cmdline: /usr/libexec/qemu-kvm \ -S \ -name 'avocado-vt-vm1' \ -sandbox on \ -blockdev node-name=file_ovmf_code,driver=file,filename=/usr/share/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=/root/avocado/data/avocado-vt/avocado-vt-vm1_rhel920-64-virtio_qcow2_filesystem_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 \ -nodefaults \ -device VGA,bus=pcie.0,addr=0x2 \ -m 30720 \ -object memory-backend-ram,size=30720M,id=mem-machine_mem \ -smp 10,maxcpus=10,cores=5,threads=1,dies=1,sockets=2 \ -cpu 'Cascadelake-Server',ss=on,vmx=on,pdcm=on,hypervisor=on,tsc-adjust=on,umip=on,pku=on,md-clear=on,stibp=on,arch-capabilities=on,xsaves=on,ibpb=on,ibrs=on,amd-stibp=on,amd-ssbd=on,rdctl-no=on,ibrs-all=on,skip-l1dfl-vmentry=on,mds-no=on,pschange-mc-no=on,tsx-ctrl=on,hle=off,rtm=off,kvm_pv_unhalt=on \ -chardev socket,id=qmp_id_qmpmonitor1,wait=off,server=on,path=/var/tmp/avocado_s8lt2e_a/monitor-qmpmonitor1-20220905-085659-dbRZWhv9 \ -mon chardev=qmp_id_qmpmonitor1,mode=control \ -chardev socket,id=qmp_id_catch_monitor,wait=off,server=on,path=/var/tmp/avocado_s8lt2e_a/monitor-catch_monitor-20220905-085659-dbRZWhv9 \ -mon chardev=qmp_id_catch_monitor,mode=control \ -device pvpanic,ioport=0x505,id=idF8Z3zs \ -chardev socket,id=chardev_serial0,wait=off,server=on,path=/var/tmp/avocado_s8lt2e_a/serial-serial0-20220905-085659-dbRZWhv9 \ -device isa-serial,id=serial0,chardev=chardev_serial0 \ -chardev socket,id=seabioslog_id_20220905-085659-dbRZWhv9,path=/var/tmp/avocado_s8lt2e_a/seabios-20220905-085659-dbRZWhv9,server=on,wait=off \ -device isa-debugcon,chardev=seabioslog_id_20220905-085659-dbRZWhv9,iobase=0x402 \ -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 \ -blockdev node-name=file_image1,driver=file,auto-read-only=on,discard=unmap,aio=threads,filename=/home/kvm_autotest_root/images/rhel920-64-virtio.qcow2,cache.direct=on,cache.no-flush=off \ -object iothread,id=iothread0 \ -blockdev node-name=drive_image1,driver=qcow2,read-only=off,cache.direct=on,cache.no-flush=off,file=file_image1 \ -device pcie-root-port,id=pcie-root-port-2,port=0x2,addr=0x1.0x2,bus=pcie.0,chassis=3 \ -device virtio-blk-pci,id=image1,drive=drive_image1,bootindex=0,write-cache=on,bus=pcie-root-port-2,addr=0x0,iothread=iothread0 \ -blockdev node-name=file_data,driver=file,auto-read-only=on,discard=unmap,aio=threads,filename=/root/avocado/data/avocado-vt/data.qcow2,cache.direct=on,cache.no-flush=off \ -blockdev node-name=drive_data,driver=qcow2,read-only=off,cache.direct=on,cache.no-flush=off,file=file_data \ -device pcie-root-port,id=pcie-root-port-3,port=0x3,addr=0x1.0x3,bus=pcie.0,chassis=4 \ -device virtio-blk-pci,id=data,drive=drive_data,bootindex=1,write-cache=on,bus=pcie-root-port-3,addr=0x0,iothread=iothread1 \ -device pcie-root-port,id=pcie-root-port-4,port=0x4,addr=0x1.0x4,bus=pcie.0,chassis=5 \ -device virtio-net-pci,mac=9a:2e:fd:1f:0a:36,id=idT01M9z,netdev=id99GZic,bus=pcie-root-port-4,addr=0x0 \ -netdev tap,id=id99GZic,vhost=on,vhostfd=16,fd=9 \ -vnc :0 \ -rtc base=utc,clock=host,driftfix=slew \ -boot menu=off,order=cdn,once=c,strict=off \ -enable-kvm \ -device pcie-root-port,id=pcie_extra_root_port_0,multifunction=on,bus=pcie.0,addr=0x3,chassis=6 2. Continue vm {'execute': 'cont', 'id': 'cNpODhjd'} Actual results: After step2, qemu core dump with info: KVM: entry failed, hardware error 0x80000021 If you're running a guest on an Intel machine without unrestricted mode support, the failure can be most likely due to the guest entering an invalid state for Intel VT. For example, the guest maybe running in big real mode which is not supported on less recent Intel processors. EAX=c78f8db0 EBX=00000000 ECX=801c001c EDX=c78f9480 ESI=841e3e00 EDI=00000200 EBP=80beb9d0 ESP=80beb920 EIP=00008000 EFL=00000002 [-------] CPL=0 II=0 A20=1 SMM=1 HLT=0 ES =0000 00000000 ffffffff 00809300 CS =b100 7ffb1000 ffffffff 00809300 SS =0000 00000000 ffffffff 00809300 DS =0000 00000000 ffffffff 00809300 FS =0000 00000000 ffffffff 00809300 GS =0000 00000000 ffffffff 00809300 LDT=0000 00000000 00000000 00000000 TR =0040 001e0000 00004087 00008b00 GDT= 001de000 0000007f IDT= 00000000 00000000 CR0=00050032 CR2=3b6bfa50 CR3=20e4a002 CR4=00000000 DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 DR6=00000000ffff0ff0 DR7=0000000000000400 EFER=0000000000000000 Code=qemu-kvm: ../hw/core/cpu-sysemu.c:77: int cpu_asidx_from_attrs(CPUState *, MemTxAttrs): Assertion `ret < cpu->num_ases && ret >= 0' failed. /tmp/aexpect_iEA6LMnf/aexpect-j9vf15e4.sh: line 1: 108671 Aborted (core dumped) MALLOC_PERTURB_=1 /usr/libexec/qemu-kvm -S -name 'avocado-vt-vm1' -sandbox on -blockdev node-name=file_ovmf_code,driver=file,filename=/usr/share/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 ... Expected results: Qemu shouldn't coredump when continue vm. Additional info: Coredump file not captured by auto, will try to provide it later once reproduce. Auto script: blockdev_commit_with_ioerror, blockdev_commit_forbidden_actions,blockdev_inc_backup_inconsistent_bitmap.handle_bitmap_with_qmp_cmd,blockdev_mirror_vm_reboot