[SOLVED] VMs will not start, not even basic console or bios

[Anghywir]

Copied this over from the general support page, cause I posted there before I saw this one.

 

I decided I was going to try a little project that will require a Windows 10 installation for a little while, so I was going to revive an old VM I used a while ago. I enabled VMs on my server and my VM was still in the list, so I tried to start it.

 

VM shows as started, but no activity change on the server CPU, and when I try to connect to the VNC console for the VM, I gt a failed to connect message instantly.

 

Thought it might be the VM, so I created a new blank VM from the linux template, didn't hand it any ISOs, didn't attach any new devices or change any settings. Same behaviour, instant connection failure on both VNC and Spice console.

 

I stopped all my dockers and turned off autostart, rebooted the server, and the fresh VM still doesn't start. VM logs only show blue and white text (text and system) and I can't see anything there that might be causing issues. It's like it just stops when it should be bringing up the BIOS for the VM.

 

The shutdown or Restart commands from the VM menu in unraid do essentially nothing, not even an entry in the logs, but the force stop option does show in the logs as an event as they should.

 

I don't even know where to start looking for the cause of this issue.

 

VM have been running on this server in the past. With no hardware or BIOS changes, this server had a PFSense router with a passed through NIC running for over a year, but I upgraded to a dedicated box for that about a year ago and turned VMs off on my server because I was not using them.

 

I have attached the log from a freshly created VM, left if "Running" for a few hours and then force stopped it.

Log.txt

Edited September 14, 2024 by Anghywir

[SimonF]

34 minutes ago, Anghywir said:

Copied this over from the general support page, cause I posted there before I saw this one.

 

I decided I was going to try a little project that will require a Windows 10 installation for a little while, so I was going to revive an old VM I used a while ago. I enabled VMs on my server and my VM was still in the list, so I tried to start it.

 

VM shows as started, but no activity change on the server CPU, and when I try to connect to the VNC console for the VM, I gt a failed to connect message instantly.

 

Thought it might be the VM, so I created a new blank VM from the linux template, didn't hand it any ISOs, didn't attach any new devices or change any settings. Same behaviour, instant connection failure on both VNC and Spice console.

 

I stopped all my dockers and turned off autostart, rebooted the server, and the fresh VM still doesn't start. VM logs only show blue and white text (text and system) and I can't see anything there that might be causing issues. It's like it just stops when it should be bringing up the BIOS for the VM.

 

The shutdown or Restart commands from the VM menu in unraid do essentially nothing, not even an entry in the logs, but the force stop option does show in the logs as an event as they should.

 

I don't even know where to start looking for the cause of this issue.

 

VM have been running on this server in the past. With no hardware or BIOS changes, this server had a PFSense router with a passed through NIC running for over a year, but I upgraded to a dedicated box for that about a year ago and turned VMs off on my server because I was not using them.

 

I have attached the log from a freshly created VM, left if "Running" for a few hours and then force stopped it.

Log.txt 4.61 kB · 0 downloads

Do you get a red banner on tbe vnc page, could be a cookie problem if you do.

[Anghywir]

6 minutes ago, SimonF said:

Do you get a red banner on tbe vnc page, could be a cookie problem if you do.

Now I feel a little dumb.

 

Tried in a different browser and it works.

 

Not sure if it's Firefox, or some addin I have installed, but it works in chrome.