Qemu not working after updates

LawrieHoltby · 2025-02-17 18:15:40

Hi, each time an update happens on my XFCE 25 laptop I am unable to run QEMU until I reinstall virtual-manager from app installer. Please help as this is a pain.

ToZ · 2025-02-17 21:22:01

Hello and welcome.

LawrieHoltby wrote:

from app installer.

What is "app installer"?

Also, maybe you could provide some info about your system/setup? Which distro, version of Xfce, etc.

LawrieHoltby · 2025-02-18 08:22:38

Sorry! MX Package Installer. MX XFCE 23.5, kernel 6.12.13.2 liquorix, amd64, Dell Laptop 32GB RAM. Anything else?

ToZ · 2025-02-18 11:19:41

When you say "qemu fails to run", what exactly do you mean? Are you starting the VM from within virt-manager? Is there an error message (also check your journal for error messages)?

Is it any update that causes this to happen or only specific updates (like a kernel update)?

LawrieHoltby · 2025-02-18 13:40:44

ToZ wrote:

When you say "qemu fails to run", what exactly do you mean? Are you starting the VM from within virt-manager? Is there an error message (also check your journal for error messages)?
Is it any update that causes this to happen or only specific updates (like a kernel update)?

Hi, i have virt-manager set to execute on startup, the error message (cannot recall the exact words - I'm a relative newby on Linux) suggests it's the daemon not starting. It's not EVERY update, sometime I get away with it) but most of them and certainly kernel updates. Next time it occurs I'll screenshot the error message.
If there was a way to automatically reinstall virt-manager after an update I'd jump at it.

Thanks again for your interest in helping.

Added later 13 min 38 s:
error message already! see below
--------------------------------------

Unable to connect to libvirt qemu:///system.

Verify that the 'libvirtd' daemon is running.

Libvirt URI is: qemu:///system

Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/connection.py", line 923, in _do_open
self._backend.open(cb, data)
File "/usr/share/virt-manager/virtinst/connection.py", line 171, in open
conn = libvirt.openAuth(self._open_uri,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/libvirt.py", line 147, in openAuth
raise libvirtError('virConnectOpenAuth() failed')
libvirt.libvirtError: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory

ToZ · 2025-02-18 16:38:55

Would seem to indicate that the libvirtd deamon isn't running.

A couple of things to try:

Remove virt-manager from autostart and start it manually. If it works, there maybe a race condition happening
Next time this happens, post back the output of the following command:
```
systemctl status libvirtd.service
```

Note: you can also manually try to restart the libvirtd daemon to see if that helps:

sudo systemctl restart libvirtd.service

LawrieHoltby · 2025-02-18 16:42:24

ToZ wrote:

Would seem to indicate that the libvirtd deamon isn't running.
A couple of things to try:
Remove virt-manager from autostart and start it manually. If it works, there maybe a race condition happening
Next time this happens, post back the output of the following command:
systemctl status libvirtd.service
Note: you can also manually try to restart the libvirtd daemon to see if that helps:
sudo systemctl restart libvirtd.service

Yes, will do.

Added later 16 min 04 s:

LawrieHoltby wrote:

ToZ wrote:
Would seem to indicate that the libvirtd deamon isn't running.
A couple of things to try:
Remove virt-manager from autostart and start it manually. If it works, there maybe a race condition happening
Next time this happens, post back the output of the following command:
systemctl status libvirtd.service
Note: you can also manually try to restart the libvirtd daemon to see if that helps:
sudo systemctl restart libvirtd.service
Yes, will do.

another update and result from 1st line says something about system has not been booted with systyemd! second line gives the same error!

just manually reinstalled virt-manager and now all working again!

Last edited by LawrieHoltby (2025-02-18 17:00:15)

ToZ · 2025-02-18 19:56:32

LawrieHoltby wrote:

another update and result from 1st line says something about system has not been booted with systyemd! second line gives the same error!

If you could provide the actual error or copy of output that would be helpful.

LawrieHoltby · 2025-02-18 19:58:35

ToZ wrote:

LawrieHoltby wrote:
another update and result from 1st line says something about system has not been booted with systyemd! second line gives the same error!
If you could provide the actual error or copy of output that would be helpful.

Ok next error. Can I attach screenshots to my replies?

ToZ · 2025-02-18 22:02:41

Yes, upload them to a image hosting site and post the link here to them.

Or, just copy/paste the output back into the reply box (easier).

LawrieHoltby · 2025-02-20 09:04:20

ToZ wrote:

Yes, upload them to a image hosting site and post the link here to them.
Or, just copy/paste the output back into the reply box (easier).

Hi, everything was OK yesterday but not working today, images are at: https://ibb.co/Zp9M8wRb
https://ibb.co/YBNpHh7X
https://ibb.co/tpZ1fT9H
https://ibb.co/hRrHT3XR

sorry - ignore the one showing the win10 VMM - thats how it looks when working!

Last edited by LawrieHoltby (2025-02-20 09:45:52)

ToZ · 2025-02-20 11:22:16

When it doesn't work, can you post back the results of the following command:

systemctl status libvirtd.service --no-pager

Then run the following to see if it fixes the problem:

sudo systemctl restart libvirtd.service

k3dAR · 2025-02-20 15:03:51

i'm almost sure whole "problem" is:
- virtr-manager is autostarted before libvirtd is fully up
- reinstalling virt-manager also restart libvirtd.service

Then manually restarting libvirtd service must work, also maybe not need, but simple close error and double click to line "QEMU/KVM Not connected" which refresh VM list from now already started libvirtd ;-)

My tip for sollutions is:
- don't start virt-manager automaticaly
- only set specific VM to auto start in VM View/Details/Boot Options/Start virtual machine on host boot up"

EDIT: aah, ignore please my message, as i miss whole point of problem is only after some package update ;-)

