[Bug 250802] bhyve exited with status 134 when GPU PCI passthrough

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250802 --- Comment #52 from mr.xa...@gmail.com --- (In reply to Konstantin Belousov from comment #47) /usr/src # find . -name "*.orig" ./sys/amd64/vmm/io/ppt.c.orig ./sys/amd64/vmm/vmm.c.orig ./usr.sbin/bhyve/pci_emul.c.orig root@host:/usr/src #

[Bug 250802] bhyve exited with status 134 when GPU PCI passthrough

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250802 --- Comment #51 from Peter Grehan --- http://www.linux-kvm.org/images/e/ed/Kvm-forum-2013-VFIO-VGA.pdf -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtu

[Bug 250802] bhyve exited with status 134 when GPU PCI passthrough

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250802 --- Comment #50 from Peter Grehan --- Forcing a 1:1 mapping could be useful for a number of reasons, though it complicates the resource allocation code, and also won't allow guest re-assignment of BARs. I'll dig around for the presentation

[Bug 250802] bhyve exited with status 134 when GPU PCI passthrough

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250802 --- Comment #49 from Konstantin Belousov --- (In reply to Peter Grehan from comment #48) I remember that starting with SandyBridge, Intel GPUs have a window in their membar that translates accesses to mchbar. Quick look at the docs suggest

[Bug 250802] bhyve exited with status 134 when GPU PCI passthrough

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250802 --- Comment #48 from Peter Grehan --- I'm suspecting that this is due to lack of ROM support. There is a Linux VFIO talk somewhere that discusses 1:1 mappings, and also some other quirk issues such as adapter host config space being availa

[Bug 250802] bhyve exited with status 134 when GPU PCI passthrough

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250802 --- Comment #47 from Konstantin Belousov --- Created attachment 219501 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=219501&action=edit debugging #4 A hack to try my theory. Revert everything except D27095, and also apply 'deb

[Bug 250802] bhyve exited with status 134 when GPU PCI passthrough

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250802 --- Comment #46 from Konstantin Belousov --- (In reply to mr.xanto from comment #45) Ok, so my current understanding after looking at all debug data: 1. The real hardware BAR base address is 0xd00. 2. We remap the BAR at 0x8 in

[Bug 250802] bhyve exited with status 134 when GPU PCI passthrough

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250802 --- Comment #45 from mr.xa...@gmail.com --- (In reply to Konstantin Belousov from comment #44) pciconf -lvbc from FreeBSD guest: https://pastebin.com/EWrys8GL -- You are receiving this mail because: You are the assignee for the bug. __

[Bug 250802] bhyve exited with status 134 when GPU PCI passthrough

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250802 --- Comment #44 from Konstantin Belousov --- (In reply to mr.xanto from comment #43) Thank you, this is useful. Another request, please boot FreeBSD into this VM, and paste the output from pciconf -lvbc again (please use pastebin again).

[Bug 250802] bhyve exited with status 134 when GPU PCI passthrough

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250802 --- Comment #43 from mr.xa...@gmail.com --- (In reply to Konstantin Belousov from comment #42) bhyve output - https://pastebin.com/2pG1y31v bhyvectl output - https://pastebin.com/5wXAGjzK vmm.ko output - https://pastebin.com/wNJJ1f5r -- Yo

[Bug 250802] bhyve exited with status 134 when GPU PCI passthrough

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250802 --- Comment #42 from Konstantin Belousov --- (In reply to mr.xanto from comment #41) I cannot make sense of this output, it seems to not align with your previous data from gdb. Also bugzilla adds formatting. Or it could be the problem, bu

[Bug 250802] bhyve exited with status 134 when GPU PCI passthrough

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250802 --- Comment #41 from mr.xa...@gmail.com --- (In reply to Konstantin Belousov from comment #40) vm_map_pptdev_mmio bar 0 err 0 pci0:1:0:0 addr 0xc100 sz 0x100 base 0xfa00 vm_map_pptdev_mmio bar 1 err 0 pci0:1:0:0 addr 0x8

[Bug 250802] bhyve exited with status 134 when GPU PCI passthrough

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250802 --- Comment #40 from Konstantin Belousov --- Created attachment 219490 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=219490&action=edit debugging #3 Please apply the following patch to usr.sbin/bhyve, no need to revert kernel p

[Bug 250802] bhyve exited with status 134 when GPU PCI passthrough

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250802 --- Comment #39 from Konstantin Belousov --- (In reply to mr.xanto from comment #38) No need for gdb, and the fact that you do not see any other messages is probably telling. I will update later. -- You are receiving this mail because: Y

[Bug 250802] bhyve exited with status 134 when GPU PCI passthrough

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250802 --- Comment #38 from mr.xa...@gmail.com --- (In reply to Konstantin Belousov from comment #37) May be I do something wrong, but I'm don't see any new messages from vmm.ko exept "ppt_is_mmio 0xde6d5000 0". I should running bhyve under gdb or

[Bug 250802] bhyve exited with status 134 when GPU PCI passthrough

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250802 --- Comment #37 from Konstantin Belousov --- Created attachment 219488 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=219488&action=edit debugging #2 Please apply the attached debugging patch, rebuild kernel, and report what mes

Re: [arm64][bhyve] Hypervisor implementation proposal

Hi Andrei, The UPB team made a revision for the bhyve on arm/arm64 on phabricator[1]. Any feedback is greatly appreciated. [1] https://reviews.freebsd.org/D26976 Thanks for putting up the review: that is a sizeable amount of work. I'd suggest removing

[Bug 250802] bhyve exited with status 134 when GPU PCI passthrough

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250802 --- Comment #36 from mr.xa...@gmail.com --- (In reply to Konstantin Belousov from comment #35) I've removed D27138, set debug options for kernel (https://pastebin.com/5YLGAG91), aplied patch to vmm.c (https://pastebin.com/CSgmJ49g). gdb tra