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] Add basic PVH flights.
Date: Wed, 10 Dec 2014 13:58:37 +0000 [thread overview]
Message-ID: <1418219917.3505.57.camel@citrix.com> (raw)
In-Reply-To: <21640.20738.890057.47682@mariner.uk.xensource.com>
On Wed, 2014-12-10 at 13:56 +0000, Ian Jackson wrote:
> Ian Campbell writes ("[PATCH OSSTEST] Add basic PVH flights."):
> > These are the usual PV debian flights with pvh=1 added to the
> > configuration file.
> >
> > A job is created for each of Intel and AMD, although obviously AMD is
> > expected to fail at the moment.
> ...
> > Beyond that I've not tested this at all I fully expect even Intel to
> > fail in the first instance, due to issues such as lack of necessary
> > kernel options etc. I suggest to take this now and iterate on any
> > further changes.
>
> That seems reasonable.
>
> > For a xen-unstable flight this results in these runvars:
> > diff --git a/ts-debian-fixup b/ts-debian-fixup
> > index f001418..00477c5 100755
> > --- a/ts-debian-fixup
> > +++ b/ts-debian-fixup
> > @@ -118,6 +118,12 @@ sub otherfixupcfg () {
> ...
> > + my $pvh = guest_var($gho,'pvh',undef);
> > + if ($pvh) {
> > + $cfg =~ s/^pvh.*//mg;
>
> This should probably be
>
> + $cfg =~ s/^pvh\b.*//mg;
>
> unless you deliberately intend to strip out any other phv-related
> settings which xen-create-image might put there ?
Nope, your suggest is a good one.
Shall I resent or are you ok for me to do this change as I commit?
next prev parent reply other threads:[~2014-12-10 13:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 9:55 [PATCH OSSTEST] Add basic PVH flights Ian Campbell
2014-12-10 13:56 ` Ian Jackson
2014-12-10 13:58 ` Ian Campbell [this message]
2014-12-10 14:03 ` Ian Jackson
2014-12-10 14:30 ` Ian Campbell
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=1418219917.3505.57.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.