Domu is the guest domain, install a domu basically is a manual work, I have not done a long time almost forgot, recently to test a few systems so picked up, here the process record, the future with the face Roll keyboard on the line ... Domu are divided into two types: Para-virtualization and hardware-virtualization, specific explanations to xen.org to see. The two Domu installation methods are different.
Para-virtualization (class Virtualization):
The launch of PVM currently requires Pvgrub support (Http://wiki.xen.org/wiki/PVGrub_HowTo), which is specified in the configuration file as
Kernel=/usr/lib/xen/boot/pv-grub-x86_64.gz
Extra= (hd0,0)/boot/grub/menu.lst
Hardware-virtualization (Hardware-assisted virtualization):
HVM Domu needs to be started through Hvmloader (http://wiki.xen.org/wiki/Hvmloader), if you have Xen installed, you can look at the/ETC/XEN/XMEXAMPLE.HVM profile
Here is an example of an excerpt from the Xen wiki
Example HVM Guest configuration file for PVHVM use
Example configuration file ("/ETC/XEN/F16HVM") for Xen 4.x HVM guest VM using Linux PVHVM paravirtualized optimized driver s for disks and network:
Kernel = "Hvmloader"
builder= ' hvm '
device_model = ' QEMU-DM '
name = ' F16PVHVM '
memory = 1024
vcpus= 1
pae=1
acpi=1
apic=1
vif = [' Mac=00:16:4f:02:02:15, Bridge=virbr0, model=e1000 ']
disk = [' phy:/ Dev/vg01/f16pvhvm-disk0,hda,w ', ' file:/root/iso/fedora-16-x86_64-dvd.iso,hdc:cdrom,r ']
boot= ' CD '
Xen_ Platform_pci=1
on_poweroff = ' Destroy '
on_reboot = ' restart '
on_crash = ' Restart
' Sdl=0
vnc=1
vncpasswd= '
stdvga=0
serial=
' pty ' tsc_mode=0 usb=1 ' Tablet '
keymap= ' en '
This example has been tested and are working on Fedora Xen DOM0 host using the included Xen 4.1.2 and Linux 3.1 i n Dom0, and Fedora Xen PVHVM guest VM, also using the stock F16 Linux 3.1 kernel with the Out-of-the-box included Drivers.
PVM installation There is also a note about the installation of PV driver, please refer to the Xen wiki
Http://wiki.xen.org/wiki/Using_Xen_PV_Drivers_on_HVM_Guest
Http://wiki.xen.org/wiki/XenLinuxPVonHVMdrivers
For example, look at one of the following configurations
disk = [' File:/system.img,hda,w ', ' file:/disk1.img,sda,w ', ' file:/disk2.img,xvda,w ',]
For HDA, for example, to specify the ide0=noprobe when starting the DOM0, this will not simulate HDA with QEMU-DM, or QEMU will use SDA driver to simulate SDA. , and Xvda such devices are not used QEMU-DM to simulate, if the use of PV driver, designated XVDA, xvdb such equipment is the best choice
The "Block Xen" Virtual block Device 0 =/dev/xvda-i- VBD Whole Disk
=/dev/xvdb Second Xen VB D whole Disk
=/DEV/XVDC Third Xen VBD whole disk
...
/DEV/XVDP Sixteenth Xen VBD Whole disk partitions are handled in the same as for
IDE
Way Jor number 3) except the limit on
partitions is 15.
If the PV driver is properly installed, DMESG | Egrep-i ' Xen|front ' can see the following information
[ 0.000000] Xen Platform pci:i/o Protocol version 1
[ 0.000000] NetFront and the Xen Platform PCI driver have Been compiled for this kernel:unplug emulated NICs.
[ 0.000000] Blkfront and the Xen platform PCI driver have been compiled for this kernel:unplug emulated disks
[
0.000000] Xen HVM callback vector for event delivery is enabled
[ 2.377167] vbd vbd-5632:19 xenbus_dev_probe o n device/vbd/5632
[ 2.378134] Blkfront:xvda:flush diskcache:enabled
[ 6.266448] initialising Xen Virtual Ethernet driver.