[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] pvgrub2 is merged

From: Vladimir 'φ-coder/phcoder' Serbinenko
Subject: Re: [Xen-devel] pvgrub2 is merged
Date: Mon, 11 Nov 2013 13:52:18 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131005 Icedove/17.0.9

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
>>>> Documentation on its usage is missing for now but in short:
>>>> ARCH=x86_64
>>>> ./
>>>> ./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.
>>> 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.

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]