VirtualBox

Ticket #20621 (new defect)

Opened 3 months ago

Last modified 3 months ago

Hyper-V doesn't work on AMD Ryzen 3800x for old VM

Reported by: vbicf Owned by:
Component: other Version: VirtualBox 6.1.26
Keywords: Cc:
Guest type: Windows Host type: Windows

Description

Hi,

I have some old Windows 10 VM (VT-X) that was created when Hyper-V was not enabled in the host. After I enable Hyper-V, that old VM will not start and it will get a bluescreen. Is there a way to fix that old VM machine so that it will start with Hyper-V enabled in the host. I changed the settings in VirtualBox to use Hyper-V Paravirtualization but the blue screen happens again. See here:

If I create a VM from scratch with Hyper-V enabled in the host, the VM will boot fine.

This means something in the old VM is causing the crash. I don't want to reinstall it from scratch.

System: Ryzen 3800X

The version of VirtualBox: 6.1.26

Host: Windows 10 21H1, Guest: Windows 10 20H2

When the VM was created: VT-x/AMD-V enabled, HyperV disabled

installed Guest Additions and Host Extensions

I have another system Intel 7700k, on that system with the same VM I can start that old VM when Hyper-V is enabled!

This looks like and AMD specific issue.

I am attaching the log from my amd system when I get the blue screen.

Attachments

SQL Server-2021-10-20-14-10-07.log Download (150.4 KB) - added by vbicf 3 months ago.
blue screen.jpg Download (89.0 KB) - added by vbicf 3 months ago.

Change History

Changed 3 months ago by vbicf

Changed 3 months ago by vbicf

comment:1 follow-up: ↓ 3 Changed 3 months ago by ebk

Simple google search shows it has something to do with Parallels Tools.

 https://systemexplorer.net/file-database/file/prl_strg-sys

Try uninstall softwares that related to it.

Note that enable Win10's HyperV feature will lock vitualization to Windows exclusively. In this case VBox will try to use turtle(API) mode to start vm for you and it is slow and unstable. (Which may have something to do with your problem.)

The Paravirtualized interface options in VBox only tell it what virtual environment to emulate for different OS, and its stated clearly in the manual.

comment:2 Changed 3 months ago by vbicf

Hi,

You were right! I had the impression it was something related to windows and ignored completely the message related to prl_strg-sys. (facepalm) Yes in the past I had this machine on a mac, I totally forgot about this !

I removed the Parallel Tools from the Guest and now it boots!

Last edited 3 months ago by vbicf (previous) (diff)

comment:3 in reply to: ↑ 1 Changed 3 months ago by vbicf

I need Docker and WSL2 which requires Hyper-V.

VirtualBox will need to work nicely via Hyper-V

Replying to ebk:

Simple google search shows it has something to do with Parallels Tools.

 https://systemexplorer.net/file-database/file/prl_strg-sys

Try uninstall softwares that related to it.

Note that enable Win10's HyperV feature will lock vitualization to Windows exclusively. In this case VBox will try to use turtle(API) mode to start vm for you and it is slow and unstable. (Which may have something to do with your problem.)

The Paravirtualized interface options in VBox only tell it what virtual environment to emulate for different OS, and its stated clearly in the manual.

comment:4 follow-up: ↓ 5 Changed 3 months ago by vbicf

How do I mark this ticket as fixed?

comment:5 in reply to: ↑ 4 Changed 3 months ago by ebk

Replying to vbicf:

How do I mark this ticket as fixed?

I think only developers can do this.

Turtle mode is painfully slow on my laptop while it is normal on some of my other machines. Very weird.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use