I’m in the process of updating our documentation to F35 and re-testing the steps to install and configure KVM/libvirt.
I did a pretty standard system installation, installed virtualisation and activated libvirtd.
After reboot I get:
[root@zbox ~]# systemctl status libvirtd ○ libvirtd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: disabled) Active: inactive (dead) TriggeredBy: ○ libvirtd-ro.socket ○ libvirtd-admin.socket ○ libvirtd.socket ○ libvirtd-tcp.socket ○ libvirtd-tls.socket Docs: man:libvirtd(8) https://libvirt.org
It looks as if systemd didn’t even try to start libvirtd.
Same is true with libvirtd.socket:
[root@zbox ~]# systemctl status libvirtd.socket ○ libvirtd.socket - Libvirt local socket Loaded: loaded (/usr/lib/systemd/system/libvirtd.socket; enabled; vendor preset: disabled) Active: inactive (dead) Triggers: ● libvirtd.service Listen: /run/libvirt/libvirt-sock (Stream)
And, of course, I don’t get a virbr0 interface.
If a start libvirtd manually, it starts without any noticeable problems
[root@zbox ~]# systemctl start libvirtd [root@zbox ~]# systemctl status libvirtd ● libvirtd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: disabled) Active: active (running) since Sun 2021-11-07 21:47:36 CET; 6s ago TriggeredBy: ● libvirtd-ro.socket ● libvirtd-admin.socket ● libvirtd.socket ○ libvirtd-tcp.socket ○ libvirtd-tls.socket Docs: man:libvirtd(8) https://libvirt.org Main PID: 1077 (libvirtd) Tasks: 21 (limit: 32768) Memory: 36.2M CPU: 669ms CGroup: /system.slice/libvirtd.service ├─1077 /usr/sbin/libvirtd --timeout 120 ├─1192 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper └─1193 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
21:47:37 zbox dnsmasq[1192]: using only locally-known addresses for fritz.lan 21:47:37 zbox dnsmasq[1192]: using standard nameservers for fritz.lan 21:47:37 zbox dnsmasq[1192]: reading /etc/resolv.conf 21:47:37 zbox dnsmasq[1192]: using nameserver 127.0.0.53#53
21:47:37 zbox dnsmasq[1192]: using only locally-known addresses for 21:47:37 zbox dnsmasq[1192]: using only locally-known addresses for fritz.lan 21:47:37 zbox dnsmasq[1192]: using standard nameservers for fritz.lan 21:47:37 zbox dnsmasq[1192]: read /etc/hosts - 2 addresses 21:47:37 zbox dnsmasq[1192]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 1 addresses 21:47:37 zbox dnsmasq-dhcp[1192]: read /var/lib/libvirt/dnsmasq/default.hostsfile
Did something change in installation of libvirt? Did I miss some decent information?
Best Peter
If I search the journal I find:
Nov 07 20:35:26 zbox.fritz.box kernel: Kernel command line: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-5.14.16-301.fc35.x86_64 root=/dev/mapper/fedora_fedora-root ro rd.lvm.lv=fedora_fedora/root rhgb quiet
Nov 07 20:35:26 zbox.fritz.box kernel: ==Unknown command line parameters==: rhgb BOOT_IMAGE=(hd0,gpt2)/vmlinuz-5.14.16-301.fc35.x86_64
Strange, but it should have nothing to do with libvirt.
Later I find:
20:35:43 zbox systemd[1]: Mounted /var/lib/libvirt
20:35:45 zbox systemd[1]: Listening on SSSD Kerberos Cache Manager responder socket. 20:35:45 zbox systemd[1]: Listening on Libvirt interface local socket. 20:35:45 zbox systemd[1]: Listening on Virtual machine lock manager socket. 20:35:45 zbox systemd[1]: Listening on Virtual machine log manager socket. 20:35:45 zbox systemd[1]: Listening on Libvirt lxc local socket. 20:35:45 zbox systemd[1]: Listening on Libvirt lxc admin socket. 20:35:45 zbox systemd[1]: Listening on Libvirt lxc local read-only socket. 20:35:45 zbox systemd[1]: Listening on Libvirt network local socket. 20:35:45 zbox systemd[1]: Listening on Libvirt nodedev local socket. 20:35:45 zbox audit: BPF prog-id=35 op=LOAD 20:35:45 zbox systemd[1]: Listening on Libvirt nwfilter local socket. 20:35:45 zbox systemd[1]: Listening on Libvirt proxy local socket. 20:35:45 zbox systemd[1]: Listening on Libvirt qemu local socket. 20:35:45 zbox systemd[1]: Listening on Libvirt qemu admin socket. 20:35:45 zbox systemd[1]: Listening on Libvirt qemu local read-only socket. 20:35:45 zbox systemd[1]: Listening on Libvirt secret local socket. 20:35:45 zbox systemd[1]: Listening on Libvirt storage local socket. 20:35:45 zbox systemd[1]: Condition check resulted in Libvirt libxl local socket being skipped. 20:35:45 zbox systemd[1]: Condition check resulted in Libvirt libxl admin socket being skipped. 20:35:45 zbox systemd[1]: Condition check resulted in Libvirt libxl local read-only socket being skipped.
The most notable change to libvirt is this one: https://fedoraproject.org/wiki/Changes/LibvirtModularDaemons
---
### Contact dschier@while-true-do.io while-true-do.io
### Code code.while-true-do.io github.com/daniel-wtd/ github.com/while-true-do/
### Social dschier @libera.chat
### Disclaimer If not stated otherwise all of my work is licensed under a Creative Commons Attribution 4.0 International License (creativecommons.org/licenses/by/4.0/).
On 7. Nov 2021, at 21:53, Peter Boy pboy@uni-bremen.de wrote:
I’m in the process of updating our documentation to F35 and re-testing the steps to install and configure KVM/libvirt.
I did a pretty standard system installation, installed virtualisation and activated libvirtd.
After reboot I get:
[root@zbox ~]# systemctl status libvirtd ○ libvirtd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: disabled) Active: inactive (dead) TriggeredBy: ○ libvirtd-ro.socket ○ libvirtd-admin.socket ○ libvirtd.socket ○ libvirtd-tcp.socket ○ libvirtd-tls.socket Docs: man:libvirtd(8) https://libvirt.org
It looks as if systemd didn’t even try to start libvirtd.
Same is true with libvirtd.socket:
[root@zbox ~]# systemctl status libvirtd.socket ○ libvirtd.socket - Libvirt local socket Loaded: loaded (/usr/lib/systemd/system/libvirtd.socket; enabled; vendor preset: disabled) Active: inactive (dead) Triggers: ● libvirtd.service Listen: /run/libvirt/libvirt-sock (Stream)
And, of course, I don’t get a virbr0 interface.
If a start libvirtd manually, it starts without any noticeable problems
[root@zbox ~]# systemctl start libvirtd [root@zbox ~]# systemctl status libvirtd ● libvirtd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: disabled) Active: active (running) since Sun 2021-11-07 21:47:36 CET; 6s ago TriggeredBy: ● libvirtd-ro.socket ● libvirtd-admin.socket ● libvirtd.socket ○ libvirtd-tcp.socket ○ libvirtd-tls.socket Docs: man:libvirtd(8) https://libvirt.org Main PID: 1077 (libvirtd) Tasks: 21 (limit: 32768) Memory: 36.2M CPU: 669ms CGroup: /system.slice/libvirtd.service ├─1077 /usr/sbin/libvirtd --timeout 120 ├─1192 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper └─1193 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
21:47:37 zbox dnsmasq[1192]: using only locally-known addresses for fritz.lan 21:47:37 zbox dnsmasq[1192]: using standard nameservers for fritz.lan 21:47:37 zbox dnsmasq[1192]: reading /etc/resolv.conf 21:47:37 zbox dnsmasq[1192]: using nameserver 127.0.0.53#53
21:47:37 zbox dnsmasq[1192]: using only locally-known addresses for 21:47:37 zbox dnsmasq[1192]: using only locally-known addresses for fritz.lan 21:47:37 zbox dnsmasq[1192]: using standard nameservers for fritz.lan 21:47:37 zbox dnsmasq[1192]: read /etc/hosts - 2 addresses 21:47:37 zbox dnsmasq[1192]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 1 addresses 21:47:37 zbox dnsmasq-dhcp[1192]: read /var/lib/libvirt/dnsmasq/default.hostsfile
Did something change in installation of libvirt? Did I miss some decent information?
Best Peter
If I search the journal I find:
Nov 07 20:35:26 zbox.fritz.box kernel: Kernel command line: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-5.14.16-301.fc35.x86_64 root=/dev/mapper/fedora_fedora-root ro rd.lvm.lv=fedora_fedora/root rhgb quiet
Nov 07 20:35:26 zbox.fritz.box kernel: ==Unknown command line parameters==: rhgb BOOT_IMAGE=(hd0,gpt2)/vmlinuz-5.14.16-301.fc35.x86_64
Strange, but it should have nothing to do with libvirt.
Later I find:
20:35:43 zbox systemd[1]: Mounted /var/lib/libvirt
20:35:45 zbox systemd[1]: Listening on SSSD Kerberos Cache Manager responder socket. 20:35:45 zbox systemd[1]: Listening on Libvirt interface local socket. 20:35:45 zbox systemd[1]: Listening on Virtual machine lock manager socket. 20:35:45 zbox systemd[1]: Listening on Virtual machine log manager socket. 20:35:45 zbox systemd[1]: Listening on Libvirt lxc local socket. 20:35:45 zbox systemd[1]: Listening on Libvirt lxc admin socket. 20:35:45 zbox systemd[1]: Listening on Libvirt lxc local read-only socket. 20:35:45 zbox systemd[1]: Listening on Libvirt network local socket. 20:35:45 zbox systemd[1]: Listening on Libvirt nodedev local socket. 20:35:45 zbox audit: BPF prog-id=35 op=LOAD 20:35:45 zbox systemd[1]: Listening on Libvirt nwfilter local socket. 20:35:45 zbox systemd[1]: Listening on Libvirt proxy local socket. 20:35:45 zbox systemd[1]: Listening on Libvirt qemu local socket. 20:35:45 zbox systemd[1]: Listening on Libvirt qemu admin socket. 20:35:45 zbox systemd[1]: Listening on Libvirt qemu local read-only socket. 20:35:45 zbox systemd[1]: Listening on Libvirt secret local socket. 20:35:45 zbox systemd[1]: Listening on Libvirt storage local socket. 20:35:45 zbox systemd[1]: Condition check resulted in Libvirt libxl local socket being skipped. 20:35:45 zbox systemd[1]: Condition check resulted in Libvirt libxl admin socket being skipped. 20:35:45 zbox systemd[1]: Condition check resulted in Libvirt libxl local read-only socket being skipped.
server mailing list -- server@lists.fedoraproject.org To unsubscribe send an email to server-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Am 07.11.2021 um 22:29 schrieb Daniel Schier dschier@while-true-do.io:
The most notable change to libvirt is this one: https://fedoraproject.org/wiki/Changes/LibvirtModularDaemons
I had briefly read over this a long time ago and saved it for myself: backwards compatible, nothing changes on the outside. We had wanted to have a Test Day for this change, but unfortunately nothing came of it.
And now I see on closer reading, that with a new installation the autostart is quite different.
This is going to be a hell of a lot of extra work.
Thanks Peter
server@lists.fedoraproject.org