derpuma

Adding veto files = /._*/.DS_Store/._.DS_Store/ hide files = /._*/.DS_Store/._.DS_Store/ delete veto files = yes to my smb-extra.conf does not give me the desired result. I still see the files I want to hide on my array and unassigned devices. Even after array restart and server reboot. Any ideas why? My smb-extra.conf looks like that: #unassigned_devices_start #Unassigned devices share includes include = /tmp/unassigned.devices/smb-settings.conf #unassigned_devices_end veto files = /._*/.DS_Store/._.DS_Store/ hide files = /._*/.DS_Store/._.DS_Store/ delete veto files = yes [rootshare] path = /mnt/user comment = browseable = yes valid users = admin write list = admin vfs objects =

Yes I did, sorry for the missundertanding. Of course I meant mitigations="off"...

I used the mitigations plugin in 6.9.2 without any problems regarding to my macOS VMs. After upgrading to 6.11/6.11.1 I had boot problems into my macOS VMs (several random opencore kernel panics, syslog shows amdgpu errors) and I am not able to boot into the macOS VMs. Windows works fine. I have a verdict, causing the problem. I suspect the boot problems could be related to the mitigations plugin, as it looks like the problem only accures at the time mitigations are enabled. I can reproduce the error, every time I rebuild my flash to 6.9.2 from backup with mitigations enabled, everthing works fine. Updating 6.9.2 to 6.11 or 6.11.1, the mitigations are still enabled and I am not able to boot into the macOS VMs. Any advice from your side, what I could check to see if there is defenitly any relation? I like the mitigations enabled, as my macOS is round about 20-25% faster with them turned on.

My Catalina and Monterey Vms are running fine under 6.9.2. After the update to 6.11 the do not boot up. Monterey hangs in a endless bootloop. Any ideas? As far as I can see IOMMU Groups are exactly the same in 6.9.2 and 6.11.

I disabled bonding and did a few boot ups. But it still takes some time till network is up and running. Maybe a little bit faster like with bonding activated. Maybe this is just the way it is whithout a dedicated NIC for my VM and I have to live with that. What bothered me, was the fact, that network sometimes is there immediatly and sometimes not.

I have a problem, that my VMs (either MacOS, Windows or Linux have a problem with network being present right after boot into OS, in probably 3 to 4 times out of 10. Usually I have full network access (internet and local network to NAS and other computers) right after booting into OS. But sometimes network is not present and it takes up to 1.5 and 2 minutes before it is available. Any Idea what could cause this behaviour? It is the onboard controller at my Gigabyte Aeorus Pro which is also used by unraid: 06:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) I have also a 10GBe Ethernetcard with two ports. This network never shows that behaviour. tower-diagnostics-20221002-1039.zip

I did the update from 6.9.2 to 6.11 and now Unraid freezes and does not react when I shutdown a MacOS VM. GUI does not load, also I am not able to ping the Unraid server. I have a AMD 5700XT and AMD RX480 (known for the vendor reset bug) in my system, but never had this problems under 6.9.2. Even Force stop of the VM freezes Unraid and I am not able to use it. Only way is to power off and reeboot the system. Any Ideas?

Yes of course, will send you the files tomorrow. We can switch to PM until the problem is solved if you'd like to!

No need for sorries! 1) The dongle is a regular usb dongle. I connect it via USB - USB-C adapter to the USB-C port of my board, as this was the only way to get it working. 2) yes, the headset can run wireless and via cable. and yes, connects fine both via dongle and usb cable to the usb c port. I am not sure if the usb-c is part of the matisse controller. Copy of my IOMMU groups attatched. Best would be if it could work on any other USB port (hub or board manually or with usb plugin manager). If the dongle is connected via USB-C (working) it shows up as this device. If the dongle is connected on the hub which is passthrough (not working) it looks like that (it sorts in one cat deeper in the usb tree). The device is listed as: CORSAIR VIRTUOSO SE Wireless Gaming Headset: Produkt-ID: 0x0a46 Hersteller-ID: 0x1b1c (CORSAIR MEMORY INC.) Version: 0.00 Seriennummer: 142b6156000700da Geschwindigkeit: Bis zu 12 MBit/s Hersteller: Corsair Standort-ID: 0x06311000 / 16 Verfügbare Stromstärke (mA): 500 Erforderliche Stromstärke (mA): 500 Zusätzlicher Betriebsstrom (mA): 0 IOMMU.txt

