From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Steven Haigh <netwiz@crc.id.au>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Andreas Falck <falck.andreas.lists@gmail.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Gordan Bobic <gordan@bobich.net>, Jan Beulich <JBeulich@suse.com>
Subject: Re: PCI passthrough problems after legacy update of xen 4.1
Date: Mon, 20 May 2013 09:55:09 +0100 [thread overview]
Message-ID: <5199E4ED.8080304@citrix.com> (raw)
In-Reply-To: <51997338.3050605@crc.id.au>
On 20/05/13 01:50, Steven Haigh wrote:
> On 20/05/2013 5:59 AM, Gordan Bobic wrote:
>> I stand corrected! Jan's patch does in fact fix the problem. I have no
>> idea what I was doing wrong, but I just tried it again (for the 4th
>> time) just to make sure, uninstalled the old packages, installed the new
>> ones - and now it works! There must have been a stale file somewhere
>> that was breaking it.
>>
>> Thanks Jan, most appreciated. :)
> This is great news...
>
> Jan / Ian / Andrew:
>
> What is the path forward for this now? Will it just be committed then
> included in 4.2.3 or 4.1.x? I'm just trying to figure out if this will
> be the official fix or something else will happen before I start rolling
> new packages with this fix applied for distribution...
>
It looks to me like a good fix. It is however a libxc bugfix so is at
the discretion of the tools maintainers.
~Andrew
next prev parent reply other threads:[~2013-05-20 8:55 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAvQYUSQnM26ofCStMuSeLPbabmy7_tksELHrJvi6V=jq6_PvQ@mail.gmail.com>
[not found] ` <7fe927daf168b95128153bf104715689@mail.shatteredsilicon.net>
2013-05-01 14:22 ` [Xen-users] PCI passthrough problems after legacy update of xen 4.1 Andreas Falck
[not found] ` <CAAvQYUT8jeYm57WGEYMgJ9sWQjwP4i=E69ZdkhUswxe-pjLW0Q@mail.gmail.com>
2013-05-02 11:56 ` Jan Beulich
2013-05-02 12:42 ` Andreas Falck
[not found] ` <CAAvQYUTWT9Y24UbwVn3kzEW8Di+MtX8APGz7pGvsiv+f_LovjQ@mail.gmail.com>
2013-05-02 13:35 ` Jan Beulich
2013-05-02 18:57 ` Andreas Falck
[not found] ` <CAAvQYUR411fF__Yfc6EPUOzxCndhXv9qdz-cD1A93-GVaz_ETA@mail.gmail.com>
2013-05-02 21:07 ` Andreas Falck
[not found] ` <CAAvQYUTM8U-mBK3k3A+AOZ4gEhjAKtkparGY2dxTXsy08+Tn0A@mail.gmail.com>
2013-05-03 7:29 ` Jan Beulich
2013-05-03 13:31 ` Andreas Falck
2013-05-03 13:51 ` Jan Beulich
2013-05-03 13:57 ` Andrew Cooper
2013-05-03 14:39 ` Jan Beulich
2013-05-03 14:56 ` Andreas Falck
2013-05-03 15:03 ` Jan Beulich
2013-05-03 18:59 ` Andreas Falck
2013-05-05 19:33 ` Andreas Falck
2013-05-06 7:53 ` Jan Beulich
2013-05-14 14:01 ` Jan Beulich
2013-05-14 14:05 ` Gordan Bobic
2013-05-14 19:30 ` Gordan Bobic
2013-05-15 7:06 ` Jan Beulich
2013-05-15 7:24 ` PCI passthrough problems after XSA46 patch Gordan Bobic
2013-05-15 7:50 ` Jan Beulich
2013-05-17 19:29 ` Gordan Bobic
2013-05-16 12:20 ` Jan Beulich
2013-05-17 19:56 ` Gordan Bobic
2013-05-16 6:41 ` PCI passthrough problems after legacy update of xen 4.1 Andreas Falck
2013-05-19 14:56 ` Andreas Falck
2013-05-19 19:59 ` Gordan Bobic
2013-05-20 0:50 ` Steven Haigh
2013-05-20 8:55 ` Andrew Cooper [this message]
2013-05-20 9:13 ` Ian Campbell
2013-05-21 8:28 ` Jan Beulich
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=5199E4ED.8080304@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=falck.andreas.lists@gmail.com \
--cc=gordan@bobich.net \
--cc=netwiz@crc.id.au \
--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.