VM will not display and virtual-manager core-dumps (after upgrade)?

My VM was working last night but this morning I can’t display anything :-(.

virt-manager starts up okay but if I try to view (open) my VM it crashes. It does not matter if the guest is running or not, virt-manager dumps core (according to systemd-coredump). The log shows nothing untoward:

[Thu, 20 May 2021 10:15:32 virt-manager 2666] DEBUG (serialcon:17) Using VTE API 2.91
[Thu, 20 May 2021 10:15:32 virt-manager 2666] DEBUG (xmleditor:12) Using GtkSource 4
(crashes here)

Interestingly if I start the guest (select & press run) it starts up fine:

[Thu, 20 May 2021 10:18:53 virt-manager 2878] DEBUG (vmmenu:230) Starting vm 'win10'
[Thu, 20 May 2021 10:18:53 virt-manager 2878] DEBUG (connection:706) node device lifecycle event: nodedev=net_macvtap0_52_54_00_3c_4f_fd state=VIR_NODE_DEVICE_EVENT_CREATED reason=0
[Thu, 20 May 2021 10:18:53 virt-manager 2878] DEBUG (connection:706) node device lifecycle event: nodedev=net_vnet0_fe_54_00_dd_60_8d state=VIR_NODE_DEVICE_EVENT_CREATED reason=0
[Thu, 20 May 2021 10:18:53 virt-manager 2878] DEBUG (connection:1069) New nodedev=net_vnet0_fe_54_00_dd_60_8d requested, but it's already tracked.
[Thu, 20 May 2021 10:18:54 virt-manager 2878] DEBUG (connection:631) domain lifecycle event: domain=win10 state=VIR_DOMAIN_EVENT_RESUMED reason=VIR_DOMAIN_EVENT_RESUMED_UNPAUSED
[Thu, 20 May 2021 10:18:54 virt-manager 2878] DEBUG (connection:631) domain lifecycle event: domain=win10 state=VIR_DOMAIN_EVENT_STARTED reason=VIR_DOMAIN_EVENT_STARTED_BOOTED

and the CPU usage graph trickles along nicely.

But if I try to Open it… boom. It’s just virt-manager that crashes, however, the qemu process is still running…

ps ax | grep qemu
   2924 ?        Sl     0:55 /usr/bin/qemu-system-x86_64 ...

My system details:

Distribution:      Clear Linux OS
Installed version: 34630

running on i5-8600K Prime Z370-P with GeForce GT 710 (Nvidia drivers) running three screens under XFCE.

Firstly - I think this is a bug, where should I report it?

Secondly, is there a command line tool I can use to connect to this process and try to force it to display, or at least get more detailed error reports?

Many thanks,
Jerry

PS: systemd reports that Avahi-daemon failed to load - is that relevant?

This was recently updated as a package request and confirmed working.

But are tracked in GitHub as well.

Many thanks, but I can confirm that the reported behaviour still exists in 34640.

PS: It may be a permissions problem (but how did it arise?).

Running virt-viewer as myself (non-priviledged user) cannot find a running guest:

(virt-viewer:25277): virt-viewer-DEBUG: 18:45:42.385: keymap string is empty - nothing to do
(virt-viewer:25277): virt-viewer-DEBUG: 18:45:42.410: disabling smartcard shortcuts
(virt-viewer:25277): virt-viewer-DEBUG: 18:45:42.411: connecting ...
(virt-viewer:25277): virt-viewer-DEBUG: 18:45:42.411: Opening connection to libvirt with URI <null>
(virt-viewer:25277): virt-viewer-DEBUG: 18:45:42.456: initial connect
(virt-viewer:25277): virt-viewer-DEBUG: 18:45:42.456: notebook show status 0x55e08eb04200
(virt-viewer:25277): virt-viewer-DEBUG: 18:45:42.456: Cannot find guest win10

Running virt-viewn as root works fine…

(virt-viewer:25182): virt-viewer-DEBUG: 18:44:19.118: keymap string is empty - nothing to do
(virt-viewer:25182): virt-viewer-DEBUG: 18:44:22.158: disabling smartcard shortcuts
(virt-viewer:25182): virt-viewer-DEBUG: 18:44:22.158: connecting ...
(virt-viewer:25182): virt-viewer-DEBUG: 18:44:22.158: Opening connection to libvirt with URI <null>
(virt-viewer:25182): virt-viewer-DEBUG: 18:44:22.160: initial connect
(virt-viewer:25182): virt-viewer-DEBUG: 18:44:22.160: notebook show status 0x561be3206230
(virt-viewer:25182): virt-viewer-DEBUG: 18:44:22.160: virt_viewer_app_set_uuid_string: UUID changed
 to 1492028b-17c8-4eb4-9014-7284d77517ea
(virt-viewer:25182): virt-viewer-DEBUG: 18:44:22.160: notebook show status 0x561be3206230
(virt-viewer:25182): virt-viewer-DEBUG: 18:44:22.160: Guest win10 is running, determining display

though it does report an error:

(virt-viewer:25182): virt-viewer-DEBUG: 18:44:22.165: Error operation forbidden: read only access p
revents virDomainOpenGraphicsFD
(virt-viewer:25182): virt-viewer-DEBUG: 18:44:22.165: After open connection callback fd=-1
...
(virt-viewer:25182): GSpice-WARNING **: 18:44:25.596: Could not create org.gnome.SessionManager dbus proxy: Could not connect: Connection refused

Nothing obvious from google…

Any thoughts?

I have two workarounds,

  1. use virsh/virt-viewer with --connect quemu:///system (thanks to permissions - How do I list virsh networks without sudo? - Server Fault).
  2. use the latest code from github - which claims to be version 3.2.0, exactly the same as /usr/bin/virt-manager installed via swupd. Go figure.

I am still puzzled as to why /usr/bin/virt-manager suddenly stopped working but can live with the workaround.

PS: /usr/bin/virt-manager also crashes if I select Edit > Preferences, sigh.

Thanks for the information. It is really useful for us.

www.myaarpmedicare.com