Date: Sat, 24 Mar 2018 18:01:19 -0700 From: Peter Grehan <grehan@freebsd.org> To: Wouter Snels <nospam@ofloo.net> Cc: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net>, freebsd-virtualization@freebsd.org Subject: Re: bhyve pci passthrough usb controller Message-ID: <48cef2a2-f8de-1784-9094-daeb2dd7d55a@freebsd.org> In-Reply-To: <bfda0fa1-48be-4bc5-9172-8de89e4196fc@ofloo.net> References: <201803240230.w2O2U21F033917@pdx.rh.CN85.dnsmgr.net> <bfda0fa1-48be-4bc5-9172-8de89e4196fc@ofloo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> I surely will try this out, but what about device 4/0/0 showing the > same issue. Both tests where performed separately showing the exact > same result, of course I'd be happy if either one of them worked. I think what is happening here is that Windows is enabling legacy interrupts on the device, and that happens to be on the same shared IRQ line that the ATA controller is on, resulting in spurious interrupts. The dmesg for the system may be able to confirm this, since it should list the legacy IRQs that have been assigned. bhyve PCI passthru relies not only on the device supporting MSI/MSI-x interrupts, but the guest using those. later, Peter.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48cef2a2-f8de-1784-9094-daeb2dd7d55a>