xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH OSSTEST 3/7] ts-debian-di-install: Install pv-menu-list in ARM guests, always.
Date: Wed, 12 Aug 2015 16:44:43 +0100	[thread overview]
Message-ID: <1439394283.8356.59.camel@citrix.com> (raw)
In-Reply-To: <21963.26588.262832.107365@mariner.uk.xensource.com>

On Wed, 2015-08-12 at 16:35 +0100, Ian Jackson wrote:
> Ian Campbell writes ("[PATCH OSSTEST 3/7] ts-debian-di-install: Install 
> pv-menu-list in ARM guests, always."):
> > Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> 
> This package seems to be called `pv-grub-menu', not `pv-menu-list'.

I get that wrong more often than not it seems...

> 
> > @@ -190,9 +190,18 @@ END
> >  
> >  	$method_cfg = setup_netboot($tmpdir, $arch, $suite);
> >  
> > +	# We need the pv-menu-list package:
> > +	# - On x86 when running pvgrub, since it only speaks grub1
> > +	#   menu.lst syntax and by grub2 is now the only grub in
> > +	#   Debian.
> 
> This comment seems mangled.  "and by grub2" ?  Also in "it only speaks
> grub1", it would be clearer if "it" said "pvgrub".

Sure.

> > +	# - On ARM, which uses pygrub, because grub2 is not installed
> > +	#   on ARM by default (except for, maybe, UEFI guests in the
> > +	#   future, but not today).
> > +	my $pvmenulst = ($bl eq "pvgrub" || $arch =~ /arm/);
> 
> "pvgrub" here is pvgrub1, not pv grub2.  This could perhaps be
> clearer...

Yes, although pvgrub is what we use in production now. I could go and
change it everywhere if you like, or we could defer to the point where we
add pv grub 2 testing?

> 
> Thanks,
> Ian.

  reply	other threads:[~2015-08-12 15:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-06 12:44 [PATCH OSSTEST 0/7] Fixes for distros-debian-* flights on armhf Ian Campbell
2015-08-06 12:44 ` [PATCH OSSTEST 1/7] ts-logs-capture: Collect /var/log/xen/bootloader.*.log Ian Campbell
2015-08-12 15:30   ` Ian Jackson
2015-08-06 12:44 ` [PATCH OSSTEST 2/7] ts-debian-di-install: Use exit/poweroff in preference to exit/always_halt Ian Campbell
2015-08-12 15:30   ` Ian Jackson
2015-08-06 12:44 ` [PATCH OSSTEST 3/7] ts-debian-di-install: Install pv-menu-list in ARM guests, always Ian Campbell
2015-08-12 15:35   ` Ian Jackson
2015-08-12 15:44     ` Ian Campbell [this message]
2015-08-12 15:47       ` Ian Jackson
2015-08-06 12:44 ` [PATCH OSSTEST 4/7] ts-debian-di-install: Use the suite in the default hostname Ian Campbell
2015-08-12 15:39   ` Ian Jackson
2015-08-06 12:44 ` [PATCH OSSTEST 5/7] Debian: ARM: only apply no bootloader workaround if xopts{PvMenuLst} Ian Campbell
2015-08-12 15:40   ` Ian Jackson
2015-08-06 12:44 ` [PATCH OSSTEST 6/7] Debian: ARM has no bootloader (for Xen) even in Stretch Ian Campbell
2015-08-12 15:41   ` Ian Jackson
2015-08-06 12:44 ` [PATCH OSSTEST 7/7] Debian: Create /boot/boot -> . symlink on ARM when PvMenuLst enabled Ian Campbell
2015-08-12 15:41   ` Ian Jackson
2015-08-13 15:58     ` Ian Campbell
2015-08-13 18:05       ` Ian Jackson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1439394283.8356.59.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).