VirtualBox

Changes between Version 71 and Version 72 of Ticket #5639


Ignore:
Timestamp:
Mar 2, 2010 12:53:25 PM (14 years ago)
Author:
Frank Mehnert
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #5639 – Description

    v71 v72  
    1111
    1212'''Recommendations:'''
    13 {{{
    14 - upgrade your BIOS if possible
    15 - remove the KVM modules (Linux host)
    16 }}}
     13 * upgrade your BIOS if possible
     14 * remove the KVM modules (Linux host)
    1715
    18 3.1.4 will contain a workaround for people with a broken BIOS and no option to update it.
    19 {{{
    20 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)
    21 }}}
     163.1.4 will contain a workaround for people with a broken BIOS and no option to update it.[[BR]]
     17Set 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)
    2218
    23 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.'''
     19This 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.'''

© 2023 Oracle
ContactPrivacy policyTerms of Use