All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	xen-devel@lists.xensource.com, Wei Liu <wei.liu2@citrix.com>
Subject: Re: [xen-unstable test] 100789: regressions - FAIL [and 2 more messages]
Date: Thu, 8 Sep 2016 16:17:26 +0100	[thread overview]
Message-ID: <20160908151726.GH12697@citrix.com> (raw)
In-Reply-To: <22481.29802.806114.688233@mariner.uk.xensource.com>

On Thu, Sep 08, 2016 at 03:23:38PM +0100, Ian Jackson wrote:
> Wei Liu writes ("Re: [Xen-devel] [xen-unstable test] 100789: regressions - FAIL"):
> > I see three ways to move this forward.
> >
> > 3. Retire these two tests.
> 
> Do we expect users still to want VHD support ?  We still allegedly
> support VHD for guests.  So we shouldn't retire these tests unless we
> are dropping VHD support entirely.
> 
> AFAICT users who want VHD support need to be able to create images
> etc.
> 
> > 2. Install blktap-utils shipped in Debian (available from Wheezy
> >    onwards), the main difficulty would be the package depends on a dkms
> >    package that seems to require building with kernel header when
> >    installing.
> 
> According to Debian, we (Xen) are upstream for this package.  It makes
> no sense for osstest to install something from Debian which we have
> deleted upstream !
> 
> > 1. Resurrect vhd-util from blktap2.
> 
> What is wrong with this plan ?
> 
> > In the meantime, if we want to avoid blocking xen-unstable for too long,
> > we might want to force push.
> 
> If that's a consideration, we should be considering a revert, not a
> force push.
> 
> Andrew Cooper writes ("Re: [Xen-devel] [xen-unstable test] 100789: regressions - FAIL"):
> > +1 to a force push for now.  There are quite a few changes currently
> > blocked.
> 
> IMO that is not a good reason for a force push.
> 
> Wei Liu writes ("Re: [Xen-devel] [xen-unstable test] 100789: regressions - FAIL"):
> > 4. Provide a pre-made vhd image.
> > 
> > vhd-util create disk.vhd -s 10000 -> 24K in actual size.
> 
> This is no good because
> 
> 1. disk.vhd is a file for which we would have deleted the source code!
> 
> 2. Users need the ability to create images.
> 

It seems that we have different expectations on how things work.

I will revert that two patches now. Let's sort out the story later.

Wei.

> Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

      reply	other threads:[~2016-09-08 15:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-08  5:32 [xen-unstable test] 100789: regressions - FAIL osstest service owner
2016-09-08  9:43 ` Wei Liu
2016-09-08  9:45   ` Andrew Cooper
2016-09-08 12:58   ` Wei Liu
2016-09-08 14:23     ` [xen-unstable test] 100789: regressions - FAIL [and 2 more messages] Ian Jackson
2016-09-08 15:17       ` Wei Liu [this message]

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=20160908151726.GH12697@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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.