how to usb3.0 and gpu passthrough hackintosh big sur???

ynnek · Jun 17, 2023

first time doing a proxmox hackintosh with zero knowledge

i had enabled iommu and the rest just by following https://www.youtube.com/watch?v=DP8fMNUo4KM. after doing that, i was unable to start my VM if i attach my GPU

TASK ERROR: start failed: command '/usr/bin/kvm -id 100 -name '11.BigSur,debug-threads=on' -no-shutdown -chardev 'socket,id=qmp,path=/var/run/qemu-server/100.qmp,server=on,wait=off' -mon 'chardev=qmp,mode=control' -chardev 'socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5' -mon 'chardev=qmp-event,mode=control' -pidfile /var/run/qemu-server/100.pid -daemonize -smbios 'type=1,uuid=a4ca3031-0d1f-484c-a3a7-84903e53318c' -drive 'if=pflash,unit=0,format=raw,readonly=on,file=/usr/share/pve-edk2-firmware//OVMF_CODE_4M.secboot.fd' -drive 'if=pflash,unit=1,id=drive-efidisk0,format=raw,file=/dev/pve/vm-100-disk-0,size=540672' -smp '8,sockets=1,cores=8,maxcpus=8' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vga none -nographic -cpu 'Penryn,enforce,kvm=off,+kvm_pv_eoi,+kvm_pv_unhalt,vendor=GenuineIntel' -m 16384 -object 'iothread,id=iothread-virtio0' -readconfig /usr/share/qemu-server/pve-q35-4.0.cfg -device 'vmgenid,guid=5b0318ef-0888-4461-9ab9-6930845f71d5' -device 'usb-tablet,id=tablet,bus=ehci.0,port=1' -device 'vfio-pci,host=0000:03:00.0,id=hostpci0.0,bus=ich9-pcie-port-1,addr=0x0.0,multifunction=on' -device 'vfio-pci,host=0000:03:00.1,id=hostpci0.1,bus=ich9-pcie-port-1,addr=0x0.1' -device 'usb-host,hostbus=1,hostport=7,id=usb0' -device 'usb-host,hostbus=1,hostport=8,id=usb1' -device 'usb-host,hostbus=1,hostport=9.4,id=usb2' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3,free-page-reporting=on' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:2cde7826cd89' -drive 'file=/dev/pve/vm-100-disk-1,if=none,id=drive-virtio0,cache=unsafe,format=raw,aio=io_uring,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,iothread=iothread-virtio0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'vmxnet3,mac=06:1C:07:1C:98:C7,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=101' -machine 'type=q35+pve0' -device 'isa-applesmc,osk=ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc' -smbios 'type=2' -device 'usb-kbd,bus=ehci.0,port=2' -cpu 'host,kvm=on,vendor=GenuineIntel,+kvm_pv_unhalt,+kvm_pv_eoi,+hypervisor,+invtsc'' failed: got timeout

after reading from https://pve.proxmox.com/wiki/PCI_Passthrough#Verify_IOMMU_is_enabled, i need a dedicated IOMMU group for all PCI devices i want to assign to a VM. my GPU is at group 1 (03:00.0), i have added pcie_acs_override=downstream to /etc/default/grub and my GPU is at group 1

root@pve:~# find /sys/kernel/iommu_groups/ -type l
/sys/kernel/iommu_groups/7/devices/0000:00:1d.0
/sys/kernel/iommu_groups/5/devices/0000:00:1b.0
/sys/kernel/iommu_groups/3/devices/0000:00:16.0
/sys/kernel/iommu_groups/1/devices/0000:03:00.0
/sys/kernel/iommu_groups/1/devices/0000:02:00.0
/sys/kernel/iommu_groups/1/devices/0000:00:01.0
/sys/kernel/iommu_groups/1/devices/0000:01:00.0
/sys/kernel/iommu_groups/1/devices/0000:03:00.1
/sys/kernel/iommu_groups/8/devices/0000:00:1f.0
/sys/kernel/iommu_groups/8/devices/0000:00:1f.5
/sys/kernel/iommu_groups/8/devices/0000:00:1f.3
/sys/kernel/iommu_groups/8/devices/0000:00:1f.4
/sys/kernel/iommu_groups/6/devices/0000:00:1c.0
/sys/kernel/iommu_groups/4/devices/0000:00:17.0
/sys/kernel/iommu_groups/2/devices/0000:00:14.2
/sys/kernel/iommu_groups/2/devices/0000:00:14.0
/sys/kernel/iommu_groups/10/devices/0000:06:00.0
/sys/kernel/iommu_groups/0/devices/0000:00:00.0
/sys/kernel/iommu_groups/9/devices/0000:05:00.0

