virtualbox.org

I'm getting an error message when trying to open SAS University Edition. I've attached a copy of the screen shot of the error message, as well as a zipped version of the log. I have had all kinds of issues installing this, and was able to finally enable virtualization to get this far. Not sure why I am not able to get this thing installed, but I'm on the last 2 steps for the SAS installation when I open and this happens. Any help is appreciated.

Thanks

Your log contains these lines:

{timestamp} HM: HMR3Init: Attempting fall back to NEM: VT-x 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. 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. Find the Command Prompt icon, right click it and choose Run As Administrator.

3. Enter this command:

bcdedit /set hypervisorlaunchtype off

4. Enter this command:

shutdown -s -t 2

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

If your Virtualbox does not start successfully, see I have a 64bit host, but can't install 64bit guests. The 64-bits tutorial has a couple more things to look for in step 2. For further info, see https://www.tenforums.com/tutorials/139 ... puter.html

I didn't quite see the same as Scott as the PC appears to have an AMD rather than an Intel processor.

00:00:07.996384 ********************* End of CFGM dump **********************
00:00:07.999231 HM: HMR3Init: Attempting fall back to NEM: AMD-V is not available
00:00:08.269518 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...

That implies that AMD-v may not be enabled in the BIOS. if that's the case and this is an HP All-In-One the Guidance from the HP Site is:

"Please follow the below steps to Enabling or Disabling Virtualization Technology in BIOS.

1. Turn on the computer, and then immediately click F10 to enter BIOS.
2. Under the Security tab, use the up and down arrows to select USB Security, and then press Enter.
3. Use the up and down arrows to select Virtualization Technology (VTx), then use the left and right arrows to select either Enabled or Disabled as desired.
4. When you are finished, click F10 to save your changes and exit BIOS."

If AMD-V is already shown as enabled then you need to look at the further guidance steps that Scott pointed to.

Sorry, should have changed the 'VT-x' to 'AMD-V'...

multiOS wrote:

00:00:07.996384 ********************* End of CFGM dump **********************
00:00:07.999231 HM: HMR3Init: Attempting fall back to NEM: AMD-V is not available
00:00:08.269518 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...

That implies that AMD-v may not be enabled in the BIOS.

Well, there's no manual for interpreting the log file... but that isn't my understanding of that passage.

My understanding is that if it says "WHvCapabilityCodeHypervisorPresent is TRUE" then some part of Hyper-v is running, which means that VT-x or AMD-v is enabled. In this case AMD-v is not available to VirtualBox because NEM is using it, not because the BIOS didn't enable it.