Virtual Machines won't start after upgrade from Bluefin to Cobia

[SFaulken]

This morning, I upgraded from Bluefin 22.12.3.3 to Cobia 23.10.0.1 via switch the trains in the Updater. Went quite smoothly, until I noticed that neither of the virtual machines I have installed in Virtualization are starting.

I'm not certain what is going on, but I cannot get a VNC connection to either of them via the "Display" button, and the "Serial Console" button works, but gives no output.

I've attached the logs from both virtual machines, and hopefully somebody can point me at a solution, I've done a fair bit of searching on the web, and the forums, and haven't found anything just yet.

https://paste.opensuse.org/2170b9d96292 (openSUSE MicroOS)
https://paste.opensuse.org/44db77dcdc5e (openSUSE Tumbleweed)

The host machine TrueNAS Scale is running on is a Ryzen 5 5600G, 64GB of RAM, no Graphics Card installed.

 

[joeschmuck]

Welcome to TrueNAS Forums.

Please post your attachments in our forum vice linking to other sites. Some sites destroy the data after a period of time, your looks to expire in an hour. Also many of our members do not like to click on external links, too many bad things out there.

Also, SFaulken reminds me of the movie War Games.

 

[SFaulken]

Fair enough. Here they are as attachments

 

[probain]

One undocumented change is that VNC isn't included in the hypervisor anymore. And it now only uses Spice. And you must use a 2char password minimum, for it to work.

 

[SFaulken]

One undocumented change is that VNC isn't included in the hypervisor anymore. And it now only uses Spice. And you must use a 2char password minimum, for it to work.

What do you mean by 2char password?

 

[probain]

What do you mean by 2char password?

Password containing at least two alfanumeric charactes.

 

[SFaulken]

I'm not sure how that applies to my issue, but none of my passwords are less than 2 characters.

 

[probain]

It doesn't solve your boot isues with your vms.
But remove the display device. And add a new one in its place. And maybe you'll be able to see what they're doing when booting.

 

[SFaulken]

It doesn't solve your boot isues with your vms.
But remove the display device. And add a new one in its place. And maybe you'll be able to see what they're doing when booting.

Excellent, that actually did the trick, sort of. I removed the Display device from the "Devices" and unchecked "Ensure Display Device" under the GPU settings, and the Tumbleweed VM comes up like it's supposed to.

 

[xbgt85]

I was making a new post for my issue but I had read this one and found this also fixed my issue.

I found that if you try to point to an existing Vdisk with a display device still attached (in my case to any VM not even the one I'm working on) it can't find the old disks until I happened to remove the display device on another vm and it works fine now.