Last edited by k3dAR (2025-02-20 15:05:48)

LawrieHoltby · 2025-02-20 16:21:44

ToZ wrote:

When it doesn't work, can you post back the results of the following command:
systemctl status libvirtd.service --no-pager
Then run the following to see if it fixes the problem:
sudo systemctl restart libvirtd.service

error is at: https://ibb.co/chKwsYdK

same error when second command run.

k3dAR · 2025-02-20 17:09:48

LawrieHoltby wrote:

error is at: https://ibb.co/chKwsYdK

Really you post very little cutoff part of error message, or is problem with image loading on my side ? :-D

LawrieHoltby · 2025-02-20 18:01:03

k3dAR wrote:

LawrieHoltby wrote:
error is at: https://ibb.co/chKwsYdK
Really you post very little cutoff part of error message, or is problem with image loading on my side ? :-D

So sorry - don't know what happened! Next time it comes up I'll post it but its the same message about systemd as before.

k3dAR · 2025-02-20 19:13:09

ahh, now i understand, you use MX Linux which don't use systemd for services, so sure you see this error:

System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down

This is reason, when ask for help, is really need post full/exact error message and not "someting like..." ;-)

So, systemctl is unusable for you, but as MX Linux use Sys-V init:

# status, although show only if running or not
service libvirtd status

# restart service
sudo service libvirtd restart

BTW: this is status on MX Linux:

Checking status of libvirt management daemon: libvirtd running.

and this status on my primary Xubuntu with systemd:

● libvirtd.service - libvirt legacy monolithic daemon
     Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; preset: enabled)
     Active: active (running) since Thu 2025-02-20 18:11:12 CET; 1h 56min ago
TriggeredBy: ● libvirtd-admin.socket
             ● libvirtd.socket
             ● libvirtd-ro.socket
       Docs: man:libvirtd(8)
             https://libvirt.org/
   Main PID: 926427 (libvirtd)
      Tasks: 26 (limit: 32768)
     Memory: 104.8M (peak: 184.6M)
        CPU: 10.259s
     CGroup: /system.slice/libvirtd.service
             ├─  2690 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default68.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
             ├─  2691 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default68.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
             ├─  2773 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
             ├─  2774 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
             └─926427 /usr/sbin/libvirtd --timeout 120

