|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH OSSTEST v2 10/15] distros: support booting Debian PV (d-i installed) guests with pvgrub.
On Fri, 2014-05-02 at 15:18 +0100, Ian Jackson wrote:
> Ian Campbell writes ("Re: [PATCH OSSTEST v2 10/15] distros: support booting
> Debian PV (d-i installed) guests with pvgrub."):
> > On Fri, 2014-05-02 at 14:03 +0100, Ian Jackson wrote:
> > > > - my $blcfg = <<END;
> > > > + my $pvgrub = {
> > > > + i386 => "/usr/local/lib/xen/boot/pv-grub-x86_32.gz",
> > > > + amd64 => "/usr/local/lib/xen/boot/pv-grub-x86_64.gz"
> > > > + };
> > >
> > > I wonder, though, whether this knowledge about arch name mappings
> > > could be combined with that from
> > > ts-kernel-build:config_create_config_sh and put in Osstest.pm or
> > > somewhere.
> >
> > As in some sort of Osstest::arch_params{PvGrub}, {LinuxDefconfg},
> > {LinuxKernelImage} ?
> >
> > I think so.
>
> I was thinking
>
> our %arch_debian2xen = qw(i386 x86_32
> amd64 x86_64
> armhf armhf);
> our %arch_xen2debian;
> $arch_xen2debian{$arch_debian2xen{$_}} = $_ foreach keys %arch_debian2xen;
Wowza!
Do we need xen2debian anywhere? Mostly we have a debian thing and need a
Xen (or a Linux) thing.
> or some such.
>
> Then
>
> my $xenarch = $arch_debian2xen{$arch};
> my $pvgrub = "/usr/local/lib/xen/boot/pv-grub-$xenarch.gz";
>
> Or is that conceptually wrong ?
Not inherently, I don't think.
You mean to do the same for $arch_debian2linux for the ts-kernel-build
stuff I guess?
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |