VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (634 - 636 of 16363)

Ticket Resolution Summary Owner Reporter
#6128 wontfix AMD-V is not work properly host on FreeBSD and Windows Guest OS Joseph Poon
Description

I have a VB 3.1.2 OSE hosting on FreeNAS(FreeBSD 7.2). i use AMD Athlon(tm) II X2 240 Processor, and Zotac GeForce 8200 clipset motherboard. i also enable "Virtualization" and "Secure Virtual Machine Mode" in BIOS. i have install a Windows 2008 R2 guest OS on VB. But AMD-V is not work within Windows 2008 R2. i use AMD tools to test the guest OS, it said that it is not enable AMD-V. Enclosed please find the VBox.log for your reference.

#12049 fixed AMD-V not available under Windows 8.1 TheXDS
Description

I tried to run a OS/2 virtual machine after I upgraded to Windows 8.1 Pro (host). When I had my old Windows 7, it worked fine, but now that I switched to 8.1, AMD-V seems to be unavailable to VirtualBox. I guess it may be the same for Intel VT-x

#5639 fixed AMD-V not working: VERR_SVM_IN_USE -> update your BIOS/workaround available in SVN/3.1.4 palomino
Description

Cpu: AMD AthlonIIx3 425. Motherboard: GA-MA78GM-US2H HostOS: Ubuntu 9.10 GuestOS: Windows 2003 (2 processors allocated) Virtualization is enabled in BIOS.

When i upgraded to 3.1.0, it reported "VT-x is not available. (VERR_VMX_NO_VMX)." when i tried to start the guest os. 3.0.12 worked fine. Reinstall 3.1.0 can not fix the issue. Remove 3.1.0 -> install 3.0.12 -> remove 3.0.12 -> install 3.1.0 works. But if I restart the computer, I have to do that again. BTW: It did not happen on another computer with intel's cpu.

Recommendations:

  • upgrade your BIOS if possible
  • remove the KVM modules (Linux host)

3.1.4 will contain a workaround for people with a broken BIOS and no option to update it.
Set the VBOX_HWVIRTEX_IGNORE_SVM_IN_USE environment variable to true:

  • set VBOX_HWVIRTEX_IGNORE_SVM_IN_USE=true on Windows
  • export VBOX_HWVIRTEX_IGNORE_SVM_IN_USE=true on Linux

This will tell VirtualBox to ignore VERR_SVM_IN_USE and continue to use AMD-V. Note that this is a hack and dangerous if you run more than one hypervisor at the same time. USE AT YOUR OWN RISK.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy