From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Xen 4.3 PCI passthrough possible bug Date: Mon, 10 Feb 2014 13:47:07 -0500 Message-ID: <20140210184707.GA18755@phenom.dumpdata.com> References: <5aa3cfb2-f554-449a-b251-13b69ac35185@default> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Mike Neiderhauser Cc: George Dunlap , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org 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 wrote: > > > On Sat, Feb 8, 2014 at 5:42 PM, Mike Neiderhauser > > 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 > >