[RESOLVED] Virt-Manager keeps on locking up whenever VMs are launched on Ubuntu 22.10

Operating Systems & Open Source Virtualization
1

SOLVED

Edit

I purged and reinstalled some gstreamer packages (some failed). After reinstall, I no longer get the GLib-GObject warnings anymore.

Rhythmbox also sees that same thing, and won’t launch.

Out of the blue, Virt-Manager would stop working, VMs get “paused” and after I kill the window, I can bring it back, but my VMs are not working anymore. I have to kill the VM and restart.

Only seems to happen if I click the button “Open” which opens up the viewer/window that says “Guest is running”.

[Thu, 20 Oct 2022 20:31:22 virt-manager 14078] DEBUG (vmmenu:210) Starting vm 'NeonUnstable-GPU'
[Thu, 20 Oct 2022 20:31:23 virt-manager 14078] DEBUG (connection:706) node device lifecycle event: nodedev=net_vnet3_fe_54_00_9c_77_73 state=VIR_NODE_DEVICE_EVENT_CREATED reason=0
[Thu, 20 Oct 2022 20:31:27 virt-manager 14078] DEBUG (connection:646) domain agent lifecycle event: domain=NeonUnstable-GPU state=VIR_CONNECT_DOMAIN_EVENT_AGENT_LIFECYCLE_STATE_DISCONNECTED reason=1
[Thu, 20 Oct 2022 20:31:27 virt-manager 14078] DEBUG (console:721) Starting connect process for proto=spice trans= connhost=127.0.0.1 connuser= connport= gaddr=127.0.0.1 gport=5900 gtlsport=None gsocket=None
[Thu, 20 Oct 2022 20:31:27 virt-manager 14078] DEBUG (connection:631) domain lifecycle event: domain=NeonUnstable-GPU state=VIR_DOMAIN_EVENT_RESUMED reason=VIR_DOMAIN_EVENT_RESUMED_UNPAUSED
[Thu, 20 Oct 2022 20:31:27 virt-manager 14078] DEBUG (connection:631) domain lifecycle event: domain=NeonUnstable-GPU state=VIR_DOMAIN_EVENT_STARTED reason=VIR_DOMAIN_EVENT_STARTED_BOOTED
[Thu, 20 Oct 2022 20:31:27 virt-manager 14078] DEBUG (viewers:601) Requesting fd for channel: <SpiceClientGLib.UsbredirChannel object at 0x7f5f02219680 (SpiceUsbredirChannel at 0x55b917e46330)>
[Thu, 20 Oct 2022 20:31:27 virt-manager 14078] DEBUG (viewers:601) Requesting fd for channel: <SpiceClientGLib.UsbredirChannel object at 0x7f5f00278080 (SpiceUsbredirChannel at 0x55b917e46640)>

(gst-plugin-scanner:14318): GLib-GObject-WARNING **: 20:31:28.040: type name '-a-png-encoder-pred' contains invalid characters

(gst-plugin-scanner:14318): GLib-GObject-CRITICAL **: 20:31:28.040: g_type_set_qdata: assertion 'node != NULL' failed

(gst-plugin-scanner:14318): GLib-GObject-CRITICAL **: 20:31:28.040: g_type_set_qdata: assertion 'node != NULL' failed

(gst-plugin-scanner:14318): GLib-GObject-WARNING **: 20:31:28.101: type name '-a-png-encoder-pred' contains invalid characters

(gst-plugin-scanner:14318): GLib-GObject-CRITICAL **: 20:31:28.101: g_type_set_qdata: assertion 'node != NULL' failed

(gst-plugin-scanner:14318): GLib-GObject-CRITICAL **: 20:31:28.101: g_type_set_qdata: assertion 'node != NULL' failed
[0:09:18.268273233] [14318] ERROR Controls controls.cpp:689 Control 0x00000000 not in the idmap
[0:09:18.268287623] [14318] FATAL default controls.cpp:654 assertion "validate()" failed in ControlInfoMap()

If they are VMs with GPU passthrough, they still work, but Virt-Manager crashes, which led me to conclude that only Virt-Manager is wonky.

2

Try running virt-manager on another system and use SSH to connect to your main rig, if that is an option. I find it impressive that virt-man of all things is crashing. I use it on my RPI 4 to connect to my TR system and create VMs, but usually start them with virsh via SSH.

So what errors are you getting now?

3 
[0:09:18.268273233] [14318] ERROR Controls controls.cpp:689 Control 0x00000000 not in the idmap
[0:09:18.268287623] [14318] FATAL default controls.cpp:654 assertion "validate()" failed in ControlInfoMap()

It only crashes if the “viewer” is on.

4

If you have the option, try to use virt-manager inside one of your VMs that have GPU passthrough and connect to your host that way. Maybe also try changing the viewer type and the virtual display (you can try virtio).

Not sure how we can troubleshoot it, as it looks like c++ code. I would think the version you are using in Ubuntu 22.10 may have not been updated to use the latest c library or something. Reinstalling won’t really help. If you feel adventurous, you could install nix package manager on ubuntu and run the nix-env to install virt-manager and use that version. It might get fixed if you wait a while.

5

(post deleted by author)

6

thanks. I had a sneaking suspicion so I double checked my 22.10 Ubuntu Unity VM, and it didn’t have g++-11 or cpp-11 packages installed. I removed them, and I got Rhythmbox booted.

I have no clue why Virt-Manager won’t boot though.

Funny thing, however is that my laptop, also runs on Kubuntu 22.10 and more recently upgraded, also had those 2 and both Rhythmbox and Virt-Manager still run.

1 Like
7

SOLVED

I reinstalled cpp-12 & g++-12 packages and it worked!