Rob Bradford ed1e7817cc vmm: Workaround double reboot triggered by the kernel ... The kernel does not adhere to the ACPI specification (probably to work around broken hardware) and rather than busy looping after requesting an ACPI reset it will attempt to reset by other mechanisms (such as i8042 reset.) In order to trigger a reset the devices write to an EventFd (called reset_evt.) This is used by the VMM to identify if a reset is requested and make the VM reboot. As the reset_evt is part of the VMM and reused for both the old and new VM it is possible for the newly booted VM to immediately get reset as there is an old event sitting in the EventFd. The simplest solution is to "drain" the reset_evt EventFd on reboot to make sure that there is no spurious events in the EventFd. Fixes: #783 Signed-off-by: Rob Bradford <robert.bradford@intel.com>		2020-02-19 18:51:14 +01:00
..
src	vmm: Workaround double reboot triggered by the kernel	2020-02-19 18:51:14 +01:00
Cargo.toml	vmm: Move codebase to GuestMemoryAtomic from vm-memory	2020-02-19 13:48:19 +00:00