Subtletree

Working perfect for me, thank you!

@SimpleDino I feel bad I never came back with an update! If i remember correctly, @bastl was right and the "AER: Uncorrected (Non-Fatal) error received" was the source of the problem (Thanks @bastl!) . I think I did something like the advice here and silenced the error. Whatever I was reading at the time suggested it's not really an issue and silencing the error was all good. I'm not at home now so will check my settings when I get home.

Hi! When I shutdown my windows 10 vm (either from the unraid gui or from the vm) it ends up in a paused state, instead of being stopped. A restart also ends up in a paused state. If I try resume the vm I get: internal error: unable to execute QEMU command 'cont': Resetting the Virtual Machine is required So I force-stop and then start the vm and everything works fine. It's not really a big issue for me except: If I shutdown the vm it doesn't release the ram it was assigned. It is released after a force-stop. Windows did an update the other day and the vm ended up paused. When I rebooted it it said "failed update, rolling back" but something went wrong because windows explorer would constantly crash after that so i reset the vm. I have to force-stop and start instead of just clicking start. One potential clue is whenever I start the vm the logs show this error: qemu-system-x86_64: vfio_err_notifier_handler(0000:0a:00.1) Unrecoverable error detected. Please collect any data possible and then kill the guest The vm runs fine despite the above error. Any ideas? Diagnostics are attached and thanks for looking! tower-diagnostics-20200429-1337.zip