OldScot

Over the weekend I tried to replace my usb key without success. The last time I tried to upgrade the upgrade failed and Unraid said there was perhaps? a problem with my usb stick. I prepared the new usb stick, copied my existing stick to the new stick and restarted. Unraid complained that there were too many keys in the configuration. (Includes Basic.key, Plus.key, and Trial.key.) I tried all combinations of keys, thinking it only wanted one but I never got a "Replace Key" button. The only option was always Buy Licence. I'm going to reinstall the old stick so I can report more details... (I started the upgrade because My Win10 vm stopped working with the graphics card and I thought it was time to get up to date... Still works on vnc and other graphics card.) Any assistance appreciated. Thanks!

Thanks ghost82, that was certainly a trip down the rabbit hole. When I built the server the motherboard was quite new and wasn't fully supported by Unraid until 6.9. This was my first time updating the bios. In the midst of all that my Windows VM disappeared, can't think how or why but I did need to create a new one and copy of the old definition to restore it. After updating the bios I had lost all my bios settings so I needed to enable virtualization, boot from USB, etc. Then I discovered all of the device mappings had changed, so no VM definitions made sense. It looked like the IOMMU groups now made more sense so I turned off IOMMU splitting and preceded to use the native groups. I was able to reassign the groups in the VMs, starting with the Mac VM, and get them going again. Finally I redefined the Win10 VM using all 4 groups + the DVD drive and it seems to work perfectly. Boots up, drive works, and shutdowns no problem. Thanks for the suggestion! (Never would have imagined all the fall out from the bios update.)

Attached. odin-diagnostics-20211027-1431.zip

Thanks ghost62! I tried your suggestion but the VM fails to come up. Files and Log are attached. I'm now convinced the log isn't always useful as it contains the same entries (as the first log attached) even when it works. I also realize I lost my DVD drive passthrough at some point. Will want to re-add it when this is stable. Thanks for any and all assistance. 20210026.devices.txt 20210026.log.txt 20210026.vm.txt

Hello SimonF, Thanks for your assistance. I had tried that but didn't have any luck. At the moment adding group 28 to the VFIO binding, but not adding 9:00.2 to the VM is working. The only trouble I have now is that I can't successfully shutdown, I have to start the shutdown from a DOS command prompt and then Force Stop. Tried all permutations of group 28 and 29 and adding 9:00.2 and 9:00.3 to the VM. The odd thing is that I have never used these settings before, and this VM's been running for nearly a year. Thanks Again!

I wanted to add a new USB device to my Win 10 VM so I restarted, and haven't been able to bring up the that VM since. This is the first time I haven't been able to sort out a problem with this VM. Other VMs, like my BigSur VM are still launching just fine. (Unraid 6.9.2) Hopefully too many edits etc have simply taken their toll on the XML definition. If I Edit the VM and save using Form View I get "VM creation error. internal error: unknown pci source type 'adapter'. (I haven't been able to save with Form View in ages, but I don't recall if that was always the error message.) It edits/saves in XML view and launches, but seems to hang on "qemu-system-x86_64: vfio: Cannot reset device 0000:09:00.1, depends on group 28 which is not owned." I tried adding using "Bind selection at VFIO at boot" but that didn't help so I removed it. I'm using "PCIe ACS Override setting enabled", and passing through graphic cards with audio to the WIN 10 VM and Mac VM. VM Log, VM XML, and PCI devices files are attached. Latest changes to the server were installing/using some Linux VMs (without passthrough). The other thing of note was a complaint that there had been a memory issue at some point. Any assistance much appreciated. Thanks! pci.devices.txt vm.log.txt vm.xml.txt