Date: Tue, 27 Mar 2018 15:55:32 +0200 From: Wouter Snels <nospam@ofloo.net> To: Peter Grehan <grehan@freebsd.org> Cc: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net>, freebsd-virtualization@freebsd.org Subject: Re: bhyve pci passthrough usb controller Message-ID: <f5665c19-8fe0-db50-191c-b8af8e3a65d1@ofloo.net> In-Reply-To: <48cef2a2-f8de-1784-9094-daeb2dd7d55a@freebsd.org> References: <201803240230.w2O2U21F033917@pdx.rh.CN85.dnsmgr.net> <bfda0fa1-48be-4bc5-9172-8de89e4196fc@ofloo.net> <48cef2a2-f8de-1784-9094-daeb2dd7d55a@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
It seems that this is not limited to only windows7. I tried passing through to a generic test install of freebsd 11. And this crashes as well. Regards, .. Op 25-03-18 om 03:01 schreef Peter Grehan: > >> 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?f5665c19-8fe0-db50-191c-b8af8e3a65d1>