From: Chris Brannon <cmb@prgmr.com>
To: Jason Andryuk <jandryuk@gmail.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
christopher.w.clark@gmail.com
Subject: Re: HVM driver domains do not appear to be usable with stubdomains
Date: Thu, 13 Dec 2018 07:35:46 -0800 [thread overview]
Message-ID: <874lbh7831.fsf@prgmr.com> (raw)
In-Reply-To: <CAKf6xpsTnu-6M6Si33f5Ugdam9oQC4ggWrm7qwaarwBw3eO3cg@mail.gmail.com> (Jason Andryuk's message of "Tue, 11 Dec 2018 15:17:28 -0500")
Jason Andryuk <jandryuk@gmail.com> writes:
>> So if I understand correctly, the problem is that PCI passthrough
>> doesn't work with stubdomains, unless qemu is patched?
>
> Hi, Chris.
>
> I pulled in the QEMU patch because I found that my Intel wired
> ethernet device didn't work without it. I believe my Intel wireless
> NIC did though. Maybe it was the opposite... I should have documented
> it more. However the device was passed-through - it just wasn't
> operational.
>
> What device is 0000:05:00.0? Is it listed by `xl pci-assignable-list`?
Hi Jason,
0000:05:00.0 was an Intel wired ethernet device. Yes it showed up
in xl pci-assignable-list. In fact, my driver domain worked fine without
a stubdomain; the card was passed through and I had it passing traffic
with no problem at all.
-- Chris
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2018-12-13 15:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 18:10 HVM driver domains do not appear to be usable with stubdomains Chris Brannon
2018-12-04 19:03 ` Christopher Clark
2018-12-11 18:16 ` Chris Brannon
2018-12-11 20:17 ` Jason Andryuk
2018-12-13 15:35 ` Chris Brannon [this message]
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=874lbh7831.fsf@prgmr.com \
--to=cmb@prgmr.com \
--cc=christopher.w.clark@gmail.com \
--cc=jandryuk@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.