January 15, 20233 yr As title suggests, I have a Windows VM which is mostly responsible for running backups on my network which it emails to say its completed. I realised I hadn't see any of these emails in a while and found the VM was shutdown. Turned it back on and connected to VNC and I then see the Windows boot up screen, then VNC says unable to connect and the VM is showing as shutdown again. At the bottom of the VM log I can see the following: Quote qxl_send_events: spice-server bug: guest stopped, ignoring 2023-01-15 16:36:21.851+0000: shutting down, reason=crashed I've tried a different browser as I've seen that could be the cause but no luck. Anyone else seen this or might know how to recover the VM.
January 16, 20233 yr Did you install the guest agent using the "virtio-win-guest-tools.exe" in the main folder of your virtio drivers disk? For some unknown reason using this file will bork any windows 10 vm i tested so far and they will not boot anymore and i get the same error message as you posted above. Edited January 16, 20233 yr by Jumbo_Erdnuesse
January 17, 20233 yr Author 22 hours ago, Jumbo_Erdnuesse said: Did you install the guest agent using the "virtio-win-guest-tools.exe" in the main folder of your virtio drivers disk? For some unknown reason using this file will bork any windows 10 vm i tested so far and they will not boot anymore and i get the same error message as you posted above. I don't believe so, I built this VM quite some time as ago, so can't 100% remember, but I'm fairly sure all I did was provide the virtio driver ISO within the VM settings, I don't recall doing anything with virtio drivers directly from within Windows. The VM has been working for quite some time, several months until I noticed it recently stopped - not sure if UnRAID Upgrade may have broke it in some way.
March 9, 20233 yr Any update or solution on this? I was spinning up a Linux VM today, and suddenly got the "qxl_send_events: spice-server bug: guest stopped, ignoring" error. I thought it was some problem with the Linux VM, but now I can't connect to any of my existing VMs via noVNC! I'm using Chrome for my connection, I think, but there's no visible address bar, so I can't copy the path to try another browser. I also have no menus of any sort in the noVNC window, so I can't clear cookies or whatever as I've seen suggested elsewhere. Edited March 9, 20233 yr by Elmojo added details
December 28, 20232 yr This seems to be a common phenomenon, I had the same problem after installing win10, it stopped automatically, but the linux virtual machine still works.
October 2, 20241 yr Also wanting to know if this was ever figured out. Been happening to me the last couple weeks. Same exact situation except one of my Windows 10 VMs works no problem, and one has the lock up issue with the same logs.
January 28, 20251 yr Same issue here. Windows 10 vm setup a long time ago. Recently it started throwing this error every so often and pausing. Also it remains in paused state after running backup. It never did that before.
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.