From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Mike Neiderhauser <mikeneiderhauser@gmail.com>
Cc: George Dunlap <dunlapg@umich.edu>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen 4.3 PCI passthrough possible bug
Date: Mon, 10 Feb 2014 13:47:07 -0500 [thread overview]
Message-ID: <20140210184707.GA18755@phenom.dumpdata.com> (raw)
In-Reply-To: <CA+XTOOh3cGk8fGnhSuURKnW+B1bnxYVtjRZTB6F4DLQcrA=XmA@mail.gmail.com>
On Mon, Feb 10, 2014 at 01:29:22PM -0500, Mike Neiderhauser wrote:
> Thanks for the answers on the timeline.
>
> When I start the HVM with th broadcom adapter, I get this message back.
> Parsing config from /etc/xen/ubuntu-hvm-1.cfg
> libxl: error: libxl_pci.c:990:libxl__device_pci_reset: The kernel doesn't
> support reset from sysfs for PCI device 0000:05:00.0
> libxl: error: libxl_pci.c:990:libxl__device_pci_reset: The kernel doesn't
> support reset from sysfs for PCI device 0000:05:00.1
>
> However, the devices appear in the HVM. Is this something that I should be
> concerned about?
No. Xen pciback does the reset automatically.
Actually we might want to ditch that reporting in libxl, or maybe just
implement a stub function in xen-pciback so that libxl will be happy.
>
>
>
> On Mon, Feb 10, 2014 at 12:11 PM, George Dunlap <dunlapg@umich.edu> wrote:
>
> > On Sat, Feb 8, 2014 at 5:42 PM, Mike Neiderhauser
> > <mikeneiderhauser@gmail.com> wrote:
> > > Works like a charm. I do not have physical access to the computer this
> > > weekend to verify that the cards are isolated, but the HVM starts and
> > > appears to be working well.
> > >
> > > When do you think Xen 4.4 will be released. The article I read
> > mentioned it
> > > will be released in 2014 (hinting towards the end of February). I also
> > read
> > > 'When it is ready.'
> > >
> > > Any timeline would be great.
> >
> > I'm afraid that's about all we can give. :-) We've locked down
> > development for 2 months now and are working on finding and fixing
> > bugs. If there are no more blocker bugs or other unforeseen delays,
> > it should be out by the end of February. But there are necessarily
> > significant unknowns, so we can't make any promises.
> >
> > -George
> >
next prev parent reply other threads:[~2014-02-10 18:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-08 15:36 Xen 4.3 PCI passthrough possible bug Konrad Wilk
2014-02-08 15:37 ` Mike Neiderhauser
2014-02-08 17:42 ` Mike Neiderhauser
2014-02-08 20:02 ` Pasi Kärkkäinen
2014-02-10 17:11 ` George Dunlap
2014-02-10 18:29 ` Mike Neiderhauser
2014-02-10 18:47 ` Konrad Rzeszutek Wilk [this message]
2014-02-11 13:04 ` Mike Neiderhauser
2014-02-12 18:25 ` Konrad Rzeszutek Wilk
2014-02-12 18:34 ` Mike Neiderhauser
-- strict thread matches above, loose matches on Subject: below --
2014-02-06 14:39 Mike Neiderhauser
2014-02-07 15:25 ` Konrad Rzeszutek Wilk
2014-02-07 15:53 ` Mike Neiderhauser
2014-02-07 18:30 ` Konrad Rzeszutek Wilk
2014-02-07 18:40 ` Mike Neiderhauser
2014-02-07 20:36 ` Mike Neiderhauser
2014-02-07 20:39 ` Konrad Rzeszutek Wilk
2014-02-07 20:45 ` Mike Neiderhauser
2014-02-07 21:01 ` Konrad Rzeszutek Wilk
2014-02-07 21:29 ` Mike Neiderhauser
2014-02-07 21:49 ` Konrad Rzeszutek Wilk
2014-02-08 1:16 ` Mike Neiderhauser
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=20140210184707.GA18755@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=dunlapg@umich.edu \
--cc=mikeneiderhauser@gmail.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).