You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
after updating bootloader to v0.11.9 in 7301300, it seems that running the kernel in KVM results in the local APIC page already having been mapped by the bootloader to...some other thing.
(this is the assertion that the PTE found by walking the page table doesn't have the present bit set).
so it seems that somehow PT@0xffffffc0c07f7000[503] is pointed at 0x17000, when we would like to point it at the LAPIC MMIO page at 0xfee00000. We'd really like to identity map that address (vaddr 0xffff8180fee00000), but the bootloader seems to have already mapped the VAddr to...some other thing. which is weird.
The text was updated successfully, but these errors were encountered:
after updating
bootloader
to v0.11.9 in 7301300, it seems that running the kernel in KVM results in the local APIC page already having been mapped by the bootloader to...some other thing.running with
$ cargo run-x64 --serial -- -machine accel=kvm -cpu host,migratable=no,+invtsc
gets a crash like this:
(this is the assertion that the PTE found by walking the page table doesn't have the present bit set).
so it seems that somehow
PT@0xffffffc0c07f7000[503]
is pointed at 0x17000, when we would like to point it at the LAPIC MMIO page at 0xfee00000. We'd really like to identity map that address (vaddr 0xffff8180fee00000), but the bootloader seems to have already mapped the VAddr to...some other thing. which is weird.The text was updated successfully, but these errors were encountered: