p2m lock starvation
The current read/write lock implementation is read-biased, which allows a consistent stream of readers to starve writers indefinitely. There are certain rwlocks where guests are capable of applying arbitrary read pressure.
resource abuse (fairness for reader & writer)
switch to write-biased r/w locks
This is to improve fairness: A permanent flow of read acquires can otherwise lock out eventual writers indefinitely.
A malicious guest administrator can deny service to other tasks. If the NMI watchdog is active, a timeout might be triggered, resulting in a host crash.