Jason Andryuk 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 wire
On Tue, Dec 11, 2018 at 1:18 PM Chris Brannon wrote:
>
> Christopher Clark writes:
>
> > On Tue, Dec 4, 2018 at 10:11 AM Chris Brannon wrote:
> >>
> >> Hi,
> >> I set up a network driver domain for a dom0; it uses HVM
> >> virtualization. It worked very well when not using a device model
> >> s
Christopher Clark writes:
> On Tue, Dec 4, 2018 at 10:11 AM Chris Brannon wrote:
>>
>> Hi,
>> I set up a network driver domain for a dom0; it uses HVM
>> virtualization. It worked very well when not using a device model
>> stubdomain, but when I requested the use of a device model stubdomain in
On Tue, Dec 4, 2018 at 10:11 AM Chris Brannon wrote:
>
> Hi,
> I set up a network driver domain for a dom0; it uses HVM
> virtualization. It worked very well when not using a device model
> stubdomain, but when I requested the use of a device model stubdomain in
> my xl.cfg file, the domU refused
Hi,
I set up a network driver domain for a dom0; it uses HVM
virtualization. It worked very well when not using a device model
stubdomain, but when I requested the use of a device model stubdomain in
my xl.cfg file, the domU refused to boot. It gave the following error
message.
[76594.195404] xe