VirtualBox

Changes between Initial Version and Version 58 of Ticket #5639


Ignore:
Timestamp:
01/20/10 14:26:23 (4 years ago)
Author:
sandervl73
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #5639

    • Property Status changed from new to reopened
    • Property Summary changed from AMD-V not working to AMD-V not working: VERR_SVM_IN_USE -> update your BIOS/workaround available in SVN/3.1.4
  • Ticket #5639 – Description

    initial v58  
    99Remove 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. 
    1010BTW: It did not happen on another computer with intel's cpu. 
     11 
     12Recommendations: 
     13{{{ 
     14- upgrade your BIOS if possible 
     15- remove the KVM modules (Linux host) 
     16}}} 
     17 
     183.1.4 will contain a workaround for people with a broken BIOS and no option to update it. 
     19{{{ 
     20set the VBOX_HWVIRTEX_IGNORE_SVM_IN_USE environment variable to true (set VBOX_HWVIRTEX_IGNORE_SVM_IN_USE=true) 
     21}}} 
     22 
     23This will tell VirtualBox to ignore VERR_SVM_IN_USE and continue to use AMD-V. Note that this is a hack and risky if you run more than one hypervisor at the same time. USE AT YOUR OWN RISK. 
     24}}} 

www.oracle.com
ContactPrivacy policyTerms of Use