Arch Linux

Description:

I have performed an update and libvirt no longer starts. Libvirt was updated from 4.7.0-1 to 4.8.0-1. I have a text file attached that shows everything that was updated and some information about the error.

The following shows the error:

[user@computername ~]$ systemctl status libvirtd
● libvirtd.service - Virtualization daemon
Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2018-10-18 21:40:54 EDT; 3min 25s ago
Docs: man:libvirtd(8)
https://libvirt.org
Process: 3323 ExecStart=/usr/bin/libvirtd $LIBVIRTD_ARGS (code=exited, status=3)
Main PID: 3323 (code=exited, status=3)

Oct 18 21:40:54 computername systemd[1]: libvirtd.service: Service RestartSec=100ms expired, scheduling restart.
Oct 18 21:40:54 computername systemd[1]: libvirtd.service: Scheduled restart job, restart counter is at 5.
Oct 18 21:40:54 computername systemd[1]: Stopped Virtualization daemon.
Oct 18 21:40:54 computername systemd[1]: libvirtd.service: Start request repeated too quickly.
Oct 18 21:40:54 computername systemd[1]: libvirtd.service: Failed with result 'exit-code'.
Oct 18 21:40:54 computername systemd[1]: Failed to start Virtualization daemon.
[user@computername ~]$

During the install pacman showed that default.xml.pacnew was written to the filesystem, I ran the following in order to add the newfile:

sudo mv /etc/libvirt/qemu/networks/default.xml.pacnew /etc/libvirt/qemu/networks/default.xml


The default.xml file appears as the following:

<network>
<name>default</name>
<uuid>b3b5e138-6901-2b78-a089-794a3451a141</uuid>
<bridge name="virbr0"/>
<forward/>
<ip address="192.168.122.1" netmask="255.255.255.0">
<dhcp>
<range start="192.168.122.2" end="192.168.122.254"/>
</dhcp>
</ip>
</network>


Steps to reproduce:

Update libvirt from 4.7.0-1 to 4.8.0-1 and start service.