Hi

> With openSUSE 13.2 and SLE12 the installation tools have begun using
> grub.xen (part of the grub2-x86_64-xen package) to boot these newer
> VMs.  The tools also continue to use pygrub on older VMs but this will
> likely change in the future.  grub.xen will boot both grub and grub2 based
> VMs.  It will also boot VMs that use BTRFS as the root filesystem which
> Xen's current version of pvgrub does not understand (nor does pygrub).


That's useful info.

I have these installed

rpm -qa | grep -i grub | sort
 grub2-2.02~beta2-20.5.1.x86_64
 grub2-branding-openSUSE-13.2-3.6.1.noarch
 grub2-i386-pc-2.02~beta2-20.5.1.x86_64
 grub2-snapper-plugin-2.02~beta2-20.5.1.noarch
 grub2-x86_64-efi-2.02~beta2-20.5.1.x86_64
 grub2-x86_64-xen-2.02~beta2-20.5.1.x86_64

The Dom0 is booted 

uname -rm
 3.19.3-1.gf10e7fc-xen x86_64

The Dom0 boot loader IS grub2, but I'm on a UEFI system. Xen's booted using the 
currently needed chainloader workaround.

I'm not sure if that means I'm using grub2-x86_64-efi or grub2-x86_64-xen.

Since I don't have a specific 'grub.xen' mentioned, are either of those all I 
need to boot the grub2-based VMs?  

More to the point, what specifically do I need to do to USE the pvgrub2 
capability to boot a grub2-based, ext4 using the guest's own kernel?

And in opensuse, does all that ^^ still work for either opensuse DomUs, using 
the opensuse-specific kernel-xen backport,  OR other-OSs using unmodified, 
pv-ops capable kernels?

LT
-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]

Reply via email to