| 1 | <?xml version='1.0' encoding='UTF-8'?>
|
|---|
| 2 | <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
|
|---|
| 3 | <topic xml:lang="en-us" id="vboxandsolzvmm">
|
|---|
| 4 | <title>Oracle VM VirtualBox and Oracle Solaris Kernel Zones</title>
|
|---|
| 5 |
|
|---|
| 6 | <body>
|
|---|
| 7 | <p>
|
|---|
| 8 | Oracle Solaris kernel zones on x86-based systems make use of
|
|---|
| 9 | hardware-assisted virtualization features like Oracle VM VirtualBox
|
|---|
| 10 | does. However, for kernel zones and Oracle VM VirtualBox to share this
|
|---|
| 11 | hardware resource, they need to cooperate.
|
|---|
| 12 | </p>
|
|---|
| 13 | <p>
|
|---|
| 14 | By default, due to performance reasons, Oracle VM VirtualBox acquires
|
|---|
| 15 | the hardware-assisted virtualization resource (VT-x/AMD-V)
|
|---|
| 16 | globally on the host machine and uses it until the last
|
|---|
| 17 | Oracle VM VirtualBox VM that requires it is powered off. This prevents
|
|---|
| 18 | other software from using VT-x/AMD-V during the time
|
|---|
| 19 | Oracle VM VirtualBox has taken control of it.
|
|---|
| 20 | </p>
|
|---|
| 21 | <p>
|
|---|
| 22 | Oracle VM VirtualBox can be instructed to relinquish use of
|
|---|
| 23 | hardware-assisted virtualization features when not executing guest
|
|---|
| 24 | code, thereby allowing kernel zones to make use of them. To do
|
|---|
| 25 | this, shutdown all Oracle VM VirtualBox VMs and execute the following
|
|---|
| 26 | command:
|
|---|
| 27 | </p>
|
|---|
| 28 | <pre xml:space="preserve">$ VBoxManage setproperty hwvirtexclusive off</pre>
|
|---|
| 29 | <p>
|
|---|
| 30 | This command needs to be executed only once as the setting is
|
|---|
| 31 | stored as part of the global Oracle VM VirtualBox settings which will
|
|---|
| 32 | continue to persist across host-reboots and Oracle VM VirtualBox
|
|---|
| 33 | upgrades.
|
|---|
| 34 | </p>
|
|---|
| 35 | </body>
|
|---|
| 36 |
|
|---|
| 37 | </topic>
|
|---|
