xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Atom2 <ariel.atom2@web2web.at>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [BUG] XEN 4.3.3 - segfault in xl create for HVM with PCI passthrough
Date: Tue, 04 Nov 2014 17:48:29 +0100	[thread overview]
Message-ID: <5459035D.5010204@web2web.at> (raw)
In-Reply-To: <1415118690.11486.53.camel@citrix.com>

Am 04.11.14 um 17:31 schrieb Ian Campbell:
> On Tue, 2014-11-04 at 17:14 +0100, Atom2 wrote:
>> Am 04.11.14 um 16:44 schrieb Ian Campbell:
>>> On Tue, 2014-11-04 at 16:13 +0100, Atom2 wrote:
>>> Otherwise I think the next step would be to downgrade to 4.3.1 and see
>>> if the problem persists, in order to rule out changes elsewhere in the
>>> system. If the problem doesn't happen with a 4.3.1 rebuilt on your
>>> current system then the next thing would probably be to bisect the
>>> issue. There are only 31 toolstack changes in that range, so it ought to
>>> only take 5-6 iterations.
>> Unfortunately 4.3.1 is no longer available as an ebuild as 4.3.3 seemed
>> to fix security issues and therefore 4.3.1 has been deleted from the
>> repos. So it's not straightforward and I need to figure out how to get
>> the old version back. But I am sure there's a way.
>
> I don't know anything about ebuilds, but if you end up needing to bisect
> then building from xen.git might be useful anyway (unless you can get an
> ebuild to trivially build some other version).
Before I go down that route would I also need to re-compile xen (i.e. 
the hypervisor at /boot/xen-4.3.3.gz that's being booted from grub) or 
only xen-tools? In other words does xen-tools 4.3.1 work with the 
hypervisor version 4.3.3 under /boot? I wouldn't want to end up with an 
unbootable system.

In terms of ebuilds: Adding patches to a version is pretty easy as 
gentoo works from source code. So if 4.3.3 is just different by a number 
of well defined patches from 4.3.1 then that should be straightforward 
as applying patches is really trivial.

Thanks Atom2

  reply	other threads:[~2014-11-04 16:48 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-27 21:25 segfault in xl create for HVM with PCI passthrough Atom2
2014-10-28 10:59 ` Ian Campbell
2014-10-28 15:39   ` Atom2
2014-10-28 16:04     ` Ian Campbell
2014-10-29  0:26       ` Atom2
2014-10-30 23:05         ` Atom2
2014-11-04 15:13           ` [BUG] XEN 4.3.3 - " Atom2
2014-11-04 15:44             ` Ian Campbell
2014-11-04 16:14               ` Atom2
2014-11-04 16:31                 ` Ian Campbell
2014-11-04 16:48                   ` Atom2 [this message]
2014-11-05  9:33                     ` Ian Campbell
2014-11-04 17:30                   ` Atom2
2014-11-05  9:45                     ` Ian Campbell
2014-11-05 12:01                       ` Atom2
2014-11-05 12:39                         ` Ian Campbell
2014-11-05 12:45                           ` Andrew Cooper
2014-11-05 12:47                             ` Ian Campbell
2014-11-06 15:11                           ` Atom2
2014-11-10 11:16                             ` Ian Campbell
2014-11-10 11:44                               ` Atom2
2014-11-10 12:09                                 ` Ian Campbell
2014-12-01  3:34                                   ` Dennis Lan (dlan)
2014-12-01  9:38                                     ` Ian Campbell
2014-11-09 23:03       ` Atom2

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=5459035D.5010204@web2web.at \
    --to=ariel.atom2@web2web.at \
    --cc=Ian.Campbell@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).