Comment by tryauuum 3 hours ago Doesn't this one need it as well? I see the shadow mmu 2 comments tryauuum Reply minimaltom 2 hours ago Right, but what x86 KVM setup is there in practice that doesnt present a mmu to its guest and hence keep its own track (shadow) of memory mappings? Veserv 1 hour ago Shadow memory mappings are only needed when you do not have hardware virtualization or when doing nested virtualization.From the page: "it can threaten the guest-host isolation of KVM/x86 hosts that accept untrusted guests and expose nested virtualization"That is not to say that it is not a serious vulnerability though.
minimaltom 2 hours ago Right, but what x86 KVM setup is there in practice that doesnt present a mmu to its guest and hence keep its own track (shadow) of memory mappings? Veserv 1 hour ago Shadow memory mappings are only needed when you do not have hardware virtualization or when doing nested virtualization.From the page: "it can threaten the guest-host isolation of KVM/x86 hosts that accept untrusted guests and expose nested virtualization"That is not to say that it is not a serious vulnerability though.
Veserv 1 hour ago Shadow memory mappings are only needed when you do not have hardware virtualization or when doing nested virtualization.From the page: "it can threaten the guest-host isolation of KVM/x86 hosts that accept untrusted guests and expose nested virtualization"That is not to say that it is not a serious vulnerability though.
Right, but what x86 KVM setup is there in practice that doesnt present a mmu to its guest and hence keep its own track (shadow) of memory mappings?
Shadow memory mappings are only needed when you do not have hardware virtualization or when doing nested virtualization.
From the page: "it can threaten the guest-host isolation of KVM/x86 hosts that accept untrusted guests and expose nested virtualization"
That is not to say that it is not a serious vulnerability though.