From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen 4.4 development update: Is PVH a blocker?
Date: Mon, 16 Dec 2013 12:46:35 -0500 [thread overview]
Message-ID: <20131216174635.GA23286@phenom.dumpdata.com> (raw)
In-Reply-To: <16110253000.20131216182420@eikelenboom.it>
On Mon, Dec 16, 2013 at 06:24:20PM +0100, Sander Eikelenboom wrote:
>
> Monday, December 16, 2013, 4:09:06 PM, you wrote:
>
> >> >> * qemu-upstream not freeing pirq
> >> >> > http://www.gossamer-threads.com/lists/xen/devel/281498
> >> >> > http://marc.info/?l=xen-devel&m=137265766424502
> >> >> status: patches posted; latest patches need testing
> >> >> Not a blocker.
> >>
> >> > I can't test it, b/c qemu-upstream does not work with PCI passthrough
> >> > anymore.
> >>
> >> Strange, pci passthrough in general works for me on "simple" pci devices (usb cards, videograbber) with latest qemu-upstream and seabios upstream.
> >> (if you have no need for pci rombars, no vga passthrough, no need for specifying funky things about which virtual functions to passthrough)
> >>
> >> What are you trying to passthrough ?
>
> > -bash-4.1# lspci -s 01:00.0 -v
> > 01:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
> > Subsystem: Intel Corporation Gigabit ET Dual Port Server Adapter
> > Flags: fast devsel, IRQ 16
> > Memory at fbc20000 (32-bit, non-prefetchable) [disabled] [size=128K]
> > Memory at fb800000 (32-bit, non-prefetchable) [disabled] [size=4M]
> > I/O ports at e020 [disabled] [size=32]
> > Memory at fbc44000 (32-bit, non-prefetchable) [disabled] [size=16K]
> > Expansion ROM at fb400000 [disabled] [size=4M]
> > Capabilities: [40] Power Management version 3
> > Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
> > Capabilities: [70] MSI-X: Enable- Count=10 Masked-
> > Capabilities: [a0] Express Endpoint, MSI 00
> > Capabilities: [100] Advanced Error Reporting
> > Capabilities: [140] Device Serial Number 00-1b-21-ff-ff-45-d9-ac
> > Capabilities: [150] Alternative Routing-ID Interpretation (ARI)
> > Capabilities: [160] Single Root I/O Virtualization (SR-IOV)
> > Kernel driver in use: pciback
> > Kernel modules: igb
>
>
> >> What problems do you have / errors do you see ?
> >>
>
> > http://www.gossamer-threads.com/lists/xen/devel/309476?do=post_view_threaded
>
>
> Could it be related to the outstanding issue (since 4.3) of:
>
> * PCI hole resize support hvmloader/qemu-traditional/qemu-upstream with PCI/GPU passthrough
> > http://lists.xen.org/archives/html/xen-devel/2013-05/msg02813.html
> > Where Stefano writes:
> > 2) for Xen 4.4 rework the two patches above and improve
> > i440fx_update_pci_mem_hole: resizing the pci_hole subregion is not
> > enough, it also needs to be able to resize the system memory region
> > (xen.ram) to make room for the bigger pci_hole
>
> Your card seems to need quite some resources, and restricted to 32bit, even other SR-IOV cards seems to to with less and or support 32 bit.
>
I don't think that is the problem. The QEMU-xen did work at some point - until
I blew away 'qemu-xen-dir' to get the newest and best. So I think the problem
I am seeing is with QEMU 1.6 regression.
next prev parent reply other threads:[~2013-12-16 17:46 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 19:21 Xen 4.4 development update: Is PVH a blocker? George Dunlap
2013-12-13 19:39 ` Konrad Rzeszutek Wilk
2013-12-13 20:55 ` Sander Eikelenboom
2013-12-16 15:09 ` Konrad Rzeszutek Wilk
2013-12-16 17:24 ` Sander Eikelenboom
2013-12-16 17:46 ` Konrad Rzeszutek Wilk [this message]
2013-12-16 17:59 ` Sander Eikelenboom
2013-12-16 19:34 ` Konrad Rzeszutek Wilk
2013-12-16 19:46 ` Sander Eikelenboom
2013-12-17 14:35 ` Konrad Rzeszutek Wilk
2013-12-17 15:03 ` Sander Eikelenboom
2013-12-17 21:35 ` Konrad Rzeszutek Wilk
2013-12-17 21:52 ` Sander Eikelenboom
2013-12-17 15:04 ` Anthony Liguori
2013-12-17 15:18 ` Konrad Rzeszutek Wilk
2013-12-16 10:51 ` Ian Campbell
2013-12-16 15:12 ` Konrad Rzeszutek Wilk
2013-12-16 15:24 ` Konrad Rzeszutek Wilk
2013-12-16 15:43 ` Ian Campbell
2013-12-13 19:43 ` Konrad Rzeszutek Wilk
2013-12-16 10:50 ` George Dunlap
2013-12-16 10:54 ` Ian Campbell
2013-12-16 15:10 ` Konrad Rzeszutek Wilk
2013-12-19 14:06 ` Ian Campbell
2013-12-19 14:15 ` Processed: " xen
2013-12-16 8:47 ` Jan Beulich
2013-12-16 23:45 ` Mukesh Rathor
2013-12-17 8:25 ` Jan Beulich
2013-12-17 11:58 ` Tim Deegan
2013-12-17 14:13 ` George Dunlap
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=20131216174635.GA23286@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=linux@eikelenboom.it \
--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).