8.3 DEPLOYING ORACLE SOLARIS 10 WITH ORACLE VM SERVER FOR X86 generate, create code-128 none with software projects Visual Studio Development Language Once the installation Code 128 for None process has completed, Oracle VM will shut down the guest. Select Power On for the virtual machine and use VNC to connect again to the console. When you power on the VM using the Oracle VM Manager, Solaris will go through its typical rst boot process importing all of the SMF manifests, discovering devices, asking for information about the connected keyboard, and then presenting a graphical login.

Note that when the graphical console is presented via the Java VNC client, it is clipped on the right and bottom of the display, because the display area provided by the Java VNC client is not as large as that of the default Solaris screen. Using vncviewer gets around this problem. Once you have logged in, open a terminal window.

During the rst boot after installation, the kernel was unable to nd any network devices. The Oracle VM Server presents its virtual networks as instances of the fully virtualized rtls network driver to the guest by default. However, Oracle Solaris comes with paravirtualized drivers for network and disk installed instead.

To con gure the network after Solaris is running, we must cause it to abandon its current network con guration, change the virtual network interface to a paravirtualized interface, and then reboot and rediscover the network. To do so, the VM must be rebooted and new VM identi cation information, including the networking parameters, must be discovered. The simplest way to achieve this goal is to issue the sys-uncon g command on the VM.

The sys-uncon g command causes Solaris to forget its identity and shut down. Figure 8.11 shows the Solaris 10 user interface and the sys-uncon g command.

. Figure 8.11 Recon guring Oracle Solaris After Installation 8 . Applying Virtualization Once the VM is shut d Software code 128a own, it will prompt you for a keystroke to reset the VM. At this point, you can use the Oracle VM Manager console to power off the VM, as shown in Figure 8.12.

. Figure 8.12 Power Off VM for Recon guration When the VM has been code 128c for None powered off, it can be recon gured. Select the VM from the list and click the Con gure button, or just click the name of the VM you want to con gure. Either way, you will be taken to the con guration screen.

In the con guration screen shown in Figure 8.13, you can change many of the characteristics of the VM: the number of CPUs, the amount of memory, the network con guration, additional attached disks, and more. We simply want to change the network interface from fully virtualized to paravirtualized.

Select the Network tab (between the General and Storage tabs), which takes you to the network con guration panel. Select Paravirtualized as the Network Type. Notice that when you make this choice, the network type changes from ioemu to netfront, as shown in Figure 8.

14. Return to the General tab and click Save. Then return to the Virtual Machines panel, select the VM, and click Power On to start the VM.

Connect to its console. Because we used sys-uncon g to uncon gure the VM, the VM will prompt for network and naming service identi cation as it boots. Once it has identi ed the network, it will reboot a nal time.

When the VM comes up this time, it will be fully installed and running on the network.. 8.3 DEPLOYING ORACLE SOLARIS 10 WITH ORACLE VM SERVER FOR X86 Figure 8.13 VM Con guration Screen Figure 8.14 Recon guring the Network for Paravirtualization Once the VM has been code 128a for None rebooted, it is ready to be used. At this point, you can also use it as an Oracle VM Manager template from which to instantiate multiple virtual machines. Likewise, before the VM is powered on again, the CPU and memory con guration can be modi ed as desired.

These changes are described in the Oracle VM 2.2 documentation collection at

com/ docs/cd/E15458_01/index.htm..

Copyright © . All rights reserved.