fyi, I do recall trying what I suggested in Comment #3, trying to debug
under GDB. However, I didn't find a way to trap writes to that region,
and didn't have any other good ideas.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Adding linux-kvm to the bug. It looks like if we can have the commit
above backported, it would take care of this issue for most users.
** Also affects: linux-kvm (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-kvm (Ubuntu)
Status: New => Confirmed
--
You
I got back to this a couple days ago, here's what I've learned.
I tried decoding the QEMU syndrome - but be warned, I've never done this
before. I believe what it is reporting is an EPT[*] misconfiguration.
I noticed that the 5.4 -generic kernel does not reproduce the issue,
while the -kvm one
I filed this issue on the kernel because it initially appeared to follow
the host kernel version. While it's very reproducible w/ v5.4, I wasn't
able to reproduce it with v5.8 or v5.7. However, I've now found that was
a false negative - it is still reproducible with v5.13, so the kernel
may not be
I attached gdb to the VM[*] and retrieved the following backtrace from
the guest kernel:
(gdb) bt full
#0 pci_conf1_read (seg=, bus=, devfn=, reg=16, len=4, value=0xc901fa0c) at
/home/dannf/linux-kvm-5.4.0/arch/x86/pci/direct.c:35
flags = 582
__dummy =
__dummy2
