diff options
| author | Maciej S. Szmigiero | 2022-09-30 17:52:03 +0200 |
|---|---|---|
| committer | Paolo Bonzini | 2022-10-18 13:58:04 +0200 |
| commit | ec19444a53ef221954128e36e1387592a2273dc2 (patch) | |
| tree | ff409bba0e40fed8fc92bf4c99931800927f01ed /configure | |
| parent | hw/scsi/vmw_pvscsi.c: Use device_cold_reset() to reset SCSI devices (diff) | |
| download | qemu-ec19444a53ef221954128e36e1387592a2273dc2.tar.gz qemu-ec19444a53ef221954128e36e1387592a2273dc2.tar.xz qemu-ec19444a53ef221954128e36e1387592a2273dc2.zip | |
hyperv: fix SynIC SINT assertion failure on guest reset
Resetting a guest that has Hyper-V VMBus support enabled triggers a QEMU
assertion failure:
hw/hyperv/hyperv.c:131: synic_reset: Assertion `QLIST_EMPTY(&synic->sint_routes)' failed.
This happens both on normal guest reboot or when using "system_reset" HMP
command.
The failing assertion was introduced by commit 64ddecc88bcf ("hyperv: SControl is optional to enable SynIc")
to catch dangling SINT routes on SynIC reset.
The root cause of this problem is that the SynIC itself is reset before
devices using SINT routes have chance to clean up these routes.
Since there seems to be no existing mechanism to force reset callbacks (or
methods) to be executed in specific order let's use a similar method that
is already used to reset another interrupt controller (APIC) after devices
have been reset - by invoking the SynIC reset from the machine reset
handler via a new x86_cpu_after_reset() function co-located with
the existing x86_cpu_reset() in target/i386/cpu.c.
Opportunistically move the APIC reset handler there, too.
Fixes: 64ddecc88bcf ("hyperv: SControl is optional to enable SynIc") # exposed the bug
Signed-off-by: Maciej S. Szmigiero <maciej.szmigiero@oracle.com>
Message-Id: <cb57cee2e29b20d06f81dce054cbcea8b5d497e8.1664552976.git.maciej.szmigiero@oracle.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'configure')
0 files changed, 0 insertions, 0 deletions