how do i separate my GPU from group 1 and move to a new group? will this work for my hackintosh VM?

and why is my hackintosh VM not working if i add usb 3.0?

somebody please help me... @_@
note: hackintosh is working if i direct install on this pc and i am using gigabyte rx 5500 xt

leesteken · Jun 17, 2023

I might be able to help you get PCIe passthrough working on a VM that boots from an recent Ubuntu Live installer ISO (no need for virtual disk). For AMD Navi 14 GPUs you need install vendor-reset and activate it. Using the newer 6.2 kernel probably makes things easier. Please don't use pcie_acs_override and show your IOMMU groups with this command:

cat /proc/cmdline; for d in /sys/kernel/iommu_groups/*/devices/*; do n=${d#*/iommu_groups/*}; n=${n%%/*}; printf 'IOMMU group %s ' "$n"; lspci -nns "${d##*/}"; done

.

I cannot help you with macOS, sorry. I hope the provided links can get you started on getting passthrough working (with Ubuntu). Once that has helped figuring out which work-around you need for passthrough, then you can use that for your macOS VM.

LnxBil · Jun 17, 2023

First: If your PCIe does not work at first glance and out-of-the-box, you will have a hard time getting it to work. I learnt this the hard way.

ynnek said:
how do i separate my GPU from group 1 and move to a new group?

Move your GPU to another PCIe slot.

ynnek said:
why is my hackintosh VM not working if i add usb 3.0?

Change the USB3 controller. I bought 3 and the most expensive one is the one that finally worked and also out-of-the-box.

ynnek · Jun 17, 2023

leesteken said:
I might be able to help you get PCIe passthrough working on a VM that boots from an recent Ubuntu Live installer ISO (no need for virtual disk). For AMD Navi 14 GPUs you need install vendor-reset and activate it. Using the newer 6.2 kernel probably makes things easier. Please don't use pcie_acs_override and show your IOMMU groups with this command: cat /proc/cmdline; for d in /sys/kernel/iommu_groups/*/devices/*; do n=${d#*/iommu_groups/*}; n=${n%%/*}; printf 'IOMMU group %s ' "$n"; lspci -nns "${d##*/}"; done.

I cannot help you with macOS, sorry. I hope the provided links can get you started on getting passthrough working (with Ubuntu). Once that has helped figuring out which work-around you need for passthrough, then you can use that for your macOS VM.

i deleted pcie_acs_override from /etc/default/grub

root@pve:~# cat /proc/cmdline; for d in /sys/kernel/iommu_groups/*/devices/*; do n=${d#*/iommu_groups/*}; n=${n%%/*}; printf 'IOMMU group %s ' "$n"; lspci -nns "${d##*/}"; done
BOOT_IMAGE=/boot/vmlinuz-6.2.11-2-pve root=/dev/mapper/pve-root ro quiet intel_iommu=on
IOMMU group 0 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:9b43] (rev 05)
IOMMU group 10 06:00.0 Non-Volatile memory controller [0108]: ADATA Technology Co., Ltd. Device [1cc1:628a] (rev 03)
IOMMU group 1 00:01.0 PCI bridge [0604]: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) [8086:1901] (rev 05)
IOMMU group 1 01:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Upstream Port of PCI Express Switch [1002:1478] (rev c5)
IOMMU group 1 02:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch [1002:1479]
IOMMU group 1 03:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5)
IOMMU group 1 03:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 HDMI Audio [1002:ab38]
IOMMU group 2 00:14.0 USB controller [0c03]: Intel Corporation Device [8086:43ed] (rev 11)
IOMMU group 2 00:14.2 RAM memory [0500]: Intel Corporation Device [8086:43ef] (rev 11)
IOMMU group 3 00:16.0 Communication controller [0780]: Intel Corporation Device [8086:43e0] (rev 11)
IOMMU group 4 00:17.0 SATA controller [0106]: Intel Corporation Device [8086:43d2] (rev 11)
IOMMU group 5 00:1b.0 PCI bridge [0604]: Intel Corporation Device [8086:43c4] (rev 11)
IOMMU group 6 00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:43bc] (rev 11)
IOMMU group 7 00:1d.0 PCI bridge [0604]: Intel Corporation Device [8086:43b0] (rev 11)
IOMMU group 8 00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:4387] (rev 11)
IOMMU group 8 00:1f.3 Audio device [0403]: Intel Corporation Device [8086:f0c8] (rev 11)
IOMMU group 8 00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:43a3] (rev 11)
IOMMU group 8 00:1f.5 Serial bus controller [0c80]: Intel Corporation Device [8086:43a4] (rev 11)
IOMMU group 9 05:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 16)

