From: mail ignored <0.bugs.only.0@gmail.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: xen-devel@lists.xensource.com, weidong.han@intel.com
Subject: Re: Re: follow up to a pciback "pv pci-passthrough co-assigned problem"
Date: Sat, 23 Jan 2010 08:40:28 -0800 [thread overview]
Message-ID: <c67eed301001230840l2987a8adr81bf3dc53b2f8d58@mail.gmail.com> (raw)
In-Reply-To: <20100123123042.GG2861@reaktio.net>
hi
On Sat, Jan 23, 2010 at 4:30 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> This has been discussed many times here on xen-devel and on xen-users..
You're right -- there sure has. That's been my problem -- there's not
a consistent solution to be found. :-/
> with xen-unstable (upcoming Xen 4.0) take a look at /etc/xen/xend-config.sxp:
> (pci-passthrough-strict-check yes)
> set that to no, restart xend, and it'll work.
Yep, I'm aware of that. But 4.0.x fails miserably on my box, atm :-/
I'm hoping that there's a fix for 'stable' 3.4.x.
> With Xen 3.3, or 3.4, you can apply a "disable FLR" patch, which also makes it work:
> http://xen.markmail.org/download.xqy?id=7dbm675e4x4dawec&number=1
I applied the patch at that link. At VM launch, I still get the
Error: pci: 0000:04:07.0 must be co-assigned to the same guest with
0000:04:06.0
message ...
Thanks.
next prev parent reply other threads:[~2010-01-23 16:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-23 1:32 follow up to a pciback "pv pci-passthrough co-assigned problem" mail ignored
2010-01-23 4:09 ` mail ignored
2010-01-23 12:30 ` Pasi Kärkkäinen
2010-01-23 16:40 ` mail ignored [this message]
2010-01-23 16:48 ` Pasi Kärkkäinen
2010-01-23 17:36 ` mail ignored
2010-01-23 17:43 ` Pasi Kärkkäinen
2010-01-23 17:45 ` mail ignored
2010-01-23 17:54 ` mail ignored
2010-01-23 17:57 ` Pasi Kärkkäinen
2010-01-23 17:58 ` mail ignored
2010-01-23 18:15 ` mail ignored
2010-01-25 1:44 ` Weidong Han
2010-01-25 16:17 ` 0bo0
2010-01-26 1:42 ` Weidong Han
2010-01-26 7:02 ` Pasi Kärkkäinen
2010-01-23 18:19 ` Keir Fraser
2010-01-26 6:50 ` 0bo0
2010-01-26 7:34 ` Keir Fraser
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=c67eed301001230840l2987a8adr81bf3dc53b2f8d58@mail.gmail.com \
--to=0.bugs.only.0@gmail.com \
--cc=pasik@iki.fi \
--cc=weidong.han@intel.com \
--cc=xen-devel@lists.xensource.com \
/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).