Re: [Xen-API] [xs-devel] pypxeboot (or similar) under XCP 1.6 - xenpvnetboot

[Andrew Cooper <andrew.cooper3@xxxxxxxxxx>]

On 10/07/13 19:50, James Bulpin wrote:
> Hi Alexandre,
>
> Good spot. XenServer 6.x and XCP 1.6 all use Xen 4.1 so won't have this 
> feature. XenServer will be moving to Xen 4.3 soon. xenpvnetboot is a drop-in 
> replacement for pygrub so in theory when we get Xen 4.3 in XS you'll be able 
> to use the PV-bootloader and PV-bootloader-args VM params to use it as 
> documented on the wiki page but that'll probably require a couple of xapi 
> hacks to make it permit the alternative bootloader and ensure the PV-kernel 
> etc. args are all passed through to it properly.
>
> FWIW you might even be able to manually drop the xenpvnetboot script onto a 
> XenServer or XCP system based on Xen 4.1 but that'll still need the above 
> xapi hacks.
>
> Regards,
> James

PV-bootloader will not pick stuff up from the path.  It is restricted to
"pygrub" or "eliloader"

One hack which might work for you:

Move /usr/bin/pygrub sideways and create /usr/bin/pygrub as a shell
script with a correct shebang line.

Have that shell script choose between the sideways pygrub in the usual
case, passing "$@" to it, or xenpvnetboot based on some specific
indication.  This also gives you the ability to correctly mutate the
command line options passed to xenpvnetboot.  (Because of the above
restriction, on a XenServer system pygrub and eliloader must accept
identical command line arguments, meaning that we are somewhat different
from any upstream version)

I frequently use the above shell script trick while developing, for
doing things such as wrapping valgrind/strace around sub components.

~Andrew

>
>> -----Original Message-----
>> From: xen-api-bounces@xxxxxxxxxxxxx [mailto:xen-api-bounces@xxxxxxxxxxxxx]
>> On Behalf Of Alexandre Kouznetsov
>> Sent: 10 July 2013 19:12
>> To: xen-api@xxxxxxxxxxxxx
>> Subject: Re: [Xen-API] pypxeboot (or similar) under XCP 1.6 - xenpvnetboot
>>
>> Hello.
>>
>> By causality I found a reference to "xenpvnetboot", which seems to solve
>> my problem and is supported since a year ago, in Xen 4.2.
>>
>> http://wiki.xen.org/wiki/Xenpvnetboot_:_A_network_bootloader_for_Xen_PV_gu
>> est
>>
>> It's mentioned on http://www.linux.org.ru/news/opensource/8240913
>> (russian), but not on
>> http://blog.xen.org/index.php/2012/09/17/xen-4-2-0-released/ .
>>
>> Debian package search engiene says it's included in xen-utils-4.2 under
>> Sid:
>> http://packages.debian.org/search?suite=sid&arch=any&searchon=contents&key
>> words=Xenpvnetboot
>>
>> By chance, does it works somehow under XCP or XenServer? I found no
>> reference documentation yet.
>>
>> Greetings
>>
>> El 04/07/13 14:02, Alexandre Kouznetsov escribió:
>>> Hello.
>>>
>>> Is there a reasonable clean way to get a PV domain to boot using
>>> existing PXE infrastructure instead of a regular VBD? Would be great to
>>> have it working "off the shelf", but if not, after a minimally invasive
>>> procedure.
>>>
>>> All the reference I have found about the subject suggests using
>>> pypxegrub, but only the usage with a regular Xen is described.
>>>
>>> "xe vm-param-list" tells me about "PV-bootloader", usually set to
>>> "pygrub" on PV guests. Is it a keyword, or the actual name of executable
>>> file to run and may be anything within PATH? In that case, maybe I can
>>> manually install pypxeboot to my XCP or XenServer host and archive my
>> goal.
>>> Have anybody done that already?
>>> Is there a known cleaner way?
>>>
>>> Thank you.
>>>
>>
>> --
>> Alexandre Kouznetsov
>> Systems Officer
>> Ondore, S.A. de C.V.
>> Tel. +52(55) 5559-0090
>> E-mail alk@xxxxxxxxxx
>>
>> _______________________________________________
>> Xen-api mailing list
>> Xen-api@xxxxxxxxxxxxx
>> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api


_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api