xavierda

Hi all, Glad the original post was helpful. I had to rebuild my XML file after a crash - for some unknown reason. Main driver was to be able to play Fortnite again. Here's the main bit of my XML for the VM. I don't explicitly hide the VM, it seems the smbios mode = host does the trick to get pass EasyCheet, and I get better performance. <os> <smbios mode='host'/> </os> <features> <acpi/> <apic/> <hyperv mode='custom'> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vpindex state='on'/> <synic state='on'/> <stimer state='on'/> <vendor_id state='on' value='none'/> </hyperv> <vmport state='off'/> </features> <cpu mode='host-passthrough' check='none' migratable='off'> <topology sockets='1' dies='1' clusters='1' cores='14' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> <feature policy='disable' name='hypervisor'/> </cpu> <clock offset='localtime'> <timer name='hpet' present='no'/> <timer name='hypervclock' present='yes'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> No BSOD. Xav,

Hi there, Just had to sort out an issue with my Windows 11 VM and thought I would post here in case anyone else encounters it. My Windows 11 VM (daily use) was fine yesterday. Went to use it this morning and the VM was off. Strange. Restarted and BSOD Unsupported Processor. It has been very stable up until this point. I had enabled the option Get the latest updates as soon as they're available for Windows Update. Seems like whatever was installed while I was away was the culprit. Luckily, I could reboot into Windows 11 natively (dual boot), which started fine. The last update installed was: 2025-05 Cumulative Update Preview for Windows 11 Version 24H2 for x64-based Systems (KB5058499) Examining the packages, included the following: dism /online /get-packages /format:table | Select-String -Pattern "29/05" ... Microsoft-Windows-HyperV-OptionalFeature-HypervisorPlatform-Disabled-Package~31bf3856ad364e35~amd64~~10.0.26100.4202 | Installed | Feature Pack | 29/05/2025 1:58 PM Searching that indicated this disables Hyper-V/VM features. Sure, enough going to the Add/Remove Windows Features revealed both Virtual Machine Platform and Windows Hypervisor Platform options had been turned off. Turned them back on, rebooted back into Unraid and restarted the VM - back to normal! Seems strange for an update to disable a feature in use? Maybe the cause was something else, yet the above steps got me back on track. Anyone else encounter this, or similar with another Windows 11 update? Hoping it doesn't occur again! In the meantime, turned off the Get the latest option - at least for a while. Xav.

I am curious, do you get good performance in Fortnite with the hypervisor feature policy disabled? For me, the game lagged terribly and was unplayable. Removed that (keeping the SMBIOS setting) and despite Windows now reporting again it is running in a VM, Fortnite worked beautifully!

Hi there, Few more tweaks today. Added back in the: <feature policy='disable' name='hypervisor'/> option. I am a bit baffled reviewing this thread actually - I swear I had this option enabled? Anyway, also added the following: </kvm> <vmport state='off'/> (just including the 'kvm' entry so you know where to pop this setting). According to the doco (https://libvirt.org/formatdomain.html#hypervisor-features) this disables emulation of a VMWare IO port. In Task Manager, Performance Tab, CPU (after shutting down and restarting the VM) you'll now see: Virtualisation: Enabled. Whereas previously, this was Virtual Machine: Yes. Before adding those settings into the XML config, Fornight was fine, but Marvel Rivals was not. Now, Rivals starts fine. Pretty impressed really, this is a ThreadRipper system I built specifically for Unraid back in 2018. Passing through a GTX3070. Again, not an avid gamer but feels good to give this older system a bit of a stretch! Happy to try other games and report back, compare configs etc. So far, stable and works...

EDIT: Oops, this was the same info mentioned earlier in the thread: BUT! I rebooted into native windows, THEN made it virtual again - will see how long that lasts for!! ----- Hi there, So, I returned to this after giving up for a while. Now, when originally configuring my VM, I passed through an NVME drive. I figured I don't need my Unraid shares while gaming, so rebooted - boot menu'd to Windows and BOOM! Back in action. I then followed this guide: Mainly for the tip about copying the UUID so as not to confuse Windows. I'm not running it activated anyway, but allows for switching between the two. Then I looked into the doco behind the XML config underpinning the KVM: https://libvirt.org/formatdomain.html I noticed the "smbios tag". By default, if not specified, the emulator populates it with things like "QEMU" (If you bring up System Info in Windows, you may see this in one of the BIOS strings). I added this instead under the <os> tag: <smbios mode='host'/> Which according to the doco instead copies those values from the host. So for example, sysinfo within my VM now looks like: System Manufacturer Micro-Star International Co., Ltd. System Model MS-7B09 System Type x64-based PC System SKU To be filled by O.E.M. Processor AMD Ryzen Threadripper 2950X 16-Core Processor, 3500 Mhz, 14 Core(s), 28 Logical Processor(s) BIOS Version/Date American Megatrends Inc. A.89, 11/08/2022 SMBIOS Version 2.8 Embedded Controller Version 255.255 BIOS Mode UEFI BaseBoard Manufacturer Micro-Star International Co., Ltd. BaseBoard Product X399 SLI PLUS (MS-7B09) BaseBoard Version 2.0 Now, my previous boot into this VM, Fortnite exited due to detecting a VM. There may have been a few other things contributing to "resetting" the detection: I updated the BIOS (as per above) as in my case it supported Win11 (which I didn't need before when running just as a VM, as it was using the emulated one) I rebooted into native windows, THEN ran the game - all good! I booted back into Unraid, copying the UUID into the XML config. Added the smbios = host tag under the <os> section. For good measure, also threw the <kvm> <hidden state='on'/> back in there. Played Fornite in the VM again! (Yay!!!) Might be a different outcome with your WRC game, but - if you can - try the above? Happing gaming - virtually!

