On 10/30/2015 12:14 PM, Charles Arnold wrote:
On 10/30/2015 at 12:54 PM, PGNet Dev <[email protected]> wrote:
I'd recently attempted to boot an Opensuse DomU, on Opensuse Dom0,
switching to pvgrub2 rather than pygrub as the bootloader mechanism.
You may want to use what the installer tools use (virt-install and vm-install)
and that is grub.xen to boot your domU from the grub2-x86_64-xen RPM. Be
sure to pull the latest channel updates.
pygrub cannot read a btrfs file system to get boot information for starting the
VM.
The syntax for a configuration file is,
kernel="/usr/lib/grub2/x86_64-xen/grub.xen"
I'm not looking to add complexity to the boot stack -- for either Dom0
or the DomUs.
I don't want to install/use virt-install or vm-install.
I'd like to keep it bog simple. No auto-magic, no installer layers, etc
Simply use already provided Xen-native xl to boot a txt-based, clear &
easy to read GUEST.cfg, specifying the pvgrub2 'kernel=' line.
As mentioned in my referenced post, my
kernel = /home/tmp/pvgrub2/grub-x86_64-xen
failed, where that file's generated with
grub2-mkstandalone \
-o grub-x86_64-xen \
-O x86_64-xen \
boot/grub2/grub-xen-pvgrub2.cfg
Can you detail how
/usr/lib/grub2/x86_64-xen/grub.xen
is generated?
Also, you re-mention pygrub ("pygrub cannot read ...").
I'm specifically looking to ensure that pygrub is EXCLUDED from the
process, and that only PVGRUB2 is used.
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
