VirtualBox

Opened 3 years ago

Last modified 3 years ago

#20468 new defect

VM crashes during reboot if EFI is used on Ryzen CPU

Reported by: Justinh Owned by:
Component: EFI Version: VirtualBox 6.1.24
Keywords: Cc:
Guest type: Windows Host type: Windows

Description

Guru crash dialog during reboot of EFI Windows 10 VM upon the way back up at the EFI screen when more than 1 vCPU is used. I have a Ryzen 7 3700X CPU on a B550M chipset motherboard. Reference forum post https://forums.virtualbox.org/viewtopic.php?f=1&t=103398&sid=5b8fb3bf048f3b4fda4d91bcbd9ec0d3. User fth0 looked at the logs and found that "vCPU1 (the second vCPU) is in real mode and triple-faults".

Logs attached.

Attachments (1)

VBox_6.1.24_crash_2vCPU.zip (292.7 KB ) - added by Justinh 3 years ago.
crash with 2 vCPUs

Download all attachments as: .zip

Change History (2)

by Justinh, 3 years ago

Attachment: VBox_6.1.24_crash_2vCPU.zip added

crash with 2 vCPUs

comment:1 by fth0, 3 years ago

A few additional remarks:

  1. In the VirtualBox forum thread, I've requested and analyzed several VBox.log files, created by VirtualBox 6.1.22, especially with 2|3|4 vCPUs. At the time of the Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT), all vCPUs except vCPU0 were in a similar state, either in real mode or 32-bit protected mode, with EIP not pointing to a meaningful instruction. The "crashing" vCPU<n> seemed to be one step ahead of the others each time (EDI seemed to contain an offset or counter), for <n> not necessarily being 1, and the last VM-exit often was a regularly occurring "MMIO access".
  1. In the VirtualBox 6.1.24 VBox.log file above, the log messages are very similar to those in the VBox.log files in the VirtualBox forum thread. One notable difference are the RIP values in the VM-exit list of vCPU1, which contain 20-bit and 32-bit addresses, whereas in the older VBox.log files I've only seen 20-bit addresses.
  1. In the VirtualBox 6.1.24 VBox.log file above, the VirtualBox GA were updated just before the reboot, which could have influenced the problem. In the older VBox.log files, this wasn't the case.

@VirtualBox developers: Please let us know your thoughts, especially about further possible directions to investigate in.

Last edited 3 years ago by fth0 (previous) (diff)
Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use