Feb 20 18:44:56 t480 dnsmasq-dhcp[2773]: DHCPOFFER(virbr0) 192.168.122.243 52:54:00:b4:00:43
Feb 20 18:44:56 t480 dnsmasq-dhcp[2773]: DHCPREQUEST(virbr0) 192.168.122.243 52:54:00:b4:00:43
Feb 20 18:44:56 t480 dnsmasq-dhcp[2773]: DHCPACK(virbr0) 192.168.122.243 52:54:00:b4:00:43 mx23
Feb 20 18:54:41 t480 dnsmasq-dhcp[2773]: DHCPREQUEST(virbr0) 192.168.122.243 52:54:00:b4:00:43
Feb 20 18:54:41 t480 dnsmasq-dhcp[2773]: DHCPACK(virbr0) 192.168.122.243 52:54:00:b4:00:43 mx23
Feb 20 19:24:41 t480 dnsmasq-dhcp[2773]: DHCPREQUEST(virbr0) 192.168.122.243 52:54:00:b4:00:43
Feb 20 19:24:41 t480 dnsmasq-dhcp[2773]: DHCPACK(virbr0) 192.168.122.243 52:54:00:b4:00:43 mx23
Feb 20 19:40:07 t480 libvirtd[926427]: cannot parse process status data
Feb 20 19:41:28 t480 dnsmasq-dhcp[2773]: DHCPREQUEST(virbr0) 192.168.122.243 52:54:00:b4:00:43
Feb 20 19:41:28 t480 dnsmasq-dhcp[2773]: DHCPACK(virbr0) 192.168.122.243 52:54:00:b4:00:43 mx23

LawrieHoltby · 2025-02-25 08:32:42

didn't work I'm afraid - after today's update:

$ sudo service libvirtd restart
[sudo] password for LawrieHoltby:
Restarting libvirt management daemon: /usr/sbin/libvirtdlibvirt: error : failed to open /var/log/libvirt/libvirtd.log: No such file or directory

eriefisher · 2025-02-25 11:04:19

What about:

service libvirtd start

It it wants a log file it should be creating it unless you have permission issues.

LawrieHoltby · 2025-02-25 11:10:27

LawrieHoltby@mx:~
$ service libvirtd start
Starting libvirt management daemon: libvirtd failed!
LawrieHoltby@mx:~
$ sudo service libvirtd start
[sudo] password for LawrieHoltby:
Starting libvirt management daemon: libvirtdlibvirt: error : failed to open /var/log/libvirt/libvirtd.log: No such file or directory
failed!
LawrieHoltby@mx:~

Added later 11 min 41 s:
I've re-installed libvirt and all is well AGAIN! and the result of sudo service libvirtd restart
is:
[sudo] password for LawrieHoltby:
Restarting libvirt management daemon: /usr/sbin/libvirtd.

eriefisher · 2025-02-25 11:22:10

Let's try and create the log file.

sudo touch /var/log/libvirt/libvirtd.log

Then try and start it again.

Xfce Forum

Sub domains

#1 2025-02-17 18:15:40

Qemu not working after updates

#2 2025-02-17 21:22:01

Re: Qemu not working after updates

#3 2025-02-18 08:22:38

Re: Qemu not working after updates

#4 2025-02-18 11:19:41

Re: Qemu not working after updates

#5 2025-02-18 13:40:44

Re: Qemu not working after updates

#6 2025-02-18 16:38:55

Re: Qemu not working after updates

#7 2025-02-18 16:42:24

Re: Qemu not working after updates

#8 2025-02-18 19:56:32

Re: Qemu not working after updates

#9 2025-02-18 19:58:35

Re: Qemu not working after updates

#10 2025-02-18 22:02:41

Re: Qemu not working after updates

#11 2025-02-20 09:04:20

Re: Qemu not working after updates

#12 2025-02-20 11:22:16

Re: Qemu not working after updates

#13 2025-02-20 15:03:51

Re: Qemu not working after updates

#14 2025-02-20 16:21:44

Re: Qemu not working after updates

#15 2025-02-20 17:09:48

Re: Qemu not working after updates

#16 2025-02-20 18:01:03

Re: Qemu not working after updates

#17 2025-02-20 19:13:09

Re: Qemu not working after updates

#18 2025-02-25 08:32:42

Re: Qemu not working after updates

#19 2025-02-25 11:04:19

Re: Qemu not working after updates

#20 2025-02-25 11:10:27

Re: Qemu not working after updates

#21 2025-02-25 11:22:10

Re: Qemu not working after updates

Board footer