This section contains the latest issues and information common to all operating systems running in full virtualization mode on the VM Server. It contains the following subsections:
Basic instructions for creating a fully virtual VM are in Section 3.1.4, Creating a Virtual Machine (Full Virtualization Mode).
Information in this section is common to all operating systems running in fully virtual mode. Before creating or running a fully virtual VM, you should review issues related to its specific operating system in Section 7.0, Specific Operating Systems .
Power management features, such as the suspend-to-disk feature, are not supported and should be disabled on the VM Server and all VMs.
For best performance, create each virtual disk from an entire disk or a partition. For next best performance, create an image file but do not create it as a sparse image file. A virtual disk based on a sparse image file delivers the most disk-space flexibility but the slowest installation and disk access speeds. (179409)
By default, a VM’s virtual disk uses asynchronous write mode to write data to the disk. Asynchronous write mode dramatically improves VM system-to-disk performance because the VM Server can buffer data before actually writing to disk. Although it delivers better performance, the asynchronous write mode might corrupt the file system if the VM is using a file-backed virtual disk and the VM server has a system crash or power outage. This is because Xen does not support write barriers, which preserve the order of data being written to disk.
A virtual disk using synchronous write mode maintains file system integrity in the event of a system crash, but significantly slows write-to-disk performance by executing each write-to-disk activity before continuing. In synchronous write mode, the VM Server does not cache data.
To change between modes, append or remove the S flag to the existing writable flag in the disk line in the VM's configuration file. This mode is set per disk.
For example, the first statement specifies asynchronous disk-write mode (no S). The second statement specifies synchronous write mode (added S).
disk = [ 'file:/var/lib/xen/images/vm1/hda,hda,w' , 'phy:/dev/hdb,hdb,w' ]
disk = [ 'file:/var/lib/xen/images/vm1/hda,hda,wS', 'phy:/dev/hdb,hdb,w' ]
The following commands are available by running the Virtual Machine Management (Xen) module on the Xen VM Server desktop.
On the VM Server desktop, click > > .
The Manage Virtual Machines page displays all VMs.
From the Manage Virtual Machines page, you can perform the following actions:
When running or setting up a VM in full virtualization mode, you can use the following commands and key combinations:
You can perform actions on VMs by using the xm command. In a terminal, log in as root and enter the desired command.
Fully-virtualized VMs can crash, especially when running heavy loads, if not enough free memory is available for Xen. Xen does not yet flush the shadow page cache when memory becomes low, which can result in an artificial out-of-memory condition. As a workaround, manually shrink the Xen VM Server’s memory (to leave some amount free for use by Xen) with a command such as xm mem-set 0 384
By default, the VM Server uses the SDL viewer to view fully virtual guests, but you can change the setting to use the VNC viewer. If you change to the VNC viewer, make sure remote administration is disabled on the VM Server. If remote administration is disabled, entering vncviewer VM_server_ip_address:VM_ID in a terminal displays the VM (matching the ID) in the VNC viewer. If remote administration is enabled, the VNC viewer displays the VM Server’s login prompt, not the intended VM.
HINT:You might need to reboot the VM Server to disable remote administration.