FS#74006 - [libvirt] Libvirt 8.1.0 breaks Virtual Machine Manager

Attached to Project: Community Packages
Opened by Frederic Bezies (fredbezies) - Wednesday, 02 March 2022, 07:34 GMT
Last edited by freswa (frederik) - Thursday, 03 March 2022, 12:40 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To freswa (frederik)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: This morning, I noticed that libvirt 8.1.0 was pushed to testing.

When I tried to launch Virtual Machine Manager, I noticed there were no connections made with qemu.

I got this error log:

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

Additional info:
* libvirt 8.1.0-1
* virtmanager 3.2.0-4

Steps to reproduce:
1) Use Archlinux with testing repositories enabled with VirtManager installed.
2) Install last libvirt
3) Launch libvirt
This task depends upon

Closed by  freswa (frederik)
Thursday, 03 March 2022, 12:40 GMT
Reason for closing:  Fixed
Additional comments about closing:  libvirt-1:8.1.0-4
Comment by huyizheng (huyizheng) - Wednesday, 02 March 2022, 08:51 GMT
The problem is, with `libvirt 8.1.0` the `libvirtd.service` won't start:

```
invalid argument: Failed to parse user 'kvm'
Initialization of QEMU state driver failed: invalid argument: Failed to parse user 'kvm'
Driver state initialization failed
```

In my system there's no `kvm` user, only a `kvm` group created by systemd.

`libvirt 8.1.0` adds a `-Dqemu_user=kvm` build option, maybe this is the cause.
Comment by Dmitryi (RusWolf) - Wednesday, 02 March 2022, 10:11 GMT
× libvirtd.service - Virtualization daemon
Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: disabled)
Active: failed (Result: start-limit-hit) since Wed 2022-03-02 13:07:31 MSK; 3min 34s ago
TriggeredBy: × libvirtd.socket
× libvirtd-admin.socket
× libvirtd-ro.socket
Docs: man:libvirtd(8)
https://libvirt.org
Process: 2521 ExecStart=/usr/bin/libvirtd $LIBVIRTD_ARGS (code=exited, status=0/SUCCESS)
Main PID: 2521 (code=exited, status=0/SUCCESS)
Tasks: 2 (limit: 32768)
Memory: 43.8M
CPU: 494ms
CGroup: /system.slice/libvirtd.service
├─704 /usr/bin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/network.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
└─705 /usr/bin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/network.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper

мар 02 13:07:31 wolf-arch libvirtd[2521]: Не удалось инициализировать драйвер состояния QEMU: недопустимый аргумент: Не удалось разобрать пользователя «kvm»
мар 02 13:07:31 wolf-arch libvirtd[2521]: Ошибка инициализации состояния драйвера
мар 02 13:07:31 wolf-arch systemd[1]: libvirtd.service: Deactivated successfully.
мар 02 13:07:31 wolf-arch systemd[1]: libvirtd.service: Unit process 704 (dnsmasq) remains running after unit stopped.
мар 02 13:07:31 wolf-arch systemd[1]: libvirtd.service: Unit process 705 (dnsmasq) remains running after unit stopped.
мар 02 13:07:31 wolf-arch systemd[1]: libvirtd.service: Start request repeated too quickly.
мар 02 13:07:31 wolf-arch systemd[1]: libvirtd.service: Failed with result 'start-limit-hit'.
мар 02 13:07:31 wolf-arch systemd[1]: libvirtd.service: Unit process 704 (dnsmasq) remains running after unit stopped.
мар 02 13:07:31 wolf-arch systemd[1]: libvirtd.service: Unit process 705 (dnsmasq) remains running after unit stopped.
мар 02 13:07:31 wolf-arch systemd[1]: Failed to start Virtualization daemon.
Comment by freswa (frederik) - Wednesday, 02 March 2022, 12:40 GMT
Please check libvirt 8.1.0-2
Comment by Frederic Bezies (fredbezies) - Wednesday, 02 March 2022, 12:47 GMT
libvirt 8.1.0-2 works correctly for me.
Comment by Dmitryi (RusWolf) - Wednesday, 02 March 2022, 13:02 GMT
libvirt 8.1.0-2 has started.
But deleting an unnecessary connection does not work.

Ошибка удаления виртуальной машины «manjaro»: внутренняя ошибка: сокет клиента был закрыт

Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/object/domain.py", line 1356, in delete
self._backend.undefineFlags(flags)
File "/usr/lib/python3.10/site-packages/libvirt.py", line 3215, in undefineFlags
raise libvirtError('virDomainUndefineFlags() failed')
libvirt.libvirtError: Не удалось восстановить данные: Соединение разорвано другой стороной

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/delete.py", line 190, in _async_delete
self._delete_vm(vm)
File "/usr/share/virt-manager/virtManager/delete.py", line 318, in _delete_vm
vm.delete()
File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn
ret = fn(self, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/domain.py", line 1360, in delete
self._backend.undefine()
File "/usr/lib/python3.10/site-packages/libvirt.py", line 3178, in undefine
raise libvirtError('virDomainUndefine() failed')
libvirt.libvirtError: внутренняя ошибка: сокет клиента был закрыт.
Comment by freswa (frederik) - Wednesday, 02 March 2022, 13:10 GMT
try virsh pls
Comment by Dmitryi (RusWolf) - Wednesday, 02 March 2022, 13:35 GMT
[wolf@wolf-arch ~]$ LC_ALL=C sudo virsh list --all
Id Name State
----------------------------
- linux2020 shut off
- manjaro shut off

[wolf@wolf-arch ~]$ LC_ALL=C sudo virsh undefine manjaro
error: Disconnected from qemu:///system due to end of file
error: Failed to undefine domain 'manjaro'
error: End of file while reading data: Input/output error

[wolf@wolf-arch ~]$
Comment by Dmitryi (RusWolf) - Wednesday, 02 March 2022, 13:37 GMT
wolf-arch# LC_ALL=C virsh list --all
Id Name State
----------------------------
- linux2020 shut off
- manjaro shut off

wolf-arch# LC_ALL=C virsh undefine manjaro

error: Disconnected from qemu:///system due to end of file
error: Failed to undefine domain 'manjaro'
error: End of file while reading data: Input/output error

wolf-arch#

Comment by freswa (frederik) - Wednesday, 02 March 2022, 13:37 GMT
Anything in the libvirt logs?
Comment by Dmitryi (RusWolf) - Wednesday, 02 March 2022, 13:41 GMT
I can't watch right now, I have to go home from work.
I'll check at home later.
Comment by Dmitryi (RusWolf) - Wednesday, 02 March 2022, 13:59 GMT
/var/log/libvirt is empty

in dmesg output:
[ 59.796774] rpc-libvirtd[581]: segfault at 18 ip 00007f0b2af65c26 sp 00007f0b5bffe8a0 error 4 in libvirt_driver_qemu.so[7f0b2aeee000+116000]
[ 59.796794] Code: 01 0f 84 d5 03 00 00 4c 89 ff ff 15 a4 a9 11 00 85 c0 0f 88 ec 02 00 00 48 8b 55 c0 48 8b b2 80 00 00 00 48 8b 86 b0 02 00 00 <48> 8b 78 18 48 85 ff 0f 84 bd 00 00 00 ff 15 2f b4 11 00 48 89 45
[ 134.013663] prio-rpc-libvir[1520]: segfault at 18 ip 00007fa6d846dc26 sp 00007fa6daffc8a0 error 4 in libvirt_driver_qemu.so[7fa6d83f6000+116000]
[ 134.013729] Code: 01 0f 84 d5 03 00 00 4c 89 ff ff 15 a4 a9 11 00 85 c0 0f 88 ec 02 00 00 48 8b 55 c0 48 8b b2 80 00 00 00 48 8b 86 b0 02 00 00 <48> 8b 78 18 48 85 ff 0f 84 bd 00 00 00 ff 15 2f b4 11 00 48 89 45
[ 251.107266] prio-rpc-libvir[1644]: segfault at 18 ip 00007f52cecedc26 sp 00007f52d66d18a0 error 4 in libvirt_driver_qemu.so[7f52cec76000+116000]
[ 251.107297] Code: 01 0f 84 d5 03 00 00 4c 89 ff ff 15 a4 a9 11 00 85 c0 0f 88 ec 02 00 00 48 8b 55 c0 48 8b b2 80 00 00 00 48 8b 86 b0 02 00 00 <48> 8b 78 18 48 85 ff 0f 84 bd 00 00 00 ff 15 2f b4 11 00 48 89 45
[ 2091.106627] rpc-libvirtd[3856]: segfault at 18 ip 00007f8786cbdc26 sp 00007f87bd22d8a0 error 4 in libvirt_driver_qemu.so[7f8786c46000+116000]
[ 2091.106657] Code: 01 0f 84 d5 03 00 00 4c 89 ff ff 15 a4 a9 11 00 85 c0 0f 88 ec 02 00 00 48 8b 55 c0 48 8b b2 80 00 00 00 48 8b 86 b0 02 00 00 <48> 8b 78 18 48 85 ff 0f 84 bd 00 00 00 ff 15 2f b4 11 00 48 89 45
[ 2169.971227] rpc-libvirtd[3974]: segfault at 18 ip 00007f605c44dc26 sp 00007f6047ffe8a0 error 4 in libvirt_driver_qemu.so[7f605c3d6000+116000]
[ 2169.971246] Code: 01 0f 84 d5 03 00 00 4c 89 ff ff 15 a4 a9 11 00 85 c0 0f 88 ec 02 00 00 48 8b 55 c0 48 8b b2 80 00 00 00 48 8b 86 b0 02 00 00 <48> 8b 78 18 48 85 ff 0f 84 bd 00 00 00 ff 15 2f b4 11 00 48 89 45
[ 2197.532820] prio-rpc-libvir[4214]: segfault at 18 ip 00007f7bb8b05c26 sp 00007f7bb9ffa8a0 error 4 in libvirt_driver_qemu.so[7f7bb8a8e000+116000]
[ 2197.532837] Code: 01 0f 84 d5 03 00 00 4c 89 ff ff 15 a4 a9 11 00 85 c0 0f 88 ec 02 00 00 48 8b 55 c0 48 8b b2 80 00 00 00 48 8b 86 b0 02 00 00 <48> 8b 78 18 48 85 ff 0f 84 bd 00 00 00 ff 15 2f b4 11 00 48 89 45
[ 2336.240630] rpc-libvirtd[4347]: segfault at 18 ip 00007fca8158dc26 sp 00007fca81f938a0 error 4 in libvirt_driver_qemu.so[7fca81516000+116000]
[ 2336.240652] Code: 01 0f 84 d5 03 00 00 4c 89 ff ff 15 a4 a9 11 00 85 c0 0f 88 ec 02 00 00 48 8b 55 c0 48 8b b2 80 00 00 00 48 8b 86 b0 02 00 00 <48> 8b 78 18 48 85 ff 0f 84 bd 00 00 00 ff 15 2f b4 11 00 48 89 45
[ 3527.032994] rpc-libvirtd[5812]: segfault at 18 ip 00007fd73e93dc26 sp 00007fd7603258a0 error 4 in libvirt_driver_qemu.so[7fd73e8c6000+116000]
[ 3527.033018] Code: 01 0f 84 d5 03 00 00 4c 89 ff ff 15 a4 a9 11 00 85 c0 0f 88 ec 02 00 00 48 8b 55 c0 48 8b b2 80 00 00 00 48 8b 86 b0 02 00 00 <48> 8b 78 18 48 85 ff 0f 84 bd 00 00 00 ff 15 2f b4 11 00 48 89 45
Comment by freswa (frederik) - Wednesday, 02 March 2022, 14:01 GMT
What about journalctl -u libvirtd?
Comment by Dmitryi (RusWolf) - Wednesday, 02 March 2022, 16:33 GMT
[wolf@wolf-pc ~]$ LC_ALL=C sudo virsh list --all
[sudo] password for wolf:
Id Name State
------------------------------
- archlinux shut off
- archlinux-2 shut off
- test shut off

[wolf@wolf-pc ~]$ LC_ALL=C sudo virsh undefine test
error: Disconnected from qemu:///system due to end of file
error: Failed to undefine domain 'test'
error: End of file while reading data: Input/output error

[wolf@wolf-pc ~]$ journalctl -u libvirtd
мар 02 19:23:24 wolf-pc systemd[1]: Starting Virtualization daemon...
мар 02 19:23:24 wolf-pc systemd[1]: Started Virtualization daemon.
мар 02 19:23:26 wolf-pc dnsmasq[730]: started, version 2.86 cachesize 150
мар 02 19:23:26 wolf-pc dnsmasq[730]: compile time options: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset auth cryptohash DNSSEC loop-dete>
мар 02 19:23:26 wolf-pc dnsmasq-dhcp[730]: DHCP, IP range 192.168.10.128 -- 192.168.10.254, lease time 1h
мар 02 19:23:26 wolf-pc dnsmasq-dhcp[730]: DHCP, sockets bound exclusively to interface virbr1
мар 02 19:23:26 wolf-pc dnsmasq[730]: no servers found in /etc/resolv.conf, will retry
мар 02 19:23:26 wolf-pc dnsmasq[730]: read /etc/hosts - 5 addresses
мар 02 19:23:26 wolf-pc dnsmasq[730]: read /var/lib/libvirt/dnsmasq/network.addnhosts - 0 addresses
мар 02 19:23:26 wolf-pc dnsmasq-dhcp[730]: read /var/lib/libvirt/dnsmasq/network.hostsfile
мар 02 19:23:33 wolf-pc dnsmasq[730]: reading /etc/resolv.conf
мар 02 19:23:33 wolf-pc dnsmasq[730]: using nameserver 192.168.100.1#53
мар 02 19:24:48 wolf-pc dnsmasq[1478]: started, version 2.86 cachesize 150
мар 02 19:24:48 wolf-pc dnsmasq[1478]: compile time options: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset auth cryptohash DNSSEC loop-det>
мар 02 19:24:48 wolf-pc dnsmasq-dhcp[1478]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h
мар 02 19:24:48 wolf-pc dnsmasq-dhcp[1478]: DHCP, sockets bound exclusively to interface virbr0
мар 02 19:24:48 wolf-pc dnsmasq[1478]: reading /etc/resolv.conf
мар 02 19:24:48 wolf-pc dnsmasq[1478]: using nameserver 192.168.100.1#53
мар 02 19:24:48 wolf-pc dnsmasq[1478]: read /etc/hosts - 5 addresses
мар 02 19:24:48 wolf-pc dnsmasq[1478]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
мар 02 19:24:48 wolf-pc dnsmasq-dhcp[1478]: read /var/lib/libvirt/dnsmasq/default.hostsfile
мар 02 19:25:05 wolf-pc libvirtd[567]: libvirt version: 8.1.0
мар 02 19:25:05 wolf-pc libvirtd[567]: hostname: wolf-pc
мар 02 19:26:16 wolf-pc systemd[1]: libvirtd.service: Main process exited, code=killed, status=11/SEGV
мар 02 19:26:16 wolf-pc systemd[1]: libvirtd.service: Failed with result 'signal'.
мар 02 19:26:16 wolf-pc systemd[1]: libvirtd.service: Unit process 730 (dnsmasq) remains running after unit stopped.
мар 02 19:26:16 wolf-pc systemd[1]: libvirtd.service: Unit process 731 (dnsmasq) remains running after unit stopped.
мар 02 19:26:16 wolf-pc systemd[1]: libvirtd.service: Unit process 1478 (dnsmasq) remains running after unit stopped.
мар 02 19:26:16 wolf-pc systemd[1]: libvirtd.service: Unit process 1479 (dnsmasq) remains running after unit stopped.
мар 02 19:26:16 wolf-pc systemd[1]: libvirtd.service: Consumed 9.316s CPU time.
мар 02 19:26:16 wolf-pc systemd[1]: libvirtd.service: Scheduled restart job, restart counter is at 1.
мар 02 19:26:16 wolf-pc systemd[1]: Stopped Virtualization daemon.
мар 02 19:26:16 wolf-pc systemd[1]: libvirtd.service: Consumed 9.316s CPU time.
мар 02 19:26:16 wolf-pc systemd[1]: libvirtd.service: Found left-over process 730 (dnsmasq) in control group while starting unit. Ignoring.
мар 02 19:26:16 wolf-pc systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
мар 02 19:26:16 wolf-pc systemd[1]: libvirtd.service: Found left-over process 731 (dnsmasq) in control group while starting unit. Ignoring.
мар 02 19:26:16 wolf-pc systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
мар 02 19:26:16 wolf-pc systemd[1]: libvirtd.service: Found left-over process 1478 (dnsmasq) in control group while starting unit. Ignoring.
мар 02 19:26:16 wolf-pc systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
мар 02 19:26:16 wolf-pc systemd[1]: libvirtd.service: Found left-over process 1479 (dnsmasq) in control group while starting unit. Ignoring.
мар 02 19:26:16 wolf-pc systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
мар 02 19:26:16 wolf-pc systemd[1]: Starting Virtualization daemon...
мар 02 19:26:16 wolf-pc systemd[1]: Started Virtualization daemon.
мар 02 19:26:17 wolf-pc dnsmasq[730]: read /etc/hosts - 5 addresses
мар 02 19:26:17 wolf-pc dnsmasq[730]: read /var/lib/libvirt/dnsmasq/network.addnhosts - 0 addresses
мар 02 19:26:17 wolf-pc dnsmasq-dhcp[730]: read /var/lib/libvirt/dnsmasq/network.hostsfile
мар 02 19:26:17 wolf-pc dnsmasq[1478]: read /etc/hosts - 5 addresses
мар 02 19:26:17 wolf-pc dnsmasq[1478]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
мар 02 19:26:17 wolf-pc dnsmasq-dhcp[1478]: read /var/lib/libvirt/dnsmasq/default.hostsfile
мар 02 19:28:11 wolf-pc systemd[1]: libvirtd.service: Main process exited, code=killed, status=11/SEGV
мар 02 19:28:11 wolf-pc systemd[1]: libvirtd.service: Failed with result 'signal'.
мар 02 19:28:11 wolf-pc systemd[1]: libvirtd.service: Unit process 730 (dnsmasq) remains running after unit stopped.
мар 02 19:28:11 wolf-pc systemd[1]: libvirtd.service: Unit process 731 (dnsmasq) remains running after unit stopped.
мар 02 19:28:11 wolf-pc systemd[1]: libvirtd.service: Unit process 1478 (dnsmasq) remains running after unit stopped.
мар 02 19:28:11 wolf-pc systemd[1]: libvirtd.service: Unit process 1479 (dnsmasq) remains running after unit stopped.
мар 02 19:28:11 wolf-pc systemd[1]: libvirtd.service: Consumed 1.734s CPU time.
мар 02 19:28:11 wolf-pc systemd[1]: libvirtd.service: Scheduled restart job, restart counter is at 2.
мар 02 19:28:11 wolf-pc systemd[1]: Stopped Virtualization daemon.
мар 02 19:28:11 wolf-pc systemd[1]: libvirtd.service: Consumed 1.734s CPU time.
мар 02 19:28:11 wolf-pc systemd[1]: libvirtd.service: Found left-over process 730 (dnsmasq) in control group while starting unit. Ignoring.
мар 02 19:28:11 wolf-pc systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
мар 02 19:28:11 wolf-pc systemd[1]: libvirtd.service: Found left-over process 731 (dnsmasq) in control group while starting unit. Ignoring.
мар 02 19:28:11 wolf-pc systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
мар 02 19:28:11 wolf-pc systemd[1]: libvirtd.service: Found left-over process 1478 (dnsmasq) in control group while starting unit. Ignoring.
мар 02 19:28:11 wolf-pc systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
мар 02 19:28:11 wolf-pc systemd[1]: libvirtd.service: Found left-over process 1479 (dnsmasq) in control group while starting unit. Ignoring.
мар 02 19:28:11 wolf-pc systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
мар 02 19:28:11 wolf-pc systemd[1]: Starting Virtualization daemon...
мар 02 19:28:11 wolf-pc systemd[1]: Started Virtualization daemon.
мар 02 19:28:12 wolf-pc dnsmasq[730]: read /etc/hosts - 5 addresses
мар 02 19:28:12 wolf-pc dnsmasq[730]: read /var/lib/libvirt/dnsmasq/network.addnhosts - 0 addresses
мар 02 19:28:12 wolf-pc dnsmasq-dhcp[730]: read /var/lib/libvirt/dnsmasq/network.hostsfile
мар 02 19:28:12 wolf-pc dnsmasq[1478]: read /etc/hosts - 5 addresses
мар 02 19:28:12 wolf-pc dnsmasq[1478]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
мар 02 19:28:12 wolf-pc dnsmasq-dhcp[1478]: read /var/lib/libvirt/dnsmasq/default.hostsfile

Comment by freswa (frederik) - Wednesday, 02 March 2022, 16:52 GMT
What's your `uname -a`?
Comment by Dmitryi (RusWolf) - Wednesday, 02 March 2022, 16:59 GMT
[wolf@wolf-pc ~]$ uname -a
Linux wolf-pc 5.16.12-arch1-1 #1 SMP PREEMPT Wed, 02 Mar 2022 12:22:51 +0000 x86_64 GNU/Linux
Comment by freswa (frederik) - Wednesday, 02 March 2022, 17:14 GMT
The logs show a segfault and I guess it's when you enter the command which leads to a broken connection from the client.
I can't reproduce, so please take the latest build libvirt-8.1.0-3 which got debug symbols enabled and get a stacktrace.
Comment by Dmitryi (RusWolf) - Wednesday, 02 March 2022, 17:22 GMT
[wolf@wolf-pc ~]$ LC_ALL=C sudo virsh list --all
[sudo] password for wolf:
Id Name State
------------------------------
- archlinux shut off
- archlinux-2 shut off
- test shut off

[wolf@wolf-pc ~]$ LC_ALL=C sudo virsh undefine test
error: Disconnected from qemu:///system due to end of file
error: Failed to undefine domain 'test'
error: End of file while reading data: Input/output error

[wolf@wolf-pc ~]$ journalctl -u libvirtd
мар 02 20:19:14 wolf-pc systemd[1]: Starting Virtualization daemon...
мар 02 20:19:14 wolf-pc systemd[1]: Started Virtualization daemon.
мар 02 20:19:16 wolf-pc dnsmasq[729]: started, version 2.86 cachesize 150
мар 02 20:19:16 wolf-pc dnsmasq[729]: compile time options: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset auth cryptohash DNSSEC loop-dete>
мар 02 20:19:16 wolf-pc dnsmasq-dhcp[729]: DHCP, IP range 192.168.10.128 -- 192.168.10.254, lease time 1h
мар 02 20:19:16 wolf-pc dnsmasq-dhcp[729]: DHCP, sockets bound exclusively to interface virbr1
мар 02 20:19:16 wolf-pc dnsmasq[729]: no servers found in /etc/resolv.conf, will retry
мар 02 20:19:16 wolf-pc dnsmasq[729]: read /etc/hosts - 5 addresses
мар 02 20:19:16 wolf-pc dnsmasq[729]: read /var/lib/libvirt/dnsmasq/network.addnhosts - 0 addresses
мар 02 20:19:16 wolf-pc dnsmasq-dhcp[729]: read /var/lib/libvirt/dnsmasq/network.hostsfile
мар 02 20:19:24 wolf-pc dnsmasq[729]: reading /etc/resolv.conf
мар 02 20:19:24 wolf-pc dnsmasq[729]: using nameserver 192.168.100.1#53
мар 02 20:20:14 wolf-pc systemd[1]: libvirtd.service: Main process exited, code=killed, status=11/SEGV
мар 02 20:20:14 wolf-pc systemd[1]: libvirtd.service: Failed with result 'signal'.
мар 02 20:20:14 wolf-pc systemd[1]: libvirtd.service: Unit process 729 (dnsmasq) remains running after unit stopped.
мар 02 20:20:14 wolf-pc systemd[1]: libvirtd.service: Unit process 730 (dnsmasq) remains running after unit stopped.
мар 02 20:20:14 wolf-pc systemd[1]: libvirtd.service: Consumed 1.208s CPU time.
мар 02 20:20:14 wolf-pc systemd[1]: libvirtd.service: Scheduled restart job, restart counter is at 1.
мар 02 20:20:14 wolf-pc systemd[1]: Stopped Virtualization daemon.
мар 02 20:20:14 wolf-pc systemd[1]: libvirtd.service: Consumed 1.208s CPU time.
мар 02 20:20:14 wolf-pc systemd[1]: libvirtd.service: Found left-over process 729 (dnsmasq) in control group while starting unit. Ignoring.
мар 02 20:20:14 wolf-pc systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
мар 02 20:20:14 wolf-pc systemd[1]: libvirtd.service: Found left-over process 730 (dnsmasq) in control group while starting unit. Ignoring.
мар 02 20:20:14 wolf-pc systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
мар 02 20:20:14 wolf-pc systemd[1]: Starting Virtualization daemon...
мар 02 20:20:14 wolf-pc systemd[1]: Started Virtualization daemon.
мар 02 20:20:15 wolf-pc dnsmasq[729]: read /etc/hosts - 5 addresses
мар 02 20:20:15 wolf-pc dnsmasq[729]: read /var/lib/libvirt/dnsmasq/network.addnhosts - 0 addresses
мар 02 20:20:15 wolf-pc dnsmasq-dhcp[729]: read /var/lib/libvirt/dnsmasq/network.hostsfile

Comment by Dmitryi (RusWolf) - Wednesday, 02 March 2022, 17:25 GMT
Where can I see this stack trace. please tell me.
Comment by Dmitryi (RusWolf) - Wednesday, 02 March 2022, 17:31 GMT
virt-manager.log:

[Ср, 02 мар 2022 20:25:21 virt-manager 1988] DEBUG (storage:139) Found default pool name=default target=/var/lib/libvirt/images
[Ср, 02 мар 2022 20:25:21 virt-manager 1988] DEBUG (connection:482) conn=qemu:///system changed to state=Активно
[Ср, 02 мар 2022 20:25:25 virt-manager 1988] DEBUG (delete:57) Showing delete wizard
[Ср, 02 мар 2022 20:25:28 virt-manager 1988] DEBUG (delete:317) Removing VM 'test'
[Ср, 02 мар 2022 20:25:29 virt-manager 1988] ERROR (domain:1358) libvirt undefineFlags failed, falling back to old style
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/object/domain.py", line 1356, in delete
self._backend.undefineFlags(flags)
File "/usr/lib/python3.10/site-packages/libvirt.py", line 3215, in undefineFlags
raise libvirtError('virDomainUndefineFlags() failed')
libvirt.libvirtError: Достигнут конец файла при чтении данных: Ошибка ввода/вывода
[Ср, 02 мар 2022 20:25:29 virt-manager 1988] DEBUG (error:101) error dialog message:
summary=Ошибка удаления виртуальной машины «test»: внутренняя ошибка: сокет клиента был закрыт
details=Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/object/domain.py", line 1356, in delete
self._backend.undefineFlags(flags)
File "/usr/lib/python3.10/site-packages/libvirt.py", line 3215, in undefineFlags
raise libvirtError('virDomainUndefineFlags() failed')
libvirt.libvirtError: Достигнут конец файла при чтении данных: Ошибка ввода/вывода

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/delete.py", line 190, in _async_delete
self._delete_vm(vm)
File "/usr/share/virt-manager/virtManager/delete.py", line 318, in _delete_vm
vm.delete()
File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn
ret = fn(self, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/domain.py", line 1360, in delete
self._backend.undefine()
File "/usr/lib/python3.10/site-packages/libvirt.py", line 3178, in undefine
raise libvirtError('virDomainUndefine() failed')
libvirt.libvirtError: внутренняя ошибка: сокет клиента был закрыт
[Ср, 02 мар 2022 20:25:29 virt-manager 1988] DEBUG (delete:64) Closing delete wizard
[Ср, 02 мар 2022 20:25:30 virt-manager 1988] DEBUG (engine:299) Error polling connection qemu:///system
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/engine.py", line 294, in _handle_tick_queue
conn.tick_from_engine(**kwargs)
File "/usr/share/virt-manager/virtManager/connection.py", line 1321, in tick_from_engine
self._tick(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/connection.py", line 1204, in _tick
self._hostinfo = self._backend.getInfo()
File "/usr/lib/python3.10/site-packages/libvirt.py", line 4572, in getInfo
raise libvirtError('virNodeGetInfo() failed')
libvirt.libvirtError: внутренняя ошибка: сокет клиента был закрыт
[Ср, 02 мар 2022 20:25:30 virt-manager 1988] DEBUG (connection:837) conn.close() uri=qemu:///system
[Ср, 02 мар 2022 20:25:30 virt-manager 1988] DEBUG (connection:851) Failed to deregister events in conn cleanup
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/connection.py", line 843, in close
self._backend.domainEventDeregisterAny(eid)
File "/usr/lib/python3.10/site-packages/libvirt.py", line 5913, in domainEventDeregisterAny
raise libvirtError('virConnectDomainEventDeregisterAny() failed')
libvirt.libvirtError: внутренняя ошибка: сокет клиента был закрыт
[Ср, 02 мар 2022 20:25:30 virt-manager 1988] DEBUG (connection:876) LEAK: conn close() returned 1, meaning refs may have leaked.
[Ср, 02 мар 2022 20:25:30 virt-manager 1988] DEBUG (connection:482) conn=qemu:///system changed to state=Отключено
[Ср, 02 мар 2022 20:25:57 virt-manager 1988] DEBUG (manager:196) Closing manager
[Ср, 02 мар 2022 20:25:57 virt-manager 1988] DEBUG (engine:323) window counter decremented to 0
[Ср, 02 мар 2022 20:25:57 virt-manager 1988] DEBUG (engine:343) No windows found, requesting app exit
[Ср, 02 мар 2022 20:25:57 virt-manager 1988] DEBUG (delete:64) Closing delete wizard
[Ср, 02 мар 2022 20:25:57 virt-manager 1988] DEBUG (engine:369) Exiting app normally.
Comment by freswa (frederik) - Wednesday, 02 March 2022, 18:36 GMT
You should run libvirt with gdb. See https://wiki.archlinux.org/title/Debugging/Getting_traces
Comment by John Barks (Zod) - Thursday, 03 March 2022, 00:51 GMT
I hope this helps, I seriously don't know what I'm doing.

libvirt 1:8.1.0-3
virt-manager 4.0.0-1

The problem as I see it now is that virt-manager cant delete the machine xml in /etc/libvirt/qemu
error is
Error deleting virtual machine 'archlinux-2': internal error: client socket is closed

Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/object/domain.py", line 1411, in delete
self._backend.undefineFlags(flags)
File "/usr/lib/python3.10/site-packages/libvirt.py", line 3215, in undefineFlags
raise libvirtError('virDomainUndefineFlags() failed')
libvirt.libvirtError: End of file while reading data: Input/output

If I try to use virsh I get...

╭─jbarks@carlos in ~
[🔴] × sudo virsh list --all
Id Name State
------------------------------
- archlinux shut off
- archlinux-2 shut off
- garudalinux shut off
- ubuntu21.10 shut off


╭─jbarks@carlos in ~
╰─λ sudo virsh undefine archlinux-2
error: Disconnected from qemu:///system due to end of file
error: Failed to undefine domain 'archlinux-2'
error: End of file while reading data: Input/output error

I can manually delete the .xml file
   trace.txt (23.6 KiB)
Comment by Toolybird (Toolybird) - Thursday, 03 March 2022, 04:53 GMT
Looks like it was reported and fixed upstream. Trace looks similar:

https://gitlab.com/libvirt/libvirt/-/commit/823a62ec
Comment by freswa (frederik) - Thursday, 03 March 2022, 11:17 GMT
Please check out libvirt-1:8.1.0-4
Comment by John Barks (Zod) - Thursday, 03 March 2022, 12:02 GMT
That got it for me. Thanks!
Comment by Dmitryi (RusWolf) - Thursday, 03 March 2022, 12:21 GMT
Thanks, everything works great now!

Loading...