I have a windows 10 VM that all of a sudden fails to start VNC (QXL) with error:

 

qxl_send_events: spice-server bug: guest stopped, ignoring

 

I am at a loss as to how to fix this, does anyone have any ideas?

 

 

On 12/30/2021 at 11:47 PM, dredge999 said:

I have a windows 10 VM that all of a sudden fails to start VNC (QXL) with error:

 

qxl_send_events: spice-server bug: guest stopped, ignoring

 

I am at a loss as to how to fix this, does anyone have any ideas?

 

 

Did you ever figure this out? I had 2 VM's that I used from time to time and both of them are giving me the same error. I am also not able to create a new VM (ubuntu server) as it gives the same error in the log file. 

anyone managed to sort this out?

I have the same for all my VMs

Same. Went to re-add a VM after months without and I cannot connect to it over VNC, and I have the feeling it's not progressing in the background.

 

Edit: running version 6.10.0-rc2

Edited February 10, 20224 yr by lurkio

Nothing?

I was having this error and disabling docker during setup worked.  Perhaps you have a docker messing with the network settings? Did you try a different browser?

I was forced to delete the VM in question completely while keeping the disk and then set it back up again using the existing disk.

There was something amiss with the XML file config (I hadn't edited it).

 

 

Damn, it was Firefox. Tried Chrome and VNC connects immediately.

Sorry for the necro - I was having the same issue and this was the 2nd link off google.

I had the opposite fix compared to lurkio, issue presented on Chrome, switching to Firefox did the trick.

It's neither nor, actually (this works for me, might work for you):

- Open the VNC windows, copy URL.

- Open private window on same browser

- Paste URL, Enter, log in, paste URL again, works.

-

 

No clue, either cookies or whatnot messing with things

Born8bit Hit the nail on the head here. Gotta be cookies messing up VNC

8 minutes ago, rednick69 said:

Born8bit Hit the nail on the head here. Gotta be cookies messing up VNC

Make sure the Community Applications is up to date then clear out all the cookies in your browser's history

On 6/18/2022 at 8:12 AM, Born8bit said:

It's neither nor, actually (this works for me, might work for you):

- Open the VNC windows, copy URL.

- Open private window on same browser

- Paste URL, Enter, log in, paste URL again, works.

-

 

No clue, either cookies or whatnot messing with things

 

 

I have the same Problem. But i dont like to delete all cookies. Instead, i use Chrome, if the noVNC Tab open, i go to the upper left Corner ("not safe" in Adress Bar) an  left Klick on it. There i can delete the specified cookies. Thas help me.

I am running into this error just trying to install the first VM.  I have tried multiple browsers and get the same error each time. Community Apps is up to date. How can I even connect to the VM if setup will not finish?  Ideas?

OK, this is weird. If I leave the RAM allocation at the minimum setting in the VM template (4GB for Windows 11), the machine boots and runs. The moment I increase the RAM at all, I get the error, even after the installation is complete.

37 minutes ago, rdagitz said:

OK, this is weird. If I leave the RAM allocation at the minimum setting in the VM template (4GB for Windows 11), the machine boots and runs. The moment I increase the RAM at all, I get the error, even after the installation is complete.

 

You sure you have enough ram available to support the increase over 4GB?

 

If so and still having issues, I would use the form view to edit the XML directly and increase the RAM and see if that works.

I have had plenty of issues creating VM using the GUI myself.

 

Rick

Edited January 9, 20233 yr by dredge999

OK, true confessions. It was operator error (and dredge999, you were right on target). I have been working on two different Unraid servers. I had the specs in mind of the other server when working on this one. It turns out that I need to add RAM to this server to get more power. Problem solved.

On 1/9/2023 at 6:44 PM, dredge999 said:

 

You sure you have enough ram available to support the increase over 4GB?

 

If so and still having issues, I would use the form view to edit the XML directly and increase the RAM and see if that works.

I have had plenty of issues creating VM using the GUI myself.

 

Rick

 

This was the fix for me. My server was using up more memory than it usually does.

 

Maybe we need better error reporting in this instance? Seems like a simple out-of-memory error that could be easily diagnosable by the user with better error reporting.

My solution was to set the minimal RAM to about 5G and to change the iso installation but from sata to usb

For me this 'bug' seems to be irelivent. The actual problem was apple's safari now doesn't work with NoVnC - whereas chrome loads up fine..

I had this same problem my excisting VM win 10 just works. but wanted to install win 11 in a VM and it just didnt want to start the VNC windows. So i tried windows 10 img same problem.

Im using firefox. So i clicked on the Schield and it was blocking 2 things so i disabled that projection for my unraid IP.  POEF it works for both windows 10 and my windows 11.

 

So the VM it self wasnt the problem it was Firefox that was blocking some VNC things.

I am encountering this issue without even using VNC on my Windows 11 gaming VM.

I encountered problems when I upgraded my win10 install to win11. very unreliablef, and black screen, it would also hang the picture of "restarting".

I changed from VNC to SPICE, seems to work so far at least, althought its really sluggish to get past the login prompt for win11, but after that everything seems fine.

On 2/15/2022 at 12:22 PM, RinkyDinkBear said:

I was having this error and disabling docker during setup worked.  Perhaps you have a docker messing with the network settings? Did you try a different browser?

Stopping all Docker containers made VNC start working for me! Thanks

I had ublock origin and disconnect plugins in chrome that probably are not playing well with chrome 127 and firefox 129. I allowed exceptions on both for the unraid site and my W11 vm worked again. could have something to do with browser compliance with the new manifest v3 or something. Thanks for this thread.