fth0 wrote:
Thank you for reporting your findings, very interesting. I have two questions:
- I'd assume that setting the Paravirtualization Interface to None would also prevent the reboots. Could you please verify and confirm this?
None did not work. It caused the VM to reboot within 2 minutes of starting up.
fth0 wrote:
[*]Just to be sure: Part of the Hyper-V paravirtualization interface is the guest error reporting, so using None or Legacy could go unnoticed, because the guest OS would simply reboot without VirtualBox knowing about the crash. Did you see that the guest OS did not crash?[/list]
I have not noticed any crashes with the guest OS. None were reported in my log files.
Additional information/notes: Since you asked these questions, I decided to look into it further and inspect the log files more closely. Indeed, I am not getting a Guest OS crash. However, I am getting BugCheck's and the Guest OS does reset itself.
Here's the exert from my log files:
Code: Select all
00:02:06.688572 AHCI#0: Reset the HBA
00:02:06.688595 VD#0: Cancelling all active requests
00:02:06.688829 AHCI#0: Port 0 reset
00:02:06.690171 VD#0: Cancelling all active requests
00:02:07.225019 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:02:16.817627 VMMDev: Guest Log: VBoxGuest: BugCheck! P0=0x3d P1=0xfffff8041227ac08 P2=0xfffff8041227a440 P3=0x0 P4=0x0
00:02:16.817792 ACPI: Reset initiated by ACPI
00:02:16.817799 Changing the VM state from 'RUNNING' to 'RESETTING'
So, with that being said, my "solution" appears to
NOT be working. It just merely keeps the Guest OS running for a longer period of time before the reboot happens and there is no crash. I have noticed that it takes 30 to 40 minutes before I get a reboot.