PvGrub: Difference between revisions

From Xen
Jump to navigationJump to search
(Migrated page)
 
m (Removed superfluous <nowiki></nowiki> tag pairs.)
Line 12: Line 12:
* Boot domU from local disk:
* Boot domU from local disk:


<pre><nowiki>
<pre>
kernel = "/usr/lib/xen/boot/pv-grub-x86_32.gz"
kernel = "/usr/lib/xen/boot/pv-grub-x86_32.gz"
extra = "(hd0,0)/grub/menu.lst"
extra = "(hd0,0)/grub/menu.lst"
</nowiki></pre>
</pre>


* Boot domU from network:
* Boot domU from network:


<pre><nowiki>
<pre>
kernel = "/usr/lib/xen/boot/pv-grub-x86_32.gz"
kernel = "/usr/lib/xen/boot/pv-grub-x86_32.gz"
extra = "(nd)/grub/menu.lst"
extra = "(nd)/grub/menu.lst"
</nowiki></pre>
</pre>


You should setup the DHCP server and TFTP server correctly. Create ${tftproot}/grub/menu.lst; copy necessary files (vmlinuz, initrd, etc.).
You should setup the DHCP server and TFTP server correctly. Create ${tftproot}/grub/menu.lst; copy necessary files (vmlinuz, initrd, etc.).

Revision as of 22:16, 28 November 2011


PV-GRUB replaces PyGrub to boot domU images safely: it runs the regular grub inside the created domain itself and uses regular domU facilities to read the disk / fetch files from network etc.; it eventually loads the PV kernel and chain-boots it.

Configuration

  • Boot domU from local disk:
kernel = "/usr/lib/xen/boot/pv-grub-x86_32.gz"
extra = "(hd0,0)/grub/menu.lst"
  • Boot domU from network:
kernel = "/usr/lib/xen/boot/pv-grub-x86_32.gz"
extra = "(nd)/grub/menu.lst"

You should setup the DHCP server and TFTP server correctly. Create ${tftproot}/grub/menu.lst; copy necessary files (vmlinuz, initrd, etc.).

Reference