[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [BUG] After upgrade to Xen 4.12.0 iommu=no-igfx

On Thu, Aug 1, 2019 at 1:45 AM Roger Pau Monné <roger.pau@xxxxxxxxxx> wrote:
> On Wed, Jul 31, 2019 at 12:30:04PM -0700, Roman Shaposhnik wrote:
> > On Wed, Jul 31, 2019 at 1:36 AM Roger Pau Monné <roger.pau@xxxxxxxxxx> 
> > wrote:
> > >
> > > On Tue, Jul 30, 2019 at 10:55:24AM -0700, Roman Shaposhnik wrote:
> > > > Sorry -- got a bit distracted yesterday. Attached is the log with only
> > > > your latest patch attached. Interestingly enough the box booted fine
> > > > without screen artifacts. So I guess we're getting closer...
> > > >
> > > > Thanks for all the help!
> > >
> > > That's quite weird, there's no functional changes between the
> > > previous patches and this one, the only difference is that this patch
> > > has more verbose output.
> >
> > That's super weird indeed. I'm re-trying your very first patch right
> > now to see if it may be a pilot error on my part (hope not).
> >
> > > Are you sure you didn't have any local patches on top of Xen that
> > > could explain this difference in behaviour?
> >
> > Pretty sure -- but let me push my branch in EVE and show to you all
> > (you will need Docker installed to build Xen the way EVE does).
> I'm afraid it's quite hard for me to figure out whether you have any
> patches on top of Xen or not.

It is actually super simple. We use Docker containers as method for
guaranteeing that our build environment is always pristine and controlled.
Precisely to avoid this type of issues like random patches getting in, etc.

So... let me explain (not so much to convince you to use it, but rather
to have an extra pair of eye on an off chance that I actually missed

All of our builds steps are captured in the following Dockerfile:
it is based on Alpine Linux 3.7 and we only install the following
packages into a printing Alpine:
then we proceed with downloading Xen from a printing upsteram
and only apply patches that sit next to the Dockerfile and have
patch file extension:

At this point this is a single patch:
there's literally nothing else in that folder:

Then we proceed with building Xen in a very vanilla fashion:

That's it! That's literally all the build logic.

> For further testing can you make sure you don't have any custom
> patches on top of Xen (if you indeed had any in the previous
> attempts)?

I don't think there's any way for extra patches to sneak in, but please
see the above explanation.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.