Installing any OS crash on Ryzen

[Viclucese]

I have tried VBox 5.2 and 6.1 on Ryzen 3750H and Ryzen 3200U (svm enabled) and both systems cannot finish installation of any OS. Any configuration on Ryzen I have to take care?

Windows 10 Pro Version 2004 on Ryzen 3750H
Windows 10 Pro Version 1909 on Ryzen 3200U

Edit: I want to share with you more information, but I get no errors in logs, only install crashing and no information in vbox logs.

[mpack]

Let us be the judge of what the log contains.

Pick one VM. With the VM fully shut down, right click it in the GUI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.

[Viclucese]

Let us be the judge of what the log contains.

Pick one VM. With the VM fully shut down, right click it in the GUI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.

Thanks, here is the log.

[mpack]

I see no sign of a VM crash, nothing is recorded in the log provided.

One thing, you have a 4-core host CPU, so you shouldn't assign more than 2 cores to a VM.

Also, you seem to have paid no attention to the other settings, e.g. VirtualBox will be warning you that 16MB is not enough graphics RAM. Increase to 128MB, then look for other settings warnings.

An 800GB hard drive seems quite large for a VM. Was that intentional? Can the host spare it?

[scottgus1]

Your log contains these lines:

{timestamp} HM: HMR3Init: Attempting fall back to NEM: AMD/V is not available
{timestamp} NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...

You might notice in the guest window's Status Bar the green turtle: The choice of animal is appropriate: Your guest is running, just really slow. Or it might guru-meditate or crash. This is because a service that uses Microsoft Hyper-V is running on your host PC. Normally Hyper-V blocks Virtualbox. But your PC is of the type and OS where Virtualbox can attempt to run the guest using the Hyper-V engine. This arrangement is still being developed and isn't 100% yet.

If VirtualBox is running without Hyper-V enabled, and nothing else is interfering with hardware virtualization (VT-x / AMD-V), then the usual virtualization icon () will be seen in the Status Bar.

To turn Hyper-V off completely, do this:

1. Shut down all programs. You will have to reboot your host.

2. Look into I have a 64bit host, but can't install 64bit guests, 2nd post, points 2 & 3 and ensure that none of these things are running.

3. Find the Command Prompt icon, right click it and choose Run As Administrator.

4. Enter this command:

bcdedit /set hypervisorlaunchtype off

5. Enter this command:

shutdown -s -t 2

6. When the computer turns off, unplug it for 20 seconds. Then plug it in again and boot up Windows 10.

Your Virtualbox should be running now. If the green turtle still appears and the tell-tale lines are in the log, try all the steps again. If you don't get the standard virtualization icon, post back exactly what you did and we'll try to help some more.

For further info, see https://www.tenforums.com/tutorials/139 ... puter.html

[Viclucese]

I see no sign of a VM crash, nothing is recorded in the log provided.

One thing, you have a 4-core host CPU, so you shouldn't assign more than 2 cores to a VM.

Also, you seem to have paid no attention to the other settings, e.g. VirtualBox will be warning you that 16MB is not enough graphics RAM. Increase to 128MB, then look for other settings warnings.

An 800GB hard drive seems quite large for a VM. Was that intentional? Can the host spare it?

I've tried lot of different configurations. Changed till every type of virtual disk, socket and cores configurations, value of RAM, and if I put more than 16 MB of RAM video VM crash. No one works. In fact, VM start, the installation of OS (Debian, Ubuntu, elementary at least) who not finish. For further information, ubuntu and elementary show me a message hinting that it may be I/O problem or disk problem. Both of my computers have nvme ssd, is this a problem?

Your log contains these lines:

{timestamp} HM: HMR3Init: Attempting fall back to NEM: AMD/V is not available
{timestamp} NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...

You might notice in the guest window's Status Bar the green turtle: The choice of animal is appropriate: Your guest is running, just really slow. Or it might guru-meditate or crash. This is because a service that uses Microsoft Hyper-V is running on your host PC. Normally Hyper-V blocks Virtualbox. But your PC is of the type and OS where Virtualbox can attempt to run the guest using the Hyper-V engine. This arrangement is still being developed and isn't 100% yet.

If VirtualBox is running without Hyper-V enabled, and nothing else is interfering with hardware virtualization (VT-x / AMD-V), then the usual virtualization icon will be seen in the Status Bar.

To turn Hyper-V off completely, do this:

1. Shut down all programs. You will have to reboot your host.

2. Look into I have a 64bit host, but can't install 64bit guests, 2nd post, points 2 & 3 and ensure that none of these things are running.

3. Find the Command Prompt icon, right click it and choose Run As Administrator.

4. Enter this command:

bcdedit /set hypervisorlaunchtype off

5. Enter this command:

shutdown -s -t 2

6. When the computer turns off, unplug it for 20 seconds. Then plug it in again and boot up Windows 10.

Your Virtualbox should be running now. If the green turtle still appears and the tell-tale lines are in the log, try all the steps again. If you don't get the standard virtualization icon, post back exactly what you did and we'll try to help some more.

My turtle is green. Never take care of this before . I've find your explanation before and tried. Didn't work. I still got WSL (ubuntu and debian), maybe they are causing problems?

By last, i've got an ova of Debian 10, and it works, with a green turtle indicator, but it works and not crash. My problem is in the OS installation.

Thanks for your help.

[scottgus1]

If the points in the 64-bits tutorial did not fix the problem, then either Microsoft has changed something, or the tutorial wasn't followed correctly.

If you kept WSL running, then it may have undone the fix. WSL version 1 is OK, but WSL2 uses Hyper-V and will interfere with Virtualbox.

The 64-bits tutorial is absolutely everything we know about how to deactivate Hyper-V.

[Viclucese]

If the points in the 64-bits tutorial did not fix the problem, then either Microsoft has changed something, or the tutorial wasn't followed correctly.

If you kept WSL running, then it may have undone the fix. WSL version 1 is OK, but WSL2 uses Hyper-V and will interfere with Virtualbox.

The 64-bits tutorial is absolutely everything we know about how to deactivate Hyper-V.

I have to apologize if I jump on any step because I resolve the problem deactivating Windows Subsystem for Linux in my laptop (Ryzen 3750H). The green turtle no longer appears on the icon, but the blue CPU appears. I have deactivated Hyper-V system before, but it's like isn't deactivate at all if you got WSL on. At this point I don't know if the CPU has something to do with the problem, I thought that being "modern" processors they could be generating some kind of problem.

I read some information where says the last version of VBox is compatible with Hyper-V and WSL 2, but my version was Versión 6.1.10 r138449 (Qt5.6.2) and not work properly.

Thanks for your help and I hope in newer versions of VBox this little problem can be resolved.

PS: In my other computer, 3200U, WSL and Hyper-V are off and it's not working yet. But I'll work on it later because I need to work in my laptop now.

[scottgus1]

WSL, actually WSL2, uses Hyper-V, so deactivating it enables Hyper-V to turn off. (The original WSL did not use Hyper-V.)

Now that you have the blue V icon instead of the turtle, you should be OK. The CPU should not cause any issues.

The devs hope to get Virtualbox working with active Hyper-V one day.