On a dual boot PC that I have with Win7Pro64 and Win10Pro64, I have a VM of Windows Server 2019 that I created on Windows 7 Pro 64-Bit and saved to a shared drive that is available to both OS's. When I try to boot the VM in Windows 10 Pro 64, it crashes the VM. The settings for both OS's for the VM are identical. Both are running the latest version of VirtualBox and the extensions are installed.
Should I export the VM in Win7 and import it in Win10? I need to boot into Win7 just to run the VM because it won't open/run in Win10.
Any ideas?
Server 2019 VM created in Win7 Pro 64, crashes on Win10 Pro 64
-
RGiuffre2005
- Posts: 1
- Joined: 29. May 2021, 01:13
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: Server 2019 VM created in Win7 Pro 64, crashes on Win10 Pro 64
While the VM is running in Windows 10, right-click the guest in the main Virtualbox window's guest list, choose Show Log.
Search the far left tab's log for this text:
Attempting fall back to NEM
If you find it, Hyper-V is enabled. See HMR3Init: Attempting fall back to NEM (Hyper-V is active).
If you don't find that text, save the far left tab's log, zip the log file, and post the zip file, using the forum's Upload Attachment tab.
Another thing, for both host OS's, The VM's 2019 template may have a bug in it. Go to the VM's General settings, Version dropdown, use the 2016 template for Server 2019, and make sure that the VM's System settings, Acceleration, Paravirtualization Interface* says 'Hyper-V'.
(* 'Paravirtualization Interface' is a comm channel for virtualization-aware OS's to talk to whatever hypervisor is running them, so they can run more efficiently. Setting this to Hyper-V does not turn on the host OS's Hyper-V.)
Search the far left tab's log for this text:
Attempting fall back to NEM
If you find it, Hyper-V is enabled. See HMR3Init: Attempting fall back to NEM (Hyper-V is active).
If you don't find that text, save the far left tab's log, zip the log file, and post the zip file, using the forum's Upload Attachment tab.
Another thing, for both host OS's, The VM's 2019 template may have a bug in it. Go to the VM's General settings, Version dropdown, use the 2016 template for Server 2019, and make sure that the VM's System settings, Acceleration, Paravirtualization Interface* says 'Hyper-V'.
(* 'Paravirtualization Interface' is a comm channel for virtualization-aware OS's to talk to whatever hypervisor is running them, so they can run more efficiently. Setting this to Hyper-V does not turn on the host OS's Hyper-V.)