I did find one work around... As I had recently changed some of my local network settings, I realised I had forgotten to specify an additional DNS server (secondary) in Network Settings. I just had the default gateway listed. Added Google's (8.8.8.8) and then I could access the WebUI again.

Hi everyone, This was running great when I installed it for the first time. Now after rebooting, reinstalling, this no longer works! Logs say: "Interface eth0 not found. Falling back to default." Seems to be a bug already captured here: https://github.com/gnmyt/myspeed/issues/806 But, can't seem to get this going again under Unraid. Any ideas? Cheers, Xav.

Yes! I know Loaded up the game to play with my son and was booted from the match about 45 seconds in - seems like the detection has been updated and the settings no longer work. Haven't been an avid gamer for years, and not kept up with it - why would running in a VM be an issue? Is this the way certain hacks/cheats are made? I'm just playing on a different setup and want to use the same hardware for different things! The performance was great, the gametime was fun. Guess I'm searching to beat BattleEye, or find another combination of setting that hides the VM status. Regards, Xav.

Hey there, Confirming this also worked for me recently. Windowss 11 VM, GTX3070 Passthrough and can now play Fortnite successfully. Performance of the VM in general seems unaffected, so will incorporate this into my templates going forward. Thank you for the tips here! Regards, Xav.

Hi there, I am experiencing intermittent lockups with a Win10 VM too. More so when the system is idle, but also when using it occasionally. How do you disable TPM? Is this an XML config option? Or were you trying to pass it through? I am passing through an NVME drive, an NVIDIA GTX3070 and the mainboard USB hub so I can use keyboard, mouse etc. All seems to work....right up until it locks up.

Hi there, Experimenting with this a bit. I have an older Canon MG5760 printer, which is connected via Wifi. There are Linux drivers available from Canon's website - the manual for Linux seems to support Wifi printing. Do I just need to mount and install within the Docker container, then do the CUPS setup stuff? Cheers, Xav.

Hi there, Adding to the list of posts about 6.10.3 and GPU Passthrough, especially for older NVIDIA hardware. I recently got a hold of an older GTX660 card. This is the second card (the first being a basic GT1030 in slot 1) in the system. Further setup: M/B: Micro-Star International Co., Ltd. X399 SLI PLUS (MS-7B09) Version 2.0 BIOS: American Megatrends Inc. Version A.70. Dated: 11/14/2018 CPU: AMD Ryzen Threadripper 2950X 16-Core @ 3500 MHz HVM: Enabled IOMMU: Enabled Cache: 1536 KiB, 8 MB, 32 MB Memory: 32 GiB DDR4 (max. installable capacity 512 GiB) Network: eth0: 1000 Mbps, full duplex, mtu 1500 Kernel: Linux 5.15.46-Unraid x86_64 I have poured over these forums for weeks - SpaceInavder1 videos, and so on. I finally thought I managed to get it working - no error 43, and looking great via HDMI output to an LG 34" widescreen. However, every few minutes or more it seems to lock up, becoming unresponsive to keyboard or mouse input; Unraid remains unaffected. The Windows event log seems to have entries: "The description for Event ID 14 from source nvlddmkm cannot be found." Tried the main solutions available on the web to little avail. More info: BIOS was dumped from the card using SpaceInvader's UserScrip method. Latest NVIDIA drivers installed (for this card 473.47). XML File is: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows 10 - V9</name> <uuid>9bffc959-4cde-8bb3-3420-cb5fcb611cb3</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>17301504</memory> <currentMemory unit='KiB'>2097152</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='16'/> <vcpupin vcpu='2' cpuset='1'/> <vcpupin vcpu='3' cpuset='17'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-6.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/9bffc959-4cde-8bb3-3420-cb5fcb611cb3_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv mode='custom'> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='1234567890ab'/> </hyperv> <kvm> <hidden state='on'/> </kvm> <ioapic driver='kvm'/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='2' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Windows 10 - V9/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Win10_21H2_EnglishInternational_x64.iso'/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.221-1.iso'/> <target dev='hdb' bus='sata'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x14'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0x15'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0x16'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x6'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:7d:2c:74'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <audio id='1' type='none'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0a' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/domains/vbios/GTX660.rom'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0a' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x1'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0c' slot='0x00' function='0x3'/> </source> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x413c'/> <product id='0x301c'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <memballoon model='none'/> </devices> </domain> I feel I am close to getting this working! But the VM is not usable Anyone else encountered this freezing/lockup issue? Note, I get great output and the driver appears to be working in Device Manager - just need to wait a few minutes and it will freeze. Thanks in advance! Xav.

No, I ended up switching to cheesemarathon's app and managing remotely the BOINC instance using BOINC Manager from a Windows host. Works for me. Xav.

I updated to the latest version (and uninstalled from CA/Apps, then installed again), but I am still getting a black screen. BOINC seems to start ok from the logs, but the X server seems to not be working correctly. Log snippet shows: X.Org X Server 1.20.13 X Protocol Version 11, Revision 0 Build Operating System: linux Ubuntu Current Operating System: Linux 2bc7a65a4633 5.10.28-Unraid #1 SMP Wed Apr 7 08:23:18 PDT 2021 x86_64 Kernel command line: BOOT_IMAGE=/bzimage isolcpus=0-3 initrd=/bzroot Build Date: 14 December 2021 02:14:13PM xorg-server 2:1.20.13-1ubuntu1~20.04.2 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.38.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (++) Log file: ".xorgxrdp.10.log", Time: Wed Mar 2 13:36:53 2022 (++) Using config file: "/etc/X11/xrdp/xorg.conf" (==) Using system config directory "/usr/share/X11/xorg.conf.d" xorgxrdpSetup: xrdpdevSetup: rdpmousePlug: rdpkeybPlug: rdpIdentify: rdpDriverFunc: op 10 : rdpProbe: found DRMDevice xorg.conf value [/dev/dri/renderD128] rdpProbe: found DRI3 xorg.conf value [1] rdpPreInit: rdpPreInit: /dev/dri/renderD128 open failed rdpScreenInit: virtualX 800 virtualY 600 rgbBits 8 depth 24 rdpScreenInit: pfbMemory bytes 1920000 rdpScreenInit: pfbMemory 0x1528d4def010 rdpSimdInit: assigning yuv functions rdpSimdInit: cpuid ax 1 cx 0 return ax 0x00800f82 bx 0x1e200800 cx 0x7ed8320b dx 0x178bfbff rdpSimdInit: sse2 amd64 yuv functions assigned rdpClientConInit: disconnect idle session after [0] sec rdpClientConInit: kill disconnected [0] timeout [0] sec rdpXvInit: depth 24 rdpScreenInit: out [20220302-13:36:20] [INFO ] starting xrdp with pid 485 [20220302-13:36:20] [INFO ] address [0.0.0.0] port [3389] mode 1 [20220302-13:36:20] [INFO ] listening to port 3389 on 0.0.0.0 [20220302-13:36:20] [INFO ] xrdp_listen_pp done [20220302-13:36:52] [INFO ] Socket 11: AF_INET6 connection received from ::ffff:127.0.0.1 port 51584 [20220302-13:36:52] [DEBUG] Closed socket 10 (AF_INET6 :: port 3389) [20220302-13:36:52] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem [20220302-13:36:52] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem [20220302-13:36:52] [DEBUG] TLSv1.3 enabled [20220302-13:36:52] [DEBUG] TLSv1.2 enabled [20220302-13:36:52] [DEBUG] Security layer: requested 3, selected 1 ssl_tls_accept: TLS connection accepted colorDepth 0xca01 (0xca00 4bpp 0xca01 8bpp) [20220302-13:36:52] [INFO ] connected client computer name: Guacamole RDP postBeta2ColorDepth 0xca01 (0xca00 4bpp 0xca01 8bpp 0xca02 15bpp 0xca03 16bpp 0xca04 24bpp) highColorDepth 0x0010 (0x0004 4bpp 0x0008 8bpp 0x000f 15bpp 0x0010 16 bpp 0x0018 24bpp) supportedColorDepths 0x0007 (0x0001 24bpp 0x0002 16bpp 0x0004 15bpp 0x0008 32bpp) earlyCapabilityFlags 0x0421 (0x0002 want32) got client client connection type 0x00000006 xrdp_sec_process_mcs_data_CS_SECURITY: client and server support none crypt, using none crypt [20220302-13:36:52] [INFO ] adding channel item name cliprdr chan_id 1004 flags 0xc0a00000 [20220302-13:36:52] [INFO ] adding channel item name rdpdr chan_id 1005 flags 0xc0800000 [20220302-13:36:52] [INFO ] adding channel item name rdpsnd chan_id 1006 flags 0xc0000000 error unknown xrdp_sec_process_mcs_data tag 0xc006 size 8 error unknown xrdp_sec_process_mcs_data tag 0xc00a size 8 Feels like I need to delete or reset something - any ideas? Cheers, Xav.

Hi ich777, I saw that link in an earlier post - when I run it, I only see a single server return, ie. the OpenDNS ones. The log window from DoH-Client (with verbose=true set in the config file) shows requests going to Google, DNS.SB and OpenDNS, which I set. So, if those requests are being tunnelled over HTTPS/TLS, then only seeing one server in the DNSLeakTest is to be expected? Cheers, Xav.