[Bug 222996] FreeBSD 11.1 on Hyper-V with PCI Express Pass Through

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222996 Mark Linimon changed: What|Removed |Added Assignee|freebsd-standards@FreeBSD.o

[Bug 222996] FreeBSD 11.1 on Hyper-V with PCI Express Pass Through

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222996 Sepherosa Ziehau changed: What|Removed |Added CC|

[Bug 222916] [bhyve] Debian guest kernel panics with message "CPU#0 stuck for Xs!"

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222916 --- Comment #6 from Peter Grehan --- >Or does the interaction between bhyve and the host scheduler somehow >result in the virtual cpus being set aside Yes, though: > for tens of seconds? The error message from

[Bug 222996] FreeBSD 11.1 on Hyper-V with PCI Express Pass Through

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222996 --- Comment #2 from Dmitry --- No, i mean not SR-IOV. I am already have extra configuration through powershell for PCI Passthrough, and it's works for other OS in Generation 2 Hyper-V VM, except FreeBSD. I have

[Bug 222916] [bhyve] Debian guest kernel panics with message "CPU#0 stuck for Xs!"

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222916 --- Comment #5 from kari...@gmail.com --- Thanks for that tip. I reduced the ARC size with sysctl and confirmed it to be 20GB with zfs-info. Thinking back to the 4 guest / 4 host cpus. Lets say the collection of guests consume 4 cpus and