Virt-Manager keeps on locking up whenever VMs are launched

Bug #1993760 reported by Jonas Gamao
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
virt-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

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.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: virt-manager 1:4.1.0-1
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Thu Oct 20 19:58:01 2022
InstallationDate: Installed on 2022-01-14 (279 days ago)
InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
PackageArchitecture: all
SourcePackage: virt-manager
UpgradeStatus: Upgraded to kinetic on 2022-10-20 (0 days ago)

Revision history for this message
Jonas Gamao (yamiyukisenpai) wrote :
Revision history for this message
Jonas Gamao (yamiyukisenpai) wrote :

[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()

Seems to happen when I open the Viewer thingy. If I leave it closed it works fine.

Revision history for this message
Jonas Gamao (yamiyukisenpai) wrote : Re: Virtual Machines keeps on locking up whenever they're opened

In addition, when I say "open", I meant when I click the button "open". If I don't click it, but I start it, it works.

summary: - Virtual Machines keeps on locking up
+ Virtual Machines keeps on locking up whenever they're opened
Revision history for this message
Jonas Gamao (yamiyukisenpai) wrote :

This applies to when I don't have a SPICE display (and using a GPU passthrough instead), and when I'm using a SPICE display.

If I have the configuration open, it doesn't crash.

summary: - Virtual Machines keeps on locking up whenever they're opened
+ Virt-Manager keeps on locking up whenever VMs are launched
Revision history for this message
Jonas Gamao (yamiyukisenpai) wrote :

I tried to launch a VM that's using SPICE display, and I got this:

[Sat, 29 Oct 2022 17:13:55 virt-manager 72529] DEBUG (vmwindow:185) Showing VM details: <vmmDomain name=Lubuntu id=0x7f6495534a00>
[Sat, 29 Oct 2022 17:13:55 virt-manager 72529] DEBUG (engine:316) window counter incremented to 2
[Sat, 29 Oct 2022 17:14:04 virt-manager 72529] DEBUG (vmmenu:210) Starting vm 'Lubuntu'
[Sat, 29 Oct 2022 17:14:04 virt-manager 72529] DEBUG (connection:706) node device lifecycle event: nodedev=net_vnet5_fe_54_00_9b_81_f9 state=VIR_NODE_DEVICE_EVENT_CREATED reason=0
[Sat, 29 Oct 2022 17:14:04 virt-manager 72529] DEBUG (connection:646) domain agent lifecycle event: domain=Lubuntu state=VIR_CONNECT_DOMAIN_EVENT_AGENT_LIFECYCLE_STATE_DISCONNECTED reason=1
[Sat, 29 Oct 2022 17:14:04 virt-manager 72529] DEBUG (console:721) Starting connect process for proto=spice trans= connhost=127.0.0.1 connuser= connport= gaddr=127.0.0.1 gport=None gtlsport=None gsocket=None
[Sat, 29 Oct 2022 17:14:05 virt-manager 72529] DEBUG (connection:631) domain lifecycle event: domain=Lubuntu state=VIR_DOMAIN_EVENT_RESUMED reason=VIR_DOMAIN_EVENT_RESUMED_UNPAUSED
[Sat, 29 Oct 2022 17:14:05 virt-manager 72529] DEBUG (connection:631) domain lifecycle event: domain=Lubuntu state=VIR_DOMAIN_EVENT_STARTED reason=VIR_DOMAIN_EVENT_STARTED_BOOTED
[10:02:07.081617086] [72643] ERROR Controls controls.cpp:689 Control 0x00000000 not in the idmap
[10:02:07.081631226] [72643] FATAL default controls.cpp:654 assertion "validate()" failed in ControlInfoMap()
Killed

It seems to be related to bug 1993751, since the last line are exactly the same.

Revision history for this message
Jonas Gamao (yamiyukisenpai) wrote :

Fixed it! Might've been a corrupted package as I reinstalled `cpp-12` and `g++-12` packages.

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Hi Jonas,
I'm happy you resolved it for yourself, but I'm concerned as I fail to see the connection/influence of compilers (cpp-12/g++-12) onto prebuilt binaries from virt-manager.

If you ever find more about the root cause I'd be curious about it.

Otherwise - for now, since it is no more a bug, marking it "invalid".

Reference: related to https://askubuntu.com/questions/1436686/rhythmbox-virt-manager-wont-launch-on-22-10-errors-seems-to-be-related-to

Changed in virt-manager (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.