Converting A Virtual Machine To A Driver Domain Virtual Machine - Oracle X6-2-HA Deployment And User's Manual

clone virtual machine
oakcli clone vm vm1_ol5u7 -vmtemplate OL5U7 -repo odarepo1 -node 0 -
driverdomain
Run the oakcli show vm command to confirm that the virtual machine is
3.
configured in driver domain mode.
When the virtual machine is in driver mode, the output for the DriverDomain
attribute is TRUE.
oakcli show vm vm1_ol5u7
Use the oakcli start vm command to start the virtual machine.
4.
For example, start the virtual machine named vm1_ol5u7 on Node 0.
oakcli start vm vm1_ol5u7 -node 0

Converting a Virtual Machine to a Driver Domain Virtual Machine

Convert a guest virtual machine to a driver domain virtual machine to improve
performance.
You can clone an existing virtual machine that uses Dom0 to create a clone virtual
machine that uses the driver domain ODA_BASE instead of Dom0.
In this example, virtual machine vm–dom0_ol5u7 is on Dom0 and is not a driver domain
virtual machine. The example creates a clone virtual machine named vm–dd1_ol5u7
that uses the driver domain ODA_BASE.
Use the oakcli stop command to shut down the virtual machine.
1.
For example, stop the virtual machine named vm–dom0_ol5u7. Shutting down the
virtual machine ensures that there is consistent data from the virtual machine (vm)
and virtual disks (vdisks)
oakcli stop vm vm2_ol5u7 -force
Detach the virtual disk (vdisk) from vm–dom0_ol5u7
2.
Use the oakcli clone vm command to clone a new virtual machine from the
3.
original.
Create a new virtual machine named vm–dd1_ol5u7 from the original virtual
machine named vm–dom0_ol5u7. Use the -snap option to create a snapshot of the
source virtual machine. Because the original virtual machine is not a driver domain
machine, use the -force and -driverdomain options to create a clone virtual
machine that does use the driver domain.
oakcli clone vm vm–dd1_ol5u7 -vm vm–dom0_ol5u7 -snap -force -driverdomain
Attach the virtual disk (vdisk) that you detached from the source virtual machine in
4.
Step 2 to the new driver domain virtual machine.
Attaching the vdisk ensures that the vm.cfg has the disk information with the driver
domain feature.
Verify that oakDom1is the vdisk in the new vm.cfg.
5.
How to Create Driver Domain Virtual Machines
Chapter 12
12-33