GHunter

QEMU 4.1 was downgraded to 4.0.1 in unRaid 6.8-RC5 so you may have to use them now.

Thanks for the help Andrew. I'll give this a try.

I'm having this same problem. I detect and load the drivers. Then scan and select the temps and fan speed readings. Hit apply and done. after leaving the page, nothing shows up in the dashboard. I go back to check the settings and everything is blank and i cannot detect or load drivers or sensors as they are all blank. filesvr-diagnostics-20190719-1020.zip

I'm having this same problem. Just happened 20 minutes ago or so. filesvr-diagnostics-20190719-1020.zip

Shutting down the array has always shutdown the VM's and most other services. Wish it didn't work this way but it does.

you should make a feature request for this. I think it would be a fairly simple fix as the logic already handles started VM's that are running normally. Basically resume all paused VM's first, then continue on with the stopping process as normal or something similar to this.

@queueizCan you be more specific? What did you try exaclty to get this working? Thanks!

I used a nVidia GTX 750 for mine. I use all nVidia GPUs in my builds as you can see in my signature.

I have it installed and working fine using Q35 and OVMF with a dedicated GPU. Didn't have any problems installing it as it was pretty straight forward. I haven't used it in ages though.

Me too! I've got quite a few VMs and could really take advantage of this feature when added.

No. To take advantage of this patch, you'll have to continue to edit the XML manually.

@jonp I was able to successfully switch a VM from Q35 to i440fx and activate my Windows 10 license. Note that I have all OEM Windows license's because they were OS upgrades from previous Windows versions. OEM licenses get 1 activation so transferring to a new PC or VM invalidates them. These Windows license's seem to be tied to the VM uuid and that's how I was able to do a successful conversion. However changing the uuid takes a bit of work as it isn't very easy to do.

Thanks. This is exactly what I needed to know! I feel better now and ditching Q35 should be a non-issue for me then. I'll convert all my Windows VM's to i440fx to future proof the VM's.

Not sure where you heard that, but it's not true. i440fx works perfectly fine when moving a VM from one set of electronics to another. Not sure where you got the impression otherwise. I think you're misunderstanding what I'm trying to say. I use Q35 Windows VM's currently. I need to migrate them to my new hardware. My concern is that the VM XML will be different if the XML is generated based on the hardware of the unRaid server. If the XML is the same regardless of hardware, then this would be a non-issue. If not, I'll be in trouble if Q35 is removed as I won't be able to properly generate the XML. If you change the motherboard of your computer, Windows wants you to call MS to reactivate the license (if you're not signed in with a Microsoft account). This applies the same with virtual motherboards like i440fx and Q35. If you've associated your registered copy of Windows with your Microsoft account, you'll just need to resign in once you change the gear and all is good. All my Windows 10 VM's were upgraded from Windows 7 or 8 and from what I understand, it is an OEM license and can only be activated on one machine. A server hardware upgrade or change to i440fx would kill my activated licenses with no recourse other than to buy new licenses. So keeping Q35 would be helpful in this case.

@jonp All of my Windows VM's use Q35. I am upgrading my server MB, CPU, and ram to use server grade hardware. In order for me to transfer my VM's, I will need to create a new VM using Q35 to use as a base template, and then point the xml to use the original virtual disk file. For migration purposes, keeping Q35 is about the only way to properly migrate a VM to ensure hardware compatibility with a new server. Also, migrating Windows based VHD's from other sources will become problematic if not impossible to get right. My other thought is that migrating Windows based VM's from q35 to i440fx could invalidate the Windows license, although I don't know if this is a real problem or not. I had no idea that i440fx is superior to q35. Knowing that, I would have used it over q35 when i originally setup my VM's.