Running Microsoft Windows in an Oracle Solaris Container in Software Development code128b in Software Running Microsoft Windows in an Oracle Solaris Container

How to generate, print barcode using .NET, Java sdk library control with example project source code free download:

8.5 Running Microsoft Windows in an Oracle Solaris Container use software code 128c creator toassign barcode 128a for software Android Solaris Containers a Software code 128 barcode re a very ef cient way to consolidate Oracle Solaris server workloads, and are exible enough to be used for additional purposes. Oracle VM VirtualBox software can run in a Container when running Solaris on x86 systems, making it possible to apply the bene ts of Containers to guest virtual machines running other operating systems. With this approach, Windows and Linux applications can be safely and conveniently run on the same server or desktop system running Solaris applications (see Figure 8.

15). The guest applications can take advantage of the isolation and resource controls of Containers as well as other Solaris features such as ZFS and Trusted Extensions. This type of consolidation need not be limited to server workloads.

Notably, the built-in RDP capabilities of VirtualBox make it possible to use this technique for desktop consolidation as well. In this example we will create a Container con gured for just one application: a VirtualBox guest running Windows XP in headless mode. Once the guest is con gured, it will be started automatically when the Container boots by placing a script in the directory /etc/rc.

d.. 8.5 RUNNING MICROSOFT WINDOWS IN AN ORACLE SOLARIS CONTAINER % rdesktop Wind % rdesktop ox Container Wind ox Container Figure 8.15 Running Remote Windows Desktops or Applications in Oracle Solaris Containers This example uses co ncepts and features described in 5, Oracle VM VirtualBox, and 6, Oracle Solaris Containers. The command examples in this section use the prompt GZ# to indicate a command that must be entered by the root user in the global zone. The prompt winxp-desktop1# shows that a command will be entered as the root user of the Container named winxp-desktop1.

The prompt % precedes a command that is run by a nonprivileged user.. 8.5.1 Planning This example assumes that Solaris 10 10/09 has been installed as the host operating system and that VirtualBox has been installed in the global zone. In this example, each Container will run a single VirtualBox guest. A remote system will access the desktop using the built-in VirtualBox RDP server.

Because only a single guest is present, the network con guration is greatly simpli ed: Each Container has a single IP address, and the VRDP server listens to the default port number 3389. If we want to run a second desktop session, we can clone the Container and the second user can connect to the same default port number but with the cloned Container s new IP address. It would also be a good idea to place the Container s zonepath inside a ZFS le system.

Should a second similar desktop be desired, creating the additional Container will be faster and consume less storage because cloning a ZFS data set takes less time than copying all of the content beneath zonepath.. 8 . Applying Virtualization The con guration of Software ANSI/AIM Code 128 the Container itself is straightforward, with the only difference being the addition of the VirtualBox control device /dev/vboxdrv. To reduce the total storage required, we will use a sparse-root zone, as described in 6. Because running a VirtualBox guest as the root user is discouraged, we must create a regular user account to con gure and run the VirtualBox guest.

Once the guest is installed, this account would be used only to make changes to the guest con guration, such as adding more storage. Once the Container is installed and properly con gured, we must create the VirtualBox guest and install the operating system, as described in 5. In our example, an ISO image library with the Microsoft Windows XP installation media is already present on the host system in a directory named /iso.

This directory will be made available to the Container using a read-only loopback le system. Because we will run Microsoft Windows XP in our guest machine, a few of the VirtualBox settings may need modi cation. The host is a relatively modern x86 system with hardware virtualization features enabled in the BIOS.

We will also enable those features in the guest machine. The recommended network device for Windows XP is the AMD PCNet FAST III. Because this is a desktop guest, we recommend using the NAT feature of VirtualBox for the Container s interface.

If it were a server, bridged mode would be more appropriate, but would require the Container to be con gured as exclusive IP Finally, for ef ciency, we use a SATA . boot disk instead of the standard IDE con guration..

Copyright © . All rights reserved.