i have read vendor reset and i am willing to give it a try. i did download source code .zip from the release page, then i do not know what to do next. do i need to upload to my proxmox? how? mind to tell me step by step?

ynnek · Jun 17, 2023

LnxBil said:
First: If your PCIe does not work at first glance and out-of-the-box, you will have a hard time getting it to work. I learnt this the hard way.

Move your GPU to another PCIe slot.

Change the USB3 controller. I bought 3 and the most expensive one is the one that finally worked and also out-of-the-box.

unfortunately i can't move my GPU to another PCIE slot, my motherboard only has 1 PCIE slot... T_T

what do you mean with usb3 controller?
just to clarify, i did add usb where i plugged flashdisk to motherboard usb port. if i checked usb 3.0, VM will not work. uncheck usb 3.0, VM will work...

leesteken · Jun 17, 2023

ynnek said:
i have read vendor reset and i am willing to give it a try. i did download source code .zip from the release page, then i do not know what to do next. do i need to upload to my proxmox? how? mind to tell me step by step?

Here is an (old) guide on installing it. And you need to activate it every reboot of the Proxmox host before starting the VM. There are several threads about this on this forum.

ynnek said:
BOOT_IMAGE=/boot/vmlinuz-6.2.11-2-pve root=/dev/mapper/pve-root ro quiet intel_iommu=on
IOMMU group 0 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:9b43] (rev 05)
IOMMU group 10 06:00.0 Non-Volatile memory controller [0108]: ADATA Technology Co., Ltd. Device [1cc1:628a] (rev 03)
IOMMU group 1 00:01.0 PCI bridge [0604]: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) [8086:1901] (rev 05)
IOMMU group 1 01:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Upstream Port of PCI Express Switch [1002:1478] (rev c5)
IOMMU group 1 02:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch [1002:1479]
IOMMU group 1 03:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5)
IOMMU group 1 03:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 HDMI Audio [1002:ab38]
IOMMU group 2 00:14.0 USB controller [0c03]: Intel Corporation Device [8086:43ed] (rev 11)
IOMMU group 2 00:14.2 RAM memory [0500]: Intel Corporation Device [8086:43ef] (rev 11)
IOMMU group 3 00:16.0 Communication controller [0780]: Intel Corporation Device [8086:43e0] (rev 11)
IOMMU group 4 00:17.0 SATA controller [0106]: Intel Corporation Device [8086:43d2] (rev 11)
IOMMU group 5 00:1b.0 PCI bridge [0604]: Intel Corporation Device [8086:43c4] (rev 11)
IOMMU group 6 00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:43bc] (rev 11)
IOMMU group 7 00:1d.0 PCI bridge [0604]: Intel Corporation Device [8086:43b0] (rev 11)
IOMMU group 8 00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:4387] (rev 11)
IOMMU group 8 00:1f.3 Audio device [0403]: Intel Corporation Device [8086:f0c8] (rev 11)
IOMMU group 8 00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:43a3] (rev 11)
IOMMU group 8 00:1f.5 Serial bus controller [0c80]: Intel Corporation Device [8086:43a4] (rev 11)
IOMMU group 9 05:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 16)

The USB controller is not alone in the IOMMU group and you cannot share devices of the same group between VMs and/or the Proxmox host.

ynnek said:
unfortunately i can't move my GPU to another PCIE slot, my motherboard only has 1 PCIE slot... T_T

