This chapter contains troubleshooting information for Sun xVM.
At this time, you should note the following issues when configuring dom0:
ZFS must be prevented from taking too much memory from dom0. Limit the ARC by adding the following line to /etc/system:
set zfs:zfs_arc_max = 0x10000000 |
Reboot the system.
Limit dom0 to a specific amount of memory by using the Xen dom0_memoption. For example, if you have 4Gb of memory, give dom0 1Gb in /rpool/boot/grub/menu.lst:
... kernel$ /boot/$ISADIR/xen.gz dom0_mem=1024M ... |
When installing OpenSolaris 2008.11, the "text-only" boot option from the GRUB menu should be selected. This is the second entry. However, the following workaround can be used if the text-only boot option is not selected.
When the GNU GRand Unified Bootloader (GRUB) boot menu appears on the console, type e for edit before the boot selection times out and starts booting the default entry.
The edit menu screen that pops up will have several lines on it. Use the down arrow key to scroll down to the line foreground, and type d for delete.
Repeat the Step 2 process for the line background. Use the down arrow key to scroll down to the line that says background, and type d for delete.
Using the arrow keys, scroll to the kernel line that contains the boot arguments, and type e for edit. Then, delete the entry for console=graphics.
Press Return to exit line edit and save the changes, and then type b to continue the boot.
Change directories to /dev/xen and list the contents:
# cd /dev/xen # ls balloon domcaps evtchn privcmd xenbus |
Become superuser, or assume the appropriate role.
Verify that the xvm services are running.
# svcs -a | grep xvm |
If the system displays the following, the services are not running:
disabled Dec_07 svc:/system/xvm/store:default disabled Dec_07 svc:/system/xvm/xend:default disabled Dec_07 svc:/system/xvm/console:default disabled Dec_07 svc:/system/xvm/domains:default |
If the services are not running, verify that you booted an i86xpv kernel.
# uname -i i86xpv |
Reboot if necessary.
If the correct kernel is running, enable the services.
# svcadm enable xvm/store # svcadm enable xvm/xend # svcadm enable xvm/console # svcadm enable xvm/domains |
You are now ready to create guest domains (domUs).
Due to the isolation of the hypervisor from dom0, there is currently no way to apply DTrace directly to the hypervisor. There is an xpv DTrace provider that allows you to trace the interaction between dom0 and the hypervisor.
To list the available DTrace probes, use the following command line:
# dtrace -l -i 'xpv:::' |
To enable all probes, use the following command line
# dtrace -n 'xpv::: {}' |
If you are running an OpenSolaris 2009.06 HVM guest on Hyper-V SP2 (RC build), you'll need to update your OpenSolaris 2009.06 to at least snv_113to get the fix for CR 6768204, “dnet interface takes a long time to resume after plumb/unplumb in Hyper-V virtual machine.” Without the update, the network interface doesn't work for several minutes after the first interface unplumb/plumb operation. Obtain the update from the OpenSolaris Packaging Repository .
If you're running an OpenSolaris 2009.06 HVM guest on OpenSolaris 2009.06 dom0, you'll need to apply the workaround for CR 6828707 for XServer to start on the guest.
The issue is how long gdm should wait before it assumes a started Xserver is defunct. The default set in /usr/share/gdm/factory-defaults.conf is:
GdmXserverTimeout=10 |
The default should be increased. To override the default and set the timeout to the recommended value, add the following to /etc/X11/gdm/custom.conf:
GdmXserverTimeout=30 |
If the workaround is not used, the user will not see the GUI login window. If booted in text mode, only a console login window will be available. If booted in graphics mode, only the OpenSolaris startup screen will be seen.
CR 6810371 HCTS CPU test fail with "can not fork: too many processes" if the virtual machine uses a dynamic hard disk.
This problem affects Solaris 10 5/09 HVM guests. The workaround is to either change hard disk of the virtual machine to fixed-size, or to create a big file and point system swap to use that file.
For additional documentation and more information about the hypervisor feature, visit the OpenSolaris community. The FAQ at this site will be updated to contain the latest issues.
For the latest information on dom0, see the document dom0 configuration for admins . See the document New Network Options, Including Limiting Bandwidth and Setting a VLAN ID, for Virtual Network Interfaces Attached to a Guest at this site to learn about new conventions for network options in virt-install.
xVM 3.3 documentation can be found on the OpenSolaris Community: Xen site.