diff options
Diffstat (limited to 'os-plugins/plugins/xen/files/xen.examples/examples/xmexample.domUloader')
-rw-r--r-- | os-plugins/plugins/xen/files/xen.examples/examples/xmexample.domUloader | 28 |
1 files changed, 28 insertions, 0 deletions
diff --git a/os-plugins/plugins/xen/files/xen.examples/examples/xmexample.domUloader b/os-plugins/plugins/xen/files/xen.examples/examples/xmexample.domUloader new file mode 100644 index 00000000..6edfdbc2 --- /dev/null +++ b/os-plugins/plugins/xen/files/xen.examples/examples/xmexample.domUloader @@ -0,0 +1,28 @@ +# This is a bootloader used to boot paravirtualized domains. You can optionally +# plug in a different boot loader here, e.g., pygrub. There is usually no +# reason to change this. Don't explicitly specify kernel and ramdisk if you use +# a bootloader. +bootloader="/usr/lib/xen/boot/domUloader.py" + +# The domUloader will pull the specified kernel and initrd out of the domU's +# disk, and use that to boot. This is easier to manage, compared to manually +# keeping a copy of the kernel and initrd in sync in dom0's filesystem and +# pointing to them with the "kernel" and "ramdisk" parameters. Syntax is +# "VDEV:KERNEL,INITRD", where VDEV is the block device (from domU's point of +# view) within which KERNEL and INITRD can be found. +bootentry = "hda1:/boot/vmlinuz-xen,/boot/initrd-xen" + + +# Remaining settings for the example VM: +name="domUloader-example" +memory=512 +vcpus=1 +on_crash="destroy" +on_poweroff="destroy" +on_reboot="restart" +localtime=0 +builder="linux" +bootargs="--entry=xvda2:/boot/vmlinuz-xen,/boot/initrd-xen" +disk=[ 'file:/var/lib/xen/images/domUloader-example/disk0,xvda,w' ] +vif=[ 'mac=00:16:3e:00:01:02,bridge=xenbr0' ] +vfb=['type=vnc,vncunused=1'] |