You can try making Proxmox ignore the actual IOMMU groups by using pcie_acs_override=downstream,multifunction (since the USB controller is a function of PCI(e) device 00:14). Note that the VM can then access all of the memory of the Proxmox host and other VMs and containers because there is no security isolation between that VM and the host (and everything on it). Check your groups after adding it to the kernel parameters, it might not help.
Or you could search for other (safer) ways to pass the USB devices, like USB passthrough.

LnxBil · Jun 17, 2023

ynnek said:
unfortunately i can't move my GPU to another PCIE slot, my motherboard only has 1 PCIE slot... T_T

Ah, damn ... yeah, buy another motherboard. What about just running hackintosh instead of virtualizing?

ynnek said:
what do you mean with usb3 controller?

Without any PCIe available, this does not make any sense. I bought 3 USB3 addon cards in order to buy ONE that actually works in MacOS without any gliches or crashes.

ynnek · Jun 18, 2023

leesteken said:
Here is an (old) guide on installing it. And you need to activate it every reboot of the Proxmox host before starting the VM. There are several threads about this on this forum.

i downloaded kernel 6.2, when i tried to install, proxmox saying that i am still using pve-header 5. i googled and input update-initramfs -u

not sure what happened, my server's monitor keeps showing like this and stuck like that forever. i am still able access proxmox from another computer

if i try to install again, it showing this

root@pve:~/vendor-reset# dkms install .
Error! DKMS tree already contains: vendor-reset-0.1.1
You cannot add the same module/version combo more than once.

any suggestion what to do next? @_@

leesteken said:
The USB controller is not alone in the IOMMU group and you cannot share devices of the same group between VMs and/or the Proxmox host.

You can try making Proxmox ignore the actual IOMMU groups by using pcie_acs_override=downstream,multifunction (since the USB controller is a function of PCI(e) device 00:14). Note that the VM can then access all of the memory of the Proxmox host and other VMs and containers because there is no security isolation between that VM and the host (and everything on it). Check your groups after adding it to the kernel parameters, it might not help.
Or you could search for other (safer) ways to pass the USB devices, like USB passthrough.

i think i'm going to skip reading it for now, i am hungry. LOL...

ynnek · Jun 18, 2023

LnxBil said:
Ah, damn ... yeah, buy another motherboard. What about just running hackintosh instead of virtualizing?

Without any PCIe available, this does not make any sense. I bought 3 USB3 addon cards in order to buy ONE that actually works in MacOS without any gliches or crashes.

as i mentioned in the first post, hackintosh running well without virtualization...

for usb, i think what @leesteken said is correct, it is not in a dedicated group

leesteken · Jun 18, 2023

ynnek said:
i downloaded kernel 6.2, when i tried to install, proxmox saying that i am still using pve-header 5. i googled and input update-initramfs -u

No need to look for random guides, it's in the Proxmox manual. Yes, you need to install the correct pve-headers version that matches the kernel version. Several threads about this on this forum.

ynnek said:
not sure what happened, my server's monitor keeps showing like this and stuck like that forever. i am still able access proxmox from another computer
View attachment 51776

I don't know, maybe it's because you are early binding the GPU? Or made changes to the kernel parameters? What is the output of cat /proc/cmdline and lspci -nnks 03:00?

ynnek said:
if i try to install again, it showing this

root@pve:~/vendor-reset# dkms install .
Error! DKMS tree already contains: vendor-reset-0.1.1
You cannot add the same module/version combo more than once.

That's normal. It even tells you that it's already installed. Did you activate it (as show in one of the previous links) for your GPU before starting the VM?

ynnek said:
any suggestion what to do next? @_@

I'm not sure what problems you are having. None of the things above seems to be very problematic. Is the VM with Ubuntu live installer working with passthrough?

ynnek said:
i think i'm going to skip reading it for now, i am hungry. LOL...

Yeah, me too...

ynnek · Jun 18, 2023

leesteken said:
I don't know, maybe it's because you are early binding the GPU? Or made changes to the kernel parameters? What is the output of cat /proc/cmdline and lspci -nnks 03:00?

