F35 libvirtd doesn't start after boot
by Peter Boy
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.
2 years, 5 months
Ongoing Fedora website revamp - FEEDBACK needed!
by Peter Boy
After a longer time of preparations the work on the website-revamp is starting now. The first session is Wednesday 27.
In a first step will rebuild the Fedora landing page (fedoraproject.org) and the download page (getfedora.org).
See: https://fedoraproject.org/wiki/Websites/Fedora_Website_Revamp
Currently the Fedora landing page is simple a redirect on the download page. In the future the landing page will be the main page with central information about Fedora and a download link to the download page.
For the design and content of the main page Máirín Duffy made a proposal.
https://discussion.fedoraproject.org/t/a-new-conceptual-model-for-fedora/...
Her proposal is "meant to represent 'the story' of Fedora and how you would use it, and serve as a model from which we will build the narrative for Fedora and its web presence.“
In this model Fedora is
- either a desktop user using Silverblue
- or a Web/App Developer using local container based development or Fedora CoreOs remotely,
- or an IoT Developer using IoT device
IMHO that story is a bit short. Nevertheless, I need feedback what members of or working group are expecting from the central Fedora website and the Download page.
2 years, 5 months
