From: Wei Liu <wei.liu2@citrix.com>
To: Anthony PERARD <anthony.perard@citrix.com>
Cc: xen-devel@lists.xenproject.org, stefano.stabellini@citrix.com,
wei.liu2@citrix.com
Subject: Re: qemu-xen-dir + PCI passthrough = BOOM
Date: Fri, 6 Dec 2013 16:00:18 +0000 [thread overview]
Message-ID: <20131206160018.GC4419@zion.uk.xensource.com> (raw)
In-Reply-To: <20131206153503.GS10855@perard.uk.xensource.com>
On Fri, Dec 06, 2013 at 03:35:04PM +0000, Anthony PERARD wrote:
> On Fri, Dec 06, 2013 at 09:49:36AM -0500, Konrad Rzeszutek Wilk wrote:
> > On Thu, Dec 05, 2013 at 12:16:32PM +0000, Anthony PERARD wrote:
> > > On Wed, Dec 04, 2013 at 02:51:48PM -0500, Konrad Rzeszutek Wilk wrote:
> > > > Hey,
> > > >
> > > > I just started noticing it today - with qemu-xen (tip is
> > > > commit b97307ecaad98360f41ea36cd9674ef810c4f8cf
> > > > xen_disk: mark ioreq as mapped before unmapping in error case)
> > > >
> > > > when I try to pass in a PCI device at bootup it blows up with:
> > > >
> > > > char device redirected to /dev/pts/2 (label serial0)
> > > > qemu: hardware error: xen: failed to populate ram at 40050000
> > >
> > > There is a good chance that the issue is in QEMU.
> > >
> > > By default, qemu-xen is not very verbose, so a
> > > #define XEN_PT_LOGGING_ENABLED
> > > can help identifying what is missing.
> > >
> > > The error is reported by xen_ram_alloc(), so it might help to enable
> > > trace for it. It's easy:
> > > sh$ cat > /tmp/trace-to-enable << EOF
> > > xen_ram_alloc
> > > EOF
> > >
> > > then
> > > device_model_args_hvm = [ '-trace', 'events=/tmp/trace-to-enable' ]
> > >
> > > There is more of those trace events in qemu.git/trace-events
> >
> > char device redirected to /dev/pts/2 (label serial0)
> > xen_ram_alloc requested: 0x3f800000, size 0x800000
> > xen_ram_alloc requested: 0x40000000, size 0x10000
> > xen_ram_alloc requested: 0x40010000, size 0x40000
> > [00:05.0] xen_pt_initfn: Assigning real physical device 01:00.0 to devfn
> > 0x28
> > [00:05.0] xen_pt_register_regions: IO region 0 registered
> > (size=0x20000lx base_addr=0xfbc20000lx type: 0)
> > [00:05.0] xen_pt_register_regions: IO region 1 registered
> > (size=0x400000lx base_addr=0xfb800000lx type: 0)
> > [00:05.0] xen_pt_register_regions: IO region 2 registered (size=0x20lx
> > base_addr=0xe020lx type: 0x1)
> > [00:05.0] xen_pt_register_regions: IO region 3 registered (size=0x4000lx
> > base_addr=0xfbc44000lx type: 0)
> > xen_ram_alloc requested: 0x40050000, size 0x400000
> > qemu: hardware error: xen: failed to populate ram at 40050000
>
> Those Xen report something like:
> (XEN) page_alloc.c:1460:d0 Over-allocation for domain 46: 131329 >
> 131328
> (XEN) memory.c:132:d0 Could not allocate order=0 extent: id=46
> memflags=0 (62 of 64)
>
> ?
>
> (I tryied to reproduce the issue by simply add many emulated e1000 in
> QEMU :) )
>
FWIW this probably comes from XENMEM_populate_physmap. Simply speaking
your domain is exceeding memory limit...
Wei.
> --
> Anthony PERARD
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-12-06 16:00 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 19:51 qemu-xen-dir + PCI passthrough = BOOM Konrad Rzeszutek Wilk
2013-12-05 12:16 ` Anthony PERARD
2013-12-06 14:49 ` Konrad Rzeszutek Wilk
2013-12-06 15:35 ` Anthony PERARD
2013-12-06 16:00 ` Wei Liu [this message]
2013-12-06 16:03 ` Wei Liu
2013-12-16 15:08 ` Konrad Rzeszutek Wilk
2013-12-18 14:48 ` Anthony PERARD
2013-12-18 14:57 ` Ian Campbell
2013-12-18 15:22 ` Konrad Rzeszutek Wilk
2013-12-18 16:13 ` Ian Campbell
2013-12-18 16:18 ` Konrad Rzeszutek Wilk
2013-12-22 11:25 ` Wu, Feng
2013-12-31 15:30 ` Konrad Rzeszutek Wilk
2014-01-06 9:54 ` Ian Campbell
2014-01-07 0:27 ` Wu, Feng
2014-01-08 19:44 ` Konrad Rzeszutek Wilk
2014-01-09 14:56 ` Anthony PERARD
2014-01-09 15:36 ` Pasi Kärkkäinen
2014-01-09 15:43 ` Pasi Kärkkäinen
2014-01-09 23:54 ` Sander Eikelenboom
2014-01-10 0:17 ` Sander Eikelenboom
2014-01-10 0:22 ` Sander Eikelenboom
2014-01-10 3:28 ` Konrad Rzeszutek Wilk
2014-01-10 15:19 ` Anthony PERARD
2014-01-10 16:05 ` Sander Eikelenboom
2014-01-10 16:25 ` Anthony PERARD
2014-01-10 16:38 ` Sander Eikelenboom
2014-01-10 16:35 ` Konrad Rzeszutek Wilk
2014-01-10 17:38 ` Sander Eikelenboom
2014-01-10 18:01 ` Konrad Rzeszutek Wilk
2014-01-26 0:05 ` Zhang, Yang Z
2014-01-27 12:12 ` Stefano Stabellini
2014-01-27 15:34 ` Zhang, Yang Z
2014-01-27 15:37 ` Stefano Stabellini
2014-01-31 15:23 ` Stefano Stabellini
2014-01-26 2:15 ` Zhang, Yang Z
2014-01-16 6:40 ` Zhang, Yang Z
2014-01-16 11:36 ` Konrad Rzeszutek Wilk
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=20131206160018.GC4419@zion.uk.xensource.com \
--to=wei.liu2@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=stefano.stabellini@citrix.com \
--cc=xen-devel@lists.xenproject.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).