root@pve:~# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-6.2.11-2-pve root=/dev/mapper/pve-root ro quiet intel_iommu=on
root@pve:~# lspci -nnks 03:00
03:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5)
Subsystem: Gigabyte Technology Co., Ltd Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1458:2319]
Kernel driver in use: vfio-pci
Kernel modules: amdgpu
03:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 HDMI Audio [1002:ab38]
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 HDMI Audio [1002:ab38]
Kernel driver in use: vfio-pci
Kernel modules: snd_hda_intel

leesteken said:
That's normal. It even tells you that it's already installed. Did you activate it (as show in one of the previous links) for your GPU before starting the VM?

I'm not sure what problems you are having. None of the things above seems to be very problematic. Is the VM with Ubuntu live installer working with passthrough?

right now, i am totally confused... i don't even know how activate it... @_@

after rebooting from the (old) guide, i add hardware and still not working...

i don't install ubuntu VM, only hackintosh... this is might be a good idea, will try later on....

leesteken · Jun 18, 2023

ynnek said:
right now, i am totally confused... i don't even know how activate it... @_@

leesteken said:
And you need to activate it every reboot of the Proxmox host before starting the VM. There are several threads about this on this forum.

It's in the orange link I provided. In your case you need to run echo device_specific >'/sys/bus/pci/devices/0000:00:03:00.0/reset_method' before starting the VM. Use whatever method you like for doing this after every reboot of the Proxmox host (cron, rc.local, systemd-service) or before starting the VM (hookscript). You should see messages about resetting from vendor-reset in journalctl when starting the VM, otherwise it is not setup right.

ynnek · Jun 19, 2023

leesteken said:
It's in the orange link I provided. In your case you need to run echo device_specific >'/sys/bus/pci/devices/0000:00:03:00.0/reset_method' before starting the VM. Use whatever method you like for doing this after every reboot of the Proxmox host (cron, rc.local, systemd-service) or before starting the VM (hookscript). You should see messages about resetting from vendor-reset in journalctl when starting the VM, otherwise it is not setup right.

root@pve:~# echo device_specific >'/sys/bus/pci/devices/0000:00:03:00.0/reset_method'
-bash: /sys/bus/pci/devices/0000:00:03:00.0/reset_method: No such file or directory

i installed ubuntu VM, i passthroughed GPU and same thing happen, can not start into ubuntu...

leesteken · Jun 19, 2023

ynnek said:
root@pve:~# echo device_specific >'/sys/bus/pci/devices/0000:00:03:00.0/reset_method'
-bash: /sys/bus/pci/devices/0000:00:03:00.0/reset_method: No such file or directory

My mistake, it should be 0000:03:00.0 not 0000:00:03:00.0.

ynnek · Jun 19, 2023

leesteken said:
My mistake, it should be 0000:03:00.0 not 0000:00:03:00.0.

root@pve:~# echo device_specific >'/sys/bus/pci/devices/0000:03:00.0/reset_method'
-bash: echo: write error: Invalid argument

leesteken · Jun 19, 2023

ynnek said:
root@pve:~# echo device_specific >'/sys/bus/pci/devices/0000:03:00.0/reset_method'
-bash: echo: write error: Invalid argument

That error means that vendor-reset is not loaded (or does not support your GPU, which is unlikely). What is the output of lsmod | grep vendor?

EDIT: The next steps of troubleshooting are: What is the output of modprobe vendor-reset? Did you add vendor_reset to /etc/modules? Did you run update-initramfs -u. Did you sucessfully install vendor-reset for you current kernel version? Did you install the pve-headers for your current kernel version, so you could build and install vendor-reset?

ynnek · Jun 19, 2023

leesteken said:
That error means that vendor-reset is not loaded (or does not support your GPU, which is unlikely). What is the output of lsmod | grep vendor?

EDIT: The next steps of troubleshooting are: What is the output of modprobe vendor-reset? Did you add vendor_reset to /etc/modules? Did you run update-initramfs -u. Did you sucessfully install vendor-reset for you current kernel version? Did you install the pve-headers for your current kernel version, so you could build and install vendor-reset?

lsmod | grep vendor --> nothing shows up

root@pve:~# modprobe vendor-reset
modprobe: FATAL: Module vendor-reset not found in directory /lib/modules/6.2.11-2-pve

leesteken said:
Did you add vendor_reset to /etc/modules? Did you run update-initramfs -u.

i did add vendor-reset to /etc/modules and i did run update-initramfs -u, those 2 are commands are in nicksherlock website...

if i nano /etc/modules, it shows
vfio
vfio_iommu_type1
vfio_pci
vfio_virqfd
vendor-reset

leesteken said:
Did you sucessfully install vendor-reset for you current kernel version? Did you install the pve-headers for your current kernel version, so you could build and install vendor-reset?

i think the problem is vendor-reset is not installed correctly. as i've said earlier, when i tried to run dkms install . for the first time it says incorrect pve-header, run second times, it shows
Error! DKMS tree already contains: vendor-reset-0.1.1
You cannot add the same module/version combo more than once.

is there a way to delete vendor-reset and reinstall?

root@pve:~# pveversion
pve-manager/7.4-13/46c37d9c (running kernel: 6.2.11-2-pve)
root@pve:~# apt install pve-headers
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
pve-headers is already the newest version (7.4-1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

leesteken · Jun 19, 2023

ynnek said:
lsmod | grep vendor --> nothing shows up

Then it's not loaded.

ynnek said:
root@pve:~# modprobe vendor-reset
modprobe: FATAL: Module vendor-reset not found in directory /lib/modules/6.2.11-2-pve

Then it is not build and installed for kernel version 6.2.11-2-pve.

ynnek said:
i did add vendor-reset to /etc/modules and i did run update-initramfs -u, those 2 are commands are in nicksherlock website...

if i nano /etc/modules, it shows
vfio
vfio_iommu_type1
vfio_pci
vfio_virqfd
vendor-reset

vfio_virqfd is no longer a separate module on kernel version 6.2. The rest looks good.

ynnek said:
i think the problem is vendor-reset is not installed correctly. as i've said earlier, when i tried to run dkms install . for the first time it says incorrect pve-header, run second times, it shows
Error! DKMS tree already contains: vendor-reset-0.1.1
You cannot add the same module/version combo more than once.

Please apt install pve-headers-6.2, as they are not automatically installed on Proxmox 7.x which uses kernel 5.15 by default. I did not notice you telling me that it said incorrect headers before, sorry.

ynnek said:
is there a way to delete vendor-reset and reinstall?

root@pve:~# pveversion
pve-manager/7.4-13/46c37d9c (running kernel: 6.2.11-2-pve)
root@pve:~# apt install pve-headers
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
pve-headers is already the newest version (7.4-1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Try dkms remove vendor_reset/0.1.1 to remove it (maybe add --all if necessary). Maybe also remove the directory where you put the sources from the downloaded vendor-reset and try unzipping, building and installing again.

ynnek · Jun 19, 2023

leesteken said:
Then it's not loaded.

Then it is not build and installed for kernel version 6.2.11-2-pve.

vfio_virqfd is no longer a separate module on kernel version 6.2. The rest looks good.

Please apt install pve-headers-6.2, as they are not automatically installed on Proxmox 7.x which uses kernel 5.15 by default. I did not notice you telling me that it said incorrect headers before, sorry.

Try dkms remove vendor_reset/0.1.1 to remove it (maybe add --all if necessary). Maybe also remove the directory where you put the sources from the downloaded vendor-reset and try unzipping, building and installing again.

i did apt install pve-headers-6.2, remove vendor-reset and reinstall it again. this time, dkms install . shows few lines about installation, it was success and lsmod | grep vendor shows vendor_reset 122880 0

i did add GPU to hardware and tried to run hackintosh VM, no luck...

what do we miss? @_@

leesteken · Jun 19, 2023

ynnek said:
i did apt install pve-headers-6.2, remove vendor-reset and reinstall it again. this time, dkms install . shows few lines about installation, it was success and lsmod | grep vendor shows vendor_reset 122880 0

i did add GPU to hardware and tried to run hackintosh VM, no luck...

what do we miss? @_@

Did you active vendor-reset? Does it work now with the Ubuntu live installer? Do you see reset messages in journalctl?

how to usb3.0 and gpu passthrough hackintosh big sur???

New Member

Distinguished Member

Distinguished Member

New Member

New Member

Distinguished Member

Distinguished Member

New Member

New Member

Distinguished Member

New Member

Distinguished Member

New Member

Distinguished Member

New Member

Distinguished Member

New Member

Distinguished Member

New Member

Distinguished Member