About Booting the Solaris Control Domain
Whether to run Solaris as a virtualized control domain or as a standalone operating system is a boot-time decision. To run the Solaris operating system as a standalone system, continue to use the same GRUB menu entries that you use currently.
To run the Solaris system as a control domain with the Sun xVM hypervisor, you must do one of the following:
This boots the hypervisor, which in turn boots the control domain.
In the Solaris xVM entry for booting Solaris as a control domain with the hypervisor, the kernel$ line refers to the hypervisor, and there are two module$ lines. The first module$ line must list the path to unix twice, with any arguments. Arguments are represented by * at the end of a line in the example. The second module$ line lists the path to the boot archive.
How to Boot the Solaris Control Domain
In some situations, the GRUB menu.lst file might not reside in /boot/grub. To determine the location of the active GRUB menu.lst file, use the bootadm command with the list-menu subcommand.
Setting the Solaris xVM Entry To Boot by Default
How to View Domains on the System
Run the virsh list --all, xm list or the xm top commands to view the domains on the system. These commands provide details of running domains. The display from any of these commands should show the single control domain, called Domain-0.
See the xentop(1M)man pages.