Bug 1750200
Summary: | [RHEL8.1][QEMU4.1]boot up guest with vf device,then system_reset guest,error prompt(qemu-kvm: Can't allocate MSIs for device 2800: IRQ 4904 is not free) | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux Advanced Virtualization | Reporter: | Minjia Cai <micai> |
Component: | qemu-kvm | Assignee: | David Gibson <dgibson> |
Status: | CLOSED ERRATA | QA Contact: | Minjia Cai <micai> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 8.1 | CC: | bugproxy, ddepaula, dgibson, hannsj_uhl, knoel, mdeng, micai, ngu, qzhang, virt-maint, yihyu, zhenyzha |
Target Milestone: | rc | Keywords: | Patch, Regression |
Target Release: | 8.1 | ||
Hardware: | ppc64le | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | qemu-kvm-4.1.0-9.module+el8.1.0+4210+23b2046a | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-11-06 07:19:21 UTC | Type: | Bug |
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: | |||
Bug Blocks: | 1624641 |
Description
Minjia Cai
2019-09-09 02:46:23 UTC
Thanks for lending me the machine Minjia. A bisect fairly quickly found an upstream fix that makes perfect sense, but which I'd forgotten about: ea52074d3a1c "spapr/pci: Free MSIs during reset" I'm building a draft fix at: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=23431036 According to comment0 ,I have test it many times but did not encounter this problem, So change the robust state of the bug to verify host: [root@ibm-p9wr-22 micai]# rpm -qa|grep qemu qemu-kvm-4.1.0-9.module+el8.1.0+4210+23b2046a.ppc64le [root@ibm-p9wr-22 ~]# uname -r 4.18.0-141.el8.ppc64le guest: Red Hat Enterprise Linux 8.1 Beta (Ootpa) Kernel 4.18.0-141.el8.ppc64le on an ppc64le 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, 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/RHBA-2019:3723 |