SpaceInvaderOne

Hi, looking at your xml all the custom lines that are needed are no longer present. Unfortunately when you make a change to the vm using the Unraid vm manager gui it strips out any custom xml. So if you make a change using the vm manager after doing so you must add back the xml that has been removed At the top of the xml would be <os> <type arch='x86_64' machine='pc-q35-3.1'>hvm</type> <loader readonly='yes' type='pflash'>/mnt/user/domains/MacinaboxCatalina/ovmf/OVMF_CODE.fd</loader> <nvram>/mnt/user/domains/MacinaboxCatalina/ovmf/OVMF_VARS.fd</nvram> </os> This points to a custom ovmf file in the domains share. <interface type='bridge'> <mac address='52:74:00:17:57:0f'/> <source bridge='br0'/> <model type='vmxnet3'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> This part here sets the network card to be vmxnet3 (as the virtio which is standard will not work) Vmxnet3 is necessary for the install . However after installing it is better to then change that to <model type='e1000-82545em'/> Also at the bottom of the xml it is very important as the vm will not continue from clover without. <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x0f' slot='0x00' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-usb'/> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd,bus=usb-bus.0'/> <qemu:arg value='-device'/> <qemu:arg value='isa-applesmc,osk=the osk key has been removed from this'/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <qemu:arg value='Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check'/> </qemu:commandline> </domain> Also if you have set your cpu to have a large amount of cores then you will need to remove the topology line from the xml. for example <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='16' threads='1'/> </cpu> should be changed to <cpu mode='host-passthrough' check='none'> </cpu> Hope this helps

Hey @jpowell8672 I am still here -- Yeah sorry the last month has been really busy for me with work so I haven't spent a great deal of time on the forums recently. Yeah its a shame that Nvidia cards, since High Sierra, are no longer supported by Apple and especially too that support in High Sierra stops at Pascal - GTX 10 series.

opps yes i will fix that

Hi @MothyTim Please download the file in this post and run it as administrator on your windows 10 vm. MSI_util.exe Select any references to gpu or sound and click apply, this will enable msi interrupts which may help you. Also maybe try changing how you gpu is presented to the vm in this video here https://www.youtube.com/watch?v=QlTVANDndpM

Here is a guide about how to setup a Bitwarden server using the Bitwardenrs container. Also last part of video shows having setup the container how to use the chrome extension and importing passwords from chrome into Bitwarden. I hope you guys find it useful.

I have made a video guide about Bitwardenrs that maybe helpful for people new to setting this up.

hi @thierrybla please post your iommu groupings.

Make sure in your bios settings that iommu is set to yes and not auto. Auto will only partially enable iommu (was done like this due to a bug in some version of win 10 i beleive that stopped the win 10 booting) Setting to enabled in bios will prob solve all your issues

I use a Sapphire rx470 4gb pulse for my macos vms. I choose the Sapphire because I had heard they dont seem to have the reset problem that some other vendors cards do ( and I found that i dont have reset problems with this card). I choose the rx470 4gb cause it was cheaper than the 8gb version lol

Here a video guide for some GPU passthrough tips. If you have issues with error 43 this can be helpful.

Ah that's great glad you have it working now

Hi @cgi2099 thanks for the PM that you sent me. I thought that i would reply here in the thread so people with similar probs may be able to be helped by this?? So you have a Ryzen 2700x cpu in an ASUS X470 ROG CROSSHAIR VII motherboard. You say you are on the latest bios yes? So is that version 2901 released on the 2019/11/04 ? So passthrough isn't working I am guessing that you are getting no error messages and just a black screen when the vm starts with the GPU passed through. I have been in the exact same position as you are now using a 2700 and an Asrock board. It is basically because you are on the latest bios. Looking through the bios releases on the Asus page i think the best version for your board for the 2700x would be Version 1201 from early 2019. When the support for Ryzen gen 3 was added it seemed to break passthrough. Check my video here. https://www.youtube.com/watch?v=l-WHCCwgyDg I had to downgrade my bios to get it working again. Now this can be risky downgrading and I haven't tried on a Asus motherboard before. But if you want to try I have a video here https://www.youtube.com/watch?v=ZzqwjVDKAnU Now I have changed my cpu in the server since to 3900x and upgraded the bios onto the version that I had the problem with the 2700 on the Asrock x470 Tiachi. So it seems that the 3rd gen doesn't have the problem with the newer bios with passthrough, well it didn't have for me with the Asrock board. There is one thing that you can try which may help you. Do you have any old GPU lying around or one that you could borrow from a friend to test with. If so put that GPU in as the primary GPU. (Unraid console should display out of that) then passthrough the 1060 as a second GPU. Also you shouldn't need vbios passed through when it is the second GPU so try without first. (Although i personally prefer to always passthrough the vbios for any GPU ) If that still doesn't work swap the GPUs over. So the 1060 is primary and displays the Unraid console then passthrough 1060 as primary. (this time you must have the vbios passed through. And if vbios is downloaded from techpower up it also must be correctly edited - removing header) Hopefully this might work. A friend upgraded the bios on his motherboard to the latest and also had second gen Ryzen and wasn't affected by passthough breaking. He had 2 GPUs in his server and I only had one. So its worth a try. Now if you do decide to attempt to downgrade your bios on your motherboard please, please be careful. There is a risk of bricking the board should anything go wrong. Whilst this maybe ok if you still have warranty on the motherboard it will mean your server wont work at all

Just tried installing container again and don't get the same error. Please can you try removing the container and try and install again and see if you still have the same problem.

Yeah a mobile app would be nice. But it works well from the webui. I just add it to the homepage of my phone (android)

Ha that will serve me right for being lazy and copy and pasting from another support thread !!