On 11.11.2013 13:06, Ian Campbell wrote: > On Mon, 2013-11-11 at 12:54 +0100, Vladimir 'φ-coder/phcoder' Serbinenko > wrote: >> On 11.11.2013 11:10, Ian Campbell wrote: >>> On Sat, 2013-11-09 at 21:52 +0100, Vladimir 'φ-coder/phcoder' Serbinenko >>> wrote: >>>> Hello, all. pvgrub2 has just became part of upstream grub as ports >>>> i386-xen and x86_64-xen. >>> >>> This is super cool, thanks! >>> >> You're welcome >>>> http://git.savannah.gnu.org/cgit/grub.git >>>> >>>> Documentation on its usage is missing for now but in short: >>>> ARCH=x86_64 >>>> ./autogen.sh >>>> ./configure --target=$ARCH --with-platform=xen >>> >>> Does this enable Xen statically for the resulting binaries or is it a >>> dynamic/boot time selection between Xen and native? >>> >> The result binaries are xen only. Dynamic selection makes very little >> sense for bootloader. > > Right this is what I expected. > > Can it coexist alright with a native grub? e.g. will grub-makestandalone > pick the right inputs based on -O $arch-xen instead of -O $arch? > Coexistance of ports is no problem. All files between ports which share the name also share the contents. Files which differ have different names ( E.g. /usr/lib/grub/{i386-pc,i386-efi,i386-xen,x86_64-xen,x86_64-efi}/*.mod) >>> Also, does this require any code from Xen (libxc, minios etc) at build >>> time or is it completely standalone? >>> >> It needs xen headers (/ur/include/xen). On debian those are in libxen-devel > > So no requirement for e.g. a Xen source tree. That should make things > much easier for the distros... > > Thanks. > Ian. > >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel