johnsanc Posted October 10, 2022 Share Posted October 10, 2022 Posted in General the other day figured this is a better place to ask along with more details... so apologies for the double post as it doesn't look like I can move a topic. I upgraded to UnRAID 6.11.1 and everything went smoothly. However my Windows 10 VM just freezes without any apparent errors as far as I can tell. There is nothing suspicious that I can see in the Windows Event Viewer logs and I don't see anything different in my VM log compared to when it was working fine. I used to have issues after I upgraded to 6.11.0 where the network connection to the VM would drop, but I resolved this by upgrading the virtio drivers to the ones from the latest stable ISO. This issue with 6.11.1 is different though, and I can tell the VM is completely frozen. I usually use RDP for accessing the VM, but if I plug in a monitor the graphics card I have passed through to the VM I can see the time on the windows lock screen is frozen. The only major change I did was enabled the virtiofs feature. I've attached my diagnostics in case anyone can take a peek to see what the issue might be. I am not really sure where to look. My VM froze around 11:29 PM ET on 10/9/22 and again at 10:53 AM ET on 10/10/22. Basically it looks like the VM will not stay live for more than 2-3 hours without completely freezing and requiring me to force stop. I did notice that if I try to do a regular stop once its frozen the libvirt log shows the following: 2022-10-10 14:57:38.384+0000: 520: error : qemuAgentSend:759 : Guest agent is not responding: Guest agent not available for now 2022-10-10 14:58:14.162+0000: 519: error : qemuAgentSend:759 : Guest agent is not responding: Guest agent not available for now 2022-10-10 14:58:56.600+0000: 521: error : qemuAgentSend:759 : Guest agent is not responding: Guest agent not available for now 2022-10-10 14:59:27.392+0000: 521: warning : qemuDomainObjTaintMsg:6464 : Domain id=2 name='Windows 10' uuid=8dd0454f-e9f4-6e94-3bc2-93cbd146abcb is tainted: custom-ga-command 2022-10-10 14:59:32.393+0000: 521: error : qemuAgentSend:759 : Guest agent is not responding: Guest agent not available for now Any ideas? tower-diagnostics-20221010-1112.zip 1 Quote Link to comment
issabankz Posted February 18, 2023 Share Posted February 18, 2023 how did you solve this? Quote Link to comment
francrouge Posted May 28, 2023 Share Posted May 28, 2023 Hi were you able to resolve it i got the same issueEnvoyé de mon Pixel 2 XL en utilisant Tapatalk Quote Link to comment
johnsanc Posted May 28, 2023 Author Share Posted May 28, 2023 (edited) Nope looks like an unresolved issue with qemu and memoryBacking. All we can do is wait I guess. I should add the issues above were also when I was trying to use VirtioFS. Edited May 28, 2023 by johnsanc Quote Link to comment
jstevenco Posted July 28, 2023 Share Posted July 28, 2023 Hey @johnsancjust wanted to give you confirmation that I've been observing regular lockups of Win10 w/CPUs pegged for some time. Based upon the comments in this and other threads, I removed the MemoryBacking and Virtiofs sections from my XML (I wasn't using Virtiofs). VM has been rock solid for over 36 hours. Will keep thread informed. Quote Link to comment
jstevenco Posted August 3, 2023 Share Posted August 3, 2023 Update: VM has now been running with no issues for over a week. Quote Link to comment
mackid1993 Posted August 3, 2023 Share Posted August 3, 2023 FYI this is supposed to be fixed in the new version of QEMU which we are supposed to get in 6.13. It's a memory leak, if you watch taskmgr the non-paged pool will slowly balloon until Windows runs out of memory. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.