1) The headset (dongle and connection via usb cable) works fine out of the box on a real mac without any additional software. 2) The headset (dongle and usb cable) does not work on any usb port which is passed through exclusivly on that port. 3) The headset (dongle and usb cable) does not work on any a onboard controller port which is passed through vfio IOMMU group. In my case this is a AMD Matisse USB 3.0 Host Controller | USB controller (09:00.1). On this controller I use a usb hub. The headset also does not work on any of the hubs ports. 4) The headset (dongle and cable) does work out of the box on the USB-C port of the mainboard. I did not configure this usb-c port extra via vfio iommu. My guess is, it belongs to the AMD Matisse USB 3.0 Host Controller. 5 ) The headset does not show up at all, while I trying to attatch it via usb plugin manager. It shows as connectet via plugin interface, but the device does not pop up under MacOs sound settings. Not works means: If connected on both sides, meaning mic and sound are activated in sound settings, the headset does not work. Sound stutters, also recording. When only one part is active in sound settings, the single selected function works just fine. So if sound is on and mic not selected, sound works. Also vice versa, if headset sound is off, speakers on and headset mic is selected for recording, it records just fine. It seems that there is a problem to seperate the two funtions sound and recording.

Very good point! This specific USB Dongle from Corsair indeed has a kext which installs into /L/E via Corsair iCUE Software. There is a <key>idProductArray</key> in info.plist and <key>idVendor</key> <integer>6940</integer> for Corsair itself. I packed the kext down below. But on my Macbook Pro, where no Corsair iCUE Software is installed, the kext is missing and the Dongle works out of the box with MacOS. You think I should give it a try and put the kext into opencore to inject from there rather then /L/E and see if this changes anything? I guess this specific kext has nothing to do with the function of the headset and dongle. CorsairAudio.kext.zip

Did you find a solution for this problem? I also use the Corsair Dongle for a Headset which does not work with the USB Manager Plugin at MacOS. Bit it looks like it is not a Dongle connection problem, cause the same behaviour shows up while connectet via USB cable. I am able to attatch it to the VM, but the device does not show up under MacOS. The dongle only works on Mac at the USB-C Port of my mainboard which seems to be internaly connected with this USB Host controller: It works exlusivly while conneted via this single USB-C Port (sound and mic without any flaws). Directly connected to the HUB I use at this USB Host controller Headset sound is working, but mic is quirky and records with gaps and hickups. When I go to the mic prefs in system>audiopreferences every Video I play starts to stutter. Headset sound alone works fine at all, while mic is off. Under Windows VM Dongle and cable are working without any problems while Headset is attatched via USB Manager Plugin. My Board is a 570Z Aeorus Pro. Any Ideas how to adress the problem under MacOS?

I did not set the 'No' to 'Public' as I thought 'No' ment no security and public access which is oviously not the case. Switching to public did it! Thanks a lot for guiding me through this!

I have a problem with the UD plugin, not beeing able to mount any of my Unassigned shared Disks from /mnt/disks aka /mnt/remotes under windows and MacOS. Under Unraid, via browser I can open them up. I am not sure how to get access to /mnt/shares as I think I switched everything needed on under settings. Via Krusader, I see everything (screenshots att.) Any help?

I have a problem with the plugin. I updated the user scripts plugin and afterwards it disappeared from my unraid menu and if I try to open it via the plugins > installed plugins tab and click on it, I get a black screen. Reinstall did not fix the problem. I am on Unraid Version: 6.10.0-rc1 Any ideas?

I also can confirm, that the latest vendor-reset for the audio fixed the problem with my Powercolor 5700 XT. It never reseted properly after an OS shutdown, or VM stop via UNRAID. NOW EVERYTHING WORKS LIKE A CHARM as it is supposed to be. Finally I will be a happy 5700 XT user. So kudos to @ajmadsen @gnif from github and also to @ICH777 for making it easy to bring all stuff to the UNRAID stick with use of the kernel helper docker!

Okay, no problem that you are a beginner. Everybody started from zero. So a short round up. Virtualisation and especially Hardware passthrough needs equivalent hardware which you have. Your mainboard groups your hardware, in your case your gpu in several groups, called IOMMU groups. If you GPU is grouped with other hardware passthrough will not be possible. To get your gpu separated, you can use the Virtual Manager in Unraid and setup to split your hardware. The settings there are done at the pcie override tab which gives you several options you should try and see what setting will give you the best result in case of separating. Separation is the basic point to achieve gpu passthrough. If this is not setup correctly, it will not work. If done right and you setup you gpu as a multifunctional device, all should work just fine. I am not 100% sure about your gpu model, as you said you have an rx570 lite. I know for sure a regular rx570 works nativly under macOS, not so sure about the lite, but I guess it should. I revommend you to read the Unraid Virtualisation Wiki step by step and follow the guides to prepare your Unraid setting. The try to finalize your macOS VM. https://wiki.unraid.net/UnRAID_6/VM_Management My advise, dont give up too early.It looks more complicated then it is and when you are fine with the settings you wonder how logical and easy a setup is, compared to a linux kvm installation via console.

Hardware wise you are good to go. With 6.8.3 and your X570 board you should have a closer look at you IOMMU groups and if the GPU and gpu sound is separated in its own group. You may play with VM Manager and pcie override settings, as you need to set up you gpu as a multifunctional device. Please make a new thread as suggested above and show at least your XML you are using to boot into mac OS. You said you followed spaceinvaderone installation video, so i guess your mac OS is running at least in VNC mode?

Audio via remote desktop? Thought your goal was the passthrough... Try to get it right first without using any remote access software. If this works and go the next step and setup the remote desktop software. To be honest, I never tried to get audio through remote desktop...

Very, very good point!

1) Question, you do have a monitor which has build in speakers and is able to play audio? Just as a reminder, this is only HDMI Sound you get there... Onboards sound is another different passthrougt. Simply add another soundcard (f.ex. the onboard sound) under the sound part of the GPU. 2) What do you mean with adding Vbios into docker settings? Do you mean the path you choose on your share in your XML? Do not put it into a smb share, as it could take a while until the share is mounted. Simply put the rom file into /mnt/isos to get it onload. If it crahes, are you sure you are using a proper Vbios? Did you selfextract it via GPU-Z from a running baremetal windows or downloaded it? Remember downloaded bios from techpowerup need a cleanup with a hexeditor. If your VM crashes, sometimes it is normal, that you need to reactivate the VM Manager after next boot up. Do not worry about that. Make sure that you have a backup while you still try to get al things working.

GPU alone sounds perfect and you can try your passthrough. The best view of your groups you have with the Unraid VFIO plugin or menu Tools > System Devices: Simply try a bus. If the bus is not free, you will get a warning when you trying to save your plain text XML under the VM tab. My second card is a RX480 and it looks like that: <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0d' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/isos/XFX_RX480.rom'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0d' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x1'/> </hostdev>

Actually selling Hardware, esp. GPUs is as easy as I never saw it before. And you get really good money also for older GPUs. If you'd like to get help, we need additional information from you. What hardware, how have you configured your VM Manager, how is your XML setup, do you useVFIO Plugin, which is your Unraid Version... Generally you should not have a problem, to get a RX570 over the finish line, but you might run in the famous reset-bug and will need the vendor-reset patch to get rid of it. But first things first, try to setup the GPU full functional first.

The bus is the same, cause it is set to multifunctional. So no worries there, just have an eye that the bus is free for GPU and HDMI-AUDIO and not booked by another PCIe device! My VManager ist set to "both". I would recommend you try "multifunctional" first and see how your IOMMU groups look like. If all is good separated, then you are fine. I you need a better split up, try "both"!

To solve the apple services problem read this: And no, mostly you can not take a 1:1 copy of the EFI Folder from your prior baremetal installation. For exact answers, you should give more details about your hardware, which macOS, etc.