I guess as long as you use NAT, you will not be able to bridge. At least that is what I understood since I work with libvirt.
To achieve a network bridge, you need,
Bridged network in virt-manager
To configure bridged network in virt-manager for your virtual machine you must have anetwork bridgeactive on your host machine so make sure your host have an active working bridge network interface configured on your host machine.
(I not tested the tutorial yet…)
@ilikelinux I have all my virtual networks configured each with a virtual bridge and NAT forwarding (e.g., “default” with virbr0, forwarding NAT). Correspondingly, I add it in the VMs with “Virtual network “default”: NAT”. Works properly: Internet works, nwfilter can be put in place, machines can communicate with each other. But the bridge at my config is at another place than yours 
Hi Christopher,
Thanks for your suggestions.
I partly executed the steps that you had mentioned in your earlier messages.
I installed the “virt-manager”. When I open it, I get an authorization message as shown below:
After providing the root authorization, the “virt-manager” window opens, but it doesn’t have any of the VMs created earlier with “gnome-boxes”. The “connection details” in the “virt-manager” looks as shown below.
Now, when I open the VM in “gnome-boxes”, I see that the issue is solved. The VM is getting the IP address in the range “192.168.*” and I’m able to do “ssh” from the host to the VM. I haven’t made any changes to the “xml” file of the VM yet.
But, if the host machine is restarted, and when I open the VM in “gnome-boxes”, the IP address is again back to “10.0.2*”. So, I have to open the “virt-manager” again and provide the root authorization as shown in the above screenshot, before opening the VM in “gnome-boxes”. Please let me know if it’s possible to make the network settings applied by the “virt-manager” (to get the IP address of the VM in the range 192.168.*) as default, so that I don’t have to open the “virt-manager” on every reboot of the host machine.
I will follow the rest of the steps that you told and will get back.
Thanks,
Mallikarjun
I am happy to hear that we found out a way to make the VM work the way you want.
The problem is hopefully-only the VM-specific configuration, where you have to add the default network. Because virt-manager does not use the user-specifc directories, it seems you will have to adjust the xml file manually as described above (see my post above; add the line <source network="default"/>; of course do not use the network name network1 as I did above but default, as you have it in virt-manager). Then reboot (don’t restart just the service with systemctl, we want to see if it works that way on itself).
Unfortunately, I assume the issue is that the virtual network is not initialized before virt-manager is started because the virtual network config is not in the user-specific directory (and I think it cannot be used there, but feel free to try). libvirtd.service seems to be not started by gnome-boxes on the user level (I didn’t know this even works). But after virt-manager has initialized it, gnome-boxes can use it as well because the network then keeps active in libvirt until reboot. So, just in case that the reboot-problem remains:
default.xml in both /etc/libvirt/ and in ~/.config/. I assume it is in /etc/libvirt/qemu/networks 
ip address: Do you now see an interface called virbr0? If not, try ip address again after you opened virt-manager to initialize the network using its own config with libvirtd: Do you see it know? Also, what is the output of systemctl status libvirtd.service before and after starting virt-manager?How to solve the issue if adding the <source network="default"/> line does not work?
I played a bit with it (I’m interested in the approach : ) and found out that gnome-boxes can work on the user level because it does not work with libvirtd.service but only with virtqemud.service directly. I have never worked that way before but this service seems to enable gnome-boxes to do some virtualization tasks with user privileges instead of root (its a module offering just some of libvirtd’s capabilities). But this may be also the reason why it is not able to set up/start virtual networks. As far as I know, this needs to be done with libvirtd.service (I don’t know if there is another module for that, or if that works with user privileges).
So, as we have already set up the virtual network with virt-manager (which did it through libvirtd.service), we hopefully just need to start libvirtd.service on boot by default when your system boots. Thus, try: systemctl enable libvirtd.service and then reboot. After this, I think the virtual network will be started automatically on boot. Let me know if it then works automatically on boot. I’m now curious myself 
Hi Christopher,
The file “/etc/libvirt/qemu/networks/default.xml” exists. As you mentioned, probably, this is the “xml” file of the virtual network created by “virt-manager”. Please take a look at the below screenshot.
I will try out the rest of the suggestions you gave, and will get back to you soon.
Thanks,
Mallikarjun
You have to add your user to the group libvirt. So you don’t need to use the root/sudo password.
Would be a possibility to facilitate access to virt-manager, especially if the current approach will prove to not work, this will make sense. But if he wants to stick with this “user privileges only” gnome-boxes approach, it might make sense to not add privileges to the user he does not need. If (sudo) systemctl enable libvirtd.service works, he won’t need virt-manager or such.
But it has to be clear that the possibilities of this “user privilege gnome-boxes” approach are limited, although libvirtd seems to automatically provide the virtual network to any VM unless it is explicitly configured differently. It seems to even work without the additional line in the VM config, although I would add it to avoid issues (e.g., when another network is created somewhen or so).
@ms-patil
Yes, this is the config of the network. Don’t change it. Just add the source network line to the fedora-unkno.xml file (as described above; “default”, not “network1”) and then, try the systemctl enable libvirtd.service (obviously as root or with sudo) & then reboot thing. I hope that solves the issue after reboot… let us know
@py0xc3 you saw the message in the default.xls that it not should be edited by hand? Using the command virsh net-edit default or an application who uses the libvirt API.
Otherwise the config file will be overwritten!
As mentioned, this is not about the default.xml. I just added the point above to make clear about which file it is. The same message is also in the fedora-unkno.xml but virsh edit is not intended to work in the user directory and thus, I don’t want to create further issues because I don’t know in what this would end. I don’t think the line will make a difference anyway. I just want to exclude it as cause if the approach doesn’t work as anticipated. He has here no automated processes in place, libvirtd and virt-manager definitely work in the /etc/ directory, and gnome-boxes would only make a change if he switches the network interfaces (if he does this with gnome-boxes, the outcome will be the same anyway, so this should be avoided). Hopefully we get this done this time
Hi Christopher,
I tried the commands that you had told in your earlier post. Please find my observations below.
Packages in “virt-manager”
When the “virt-manager” package was installed, few dependencies were also installed. This is the list of packages that got installed.
Here, the package that’s important (from what I have understood) is “libvirt-daemon-config-network”. So, I retained this package and deleted the remaining three.
Executing “sudo systemctl start libvirtd.service” after reboot
After every reboot, I’ve to execute the command “sudo systemctl start libvirtd.service”.
This is the output of the “ip address” command before and after the execution of “sudo systemctl start libvirtd.service”.
Before:
10:53:49 ~ > ip address
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether b4:b5:2f:36:ca:92 brd ff:ff:ff:ff:ff:ff
altname enp1s0
3: wlo1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 74:e5:43:c3:04:5f brd ff:ff:ff:ff:ff:ff
altname wlp2s0
inet 192.168.45.194/24 brd 192.168.45.255 scope global dynamic noprefixroute wlo1
valid_lft 3551sec preferred_lft 3551sec
inet6 2409:4071:2409:c79f:f018:3a9f:b186:f757/64 scope global dynamic noprefixroute
valid_lft 3587sec preferred_lft 3587sec
inet6 fe80::7a45:7d2e:e345:fc8d/64 scope link noprefixroute
valid_lft forever preferred_lft forever
After:
10:58:44 ~ > ip address
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether b4:b5:2f:36:ca:92 brd ff:ff:ff:ff:ff:ff
altname enp1s0
3: wlo1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 74:e5:43:c3:04:5f brd ff:ff:ff:ff:ff:ff
altname wlp2s0
inet 192.168.45.194/24 brd 192.168.45.255 scope global dynamic noprefixroute wlo1
valid_lft 3266sec preferred_lft 3266sec
inet6 2409:4071:2409:c79f:f018:3a9f:b186:f757/64 scope global dynamic noprefixroute
valid_lft 3302sec preferred_lft 3302sec
inet6 fe80::7a45:7d2e:e345:fc8d/64 scope link noprefixroute
valid_lft forever preferred_lft forever
4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 52:54:00:86:64:d2 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
valid_lft forever preferred_lft forever
Here, I have pasted a part of the “xml” file of the virtual machine (containing the “interface” information) before and after the execution of “sudo systemctl start libvirtd.service”. No manual editing to the file is done yet, the “systemctl” command itself is doing these updates in the “xml” file.
This is the IP address of the virtual machine before and after the execution of “sudo systemctl start libvirtd.service”.
Before: 10.0.2.15 (“ssh” from host is not possible)
After: 192.168.122.153 (“ssh” from host is possible)
So, after the execution of “sudo systemctl start libvirtd.service”, the “virbr0” bridge is created, and the VM is taking the right IP address such that “ssh” from the host is possible. Further, if the package “libvirt-daemon-config-network” is not installed, then the “virbr0” bridge is not created.
The “systemctl enable libvirtd.service” command
I had executed the command “sudo systemctl enable libvirtd.service” before reboot of host machine. But, I still have to execute “sudo systemctl start libvirtd.service” after every reboot for the “virbr0” bridge to be created.
Please find the output of “systemctl status libvirtd.service” after reboot of host machine, and before and after the execution of “sudo systemctl start libvirtd.service”.
Before:
10:18:35 ~ > systemctl status libvirtd.service
○ libvirtd.service - Virtualization daemon
Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; disabled; vendor preset: disabled)
Active: inactive (dead)
TriggeredBy: ○ libvirtd-ro.socket
○ libvirtd.socket
○ libvirtd-admin.socket
○ libvirtd-tcp.socket
○ libvirtd-tls.socket
Docs: man:libvirtd(8)
https://libvirt.org
After:
12:20:29 ~ > systemctl status libvirtd.service
● libvirtd.service - Virtualization daemon
Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: disabled)
Active: active (running) since Wed 2022-01-12 12:20:29 IST; 2s ago
TriggeredBy: ○ libvirtd-tls.socket
○ libvirtd-tcp.socket
● libvirtd.socket
● libvirtd-admin.socket
● libvirtd-ro.socket
Docs: man:libvirtd(8)
https://libvirt.org
Main PID: 13864 (libvirtd)
Tasks: 21 (limit: 32768)
Memory: 49.7M
CPU: 649ms
CGroup: /system.slice/libvirtd.service
├─ 2647 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
├─ 2648 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
└─13864 /usr/sbin/libvirtd --timeout 120
Jan 12 12:20:27 fedora systemd[1]: libvirtd.service: Found left-over process 2647 (dnsmasq) in control group while starting unit. Ignoring.
Jan 12 12:20:27 fedora systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Jan 12 12:20:27 fedora systemd[1]: libvirtd.service: Found left-over process 2648 (dnsmasq) in control group while starting unit. Ignoring.
Jan 12 12:20:27 fedora systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Jan 12 12:20:27 fedora systemd[1]: Starting Virtualization daemon…
Jan 12 12:20:29 fedora systemd[1]: Started Virtualization daemon.
Jan 12 12:20:30 fedora dnsmasq[2647]: read /etc/hosts - 2 addresses
Jan 12 12:20:30 fedora dnsmasq[2647]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
Jan 12 12:20:30 fedora dnsmasq-dhcp[2647]: read /var/lib/libvirt/dnsmasq/default.hostsfile
So, the “libvirtd.service” is not started by default on every reboot, and I’ve to start it using “sudo systemctl start libvirtd.service”.
Thanks,
Mallikarjun
Interesting, libvirtd is adding temporary lines within the user dir if required values are not set although it works in and uses itself the /etc/ configs. Magic!
It is strange that sudo systemctl start libvirtd.service works but sudo systemctl enable libvirtd.service does not.
With the left-over in the logs, it looks like the service starts at boot but then crashes, although it can be re-started with systemctl start.
Just to check all possibilities: Is there any output of sudo systemctl enable libvirtd.service?
With libvirtd.service enabled, reboot and let us know the rough boot time. Then, what is the output of sudo journalctl -u libvirtd.service ? This shows us all logs related to the libvirtd service.
Hi Christopher,
With the “libvritd.service” enabled, the boot time is around 1.5 minutes.
Please find below, the logs of “libvirtd.service” from the “journalctl” command.
– Journal begins at Tue 2022-01-11 08:57:54 IST, ends at Wed 2022-01-12 18:04:19 IST. –
Jan 11 10:44:55 fedora systemd[1]: Starting Virtualization daemon…
Jan 11 10:44:55 fedora systemd[1]: Started Virtualization daemon.
Jan 11 10:46:56 fedora systemd[1]: libvirtd.service: Deactivated successfully.
– Boot 8a9b2dd1275141ab92838a8480e00b1b –
Jan 12 10:27:58 fedora systemd[1]: Starting Virtualization daemon…
Jan 12 10:27:58 fedora systemd[1]: Started Virtualization daemon.
Jan 12 10:28:23 fedora systemd[1]: Stopping Virtualization daemon…
Jan 12 10:28:23 fedora systemd[1]: libvirtd.service: Deactivated successfully.
Jan 12 10:28:23 fedora systemd[1]: Stopped Virtualization daemon.
– Boot 07a0699ddae042d396754c21f44e02c0 –
Jan 12 10:31:40 fedora systemd[1]: Starting Virtualization daemon…
Jan 12 10:31:40 fedora systemd[1]: Started Virtualization daemon.
Jan 12 10:31:41 fedora dnsmasq[2849]: started, version 2.86 cachesize 150
Jan 12 10:31:41 fedora dnsmasq[2849]: compile time options: IPv6 GNU-getopt DBus no-UBus no-i18n IDN2 DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth cryptohash DNSSEC loop-detect inotify dumpfile
Jan 12 10:31:41 fedora dnsmasq-dhcp[2849]: DHCP, IP range 192.168.122.2 – 192.168.122.254, lease time 1h
Jan 12 10:31:41 fedora dnsmasq-dhcp[2849]: DHCP, sockets bound exclusively to interface virbr0
Jan 12 10:31:41 fedora dnsmasq[2849]: reading /etc/resolv.conf
Jan 12 10:31:41 fedora dnsmasq[2849]: using nameserver 127.0.0.53#53
Jan 12 10:31:41 fedora dnsmasq[2849]: read /etc/hosts - 2 addresses
Jan 12 10:31:41 fedora dnsmasq[2849]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
Jan 12 10:31:41 fedora dnsmasq-dhcp[2849]: read /var/lib/libvirt/dnsmasq/default.hostsfile
Jan 12 10:33:06 fedora systemd[1]: Stopping Virtualization daemon…
Jan 12 10:33:07 fedora systemd[1]: libvirtd.service: Deactivated successfully.
Jan 12 10:33:07 fedora systemd[1]: libvirtd.service: Unit process 2849 (dnsmasq) remains running after unit stopped.
Jan 12 10:33:07 fedora systemd[1]: libvirtd.service: Unit process 2850 (dnsmasq) remains running after unit stopped.
Jan 12 10:33:07 fedora systemd[1]: Stopped Virtualization daemon.
– Boot 8d485da301784519ba4b0a44f147dcf9 –
Jan 12 10:35:38 fedora systemd[1]: Starting Virtualization daemon…
Jan 12 10:35:39 fedora systemd[1]: Started Virtualization daemon.
Jan 12 10:36:04 fedora systemd[1]: Stopping Virtualization daemon…
Jan 12 10:36:04 fedora systemd[1]: libvirtd.service: Deactivated successfully.
Jan 12 10:36:04 fedora systemd[1]: Stopped Virtualization daemon.
Jan 12 10:37:28 fedora systemd[1]: Starting Virtualization daemon…
Jan 12 10:37:28 fedora systemd[1]: Started Virtualization daemon.
Jan 12 10:37:42 fedora systemd[1]: Stopping Virtualization daemon…
Jan 12 10:37:42 fedora systemd[1]: libvirtd.service: Deactivated successfully.
Jan 12 10:37:42 fedora systemd[1]: Stopped Virtualization daemon.
– Boot 63d1a18e8e144ce488a045eda0d9b3ed –
Jan 12 10:39:22 fedora systemd[1]: Starting Virtualization daemon…
Jan 12 10:39:23 fedora systemd[1]: Started Virtualization daemon.
Jan 12 10:39:24 fedora dnsmasq[2614]: started, version 2.86 cachesize 150
Jan 12 10:39:24 fedora dnsmasq[2614]: compile time options: IPv6 GNU-getopt DBus no-UBus no-i18n IDN2 DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth cryptohash DNSSEC loop-detect inotify dumpfile
Jan 12 10:39:24 fedora dnsmasq-dhcp[2614]: DHCP, IP range 192.168.122.2 – 192.168.122.254, lease time 1h
Jan 12 10:39:24 fedora dnsmasq-dhcp[2614]: DHCP, sockets bound exclusively to interface virbr0
Jan 12 10:39:24 fedora dnsmasq[2614]: reading /etc/resolv.conf
Jan 12 10:39:24 fedora dnsmasq[2614]: using nameserver 127.0.0.53#53
Jan 12 10:39:24 fedora dnsmasq[2614]: read /etc/hosts - 2 addresses
Jan 12 10:39:24 fedora dnsmasq[2614]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
Jan 12 10:39:24 fedora dnsmasq-dhcp[2614]: read /var/lib/libvirt/dnsmasq/default.hostsfile
Jan 12 10:41:14 fedora systemd[1]: Stopping Virtualization daemon…
Jan 12 10:41:14 fedora systemd[1]: libvirtd.service: Deactivated successfully.
Jan 12 10:41:14 fedora systemd[1]: libvirtd.service: Unit process 2614 (dnsmasq) remains running after unit stopped.
Jan 12 10:41:14 fedora systemd[1]: libvirtd.service: Unit process 2615 (dnsmasq) remains running after unit stopped.
Jan 12 10:41:14 fedora systemd[1]: Stopped Virtualization daemon.
– Boot 4a09749861ec47f7b70be837d0e79a2d –
Jan 12 10:43:02 fedora systemd[1]: Starting Virtualization daemon…
Jan 12 10:43:03 fedora systemd[1]: Started Virtualization daemon.
Jan 12 10:43:04 fedora dnsmasq[3062]: started, version 2.86 cachesize 150
Jan 12 10:43:04 fedora dnsmasq[3062]: compile time options: IPv6 GNU-getopt DBus no-UBus no-i18n IDN2 DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth cryptohash DNSSEC loop-detect inotify dumpfile
Jan 12 10:43:04 fedora dnsmasq-dhcp[3062]: DHCP, IP range 192.168.122.2 – 192.168.122.254, lease time 1h
Jan 12 10:43:04 fedora dnsmasq-dhcp[3062]: DHCP, sockets bound exclusively to interface virbr0
Jan 12 10:43:04 fedora dnsmasq[3062]: reading /etc/resolv.conf
Jan 12 10:43:04 fedora dnsmasq[3062]: using nameserver 127.0.0.53#53
Jan 12 10:43:04 fedora dnsmasq[3062]: read /etc/hosts - 2 addresses
Jan 12 10:43:04 fedora dnsmasq[3062]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
Jan 12 10:43:04 fedora dnsmasq-dhcp[3062]: read /var/lib/libvirt/dnsmasq/default.hostsfile
Jan 12 10:43:16 fedora systemd[1]: Stopping Virtualization daemon…
Jan 12 10:43:16 fedora systemd[1]: libvirtd.service: Deactivated successfully.
Jan 12 10:43:16 fedora systemd[1]: libvirtd.service: Unit process 3062 (dnsmasq) remains running after unit stopped.
Jan 12 10:43:16 fedora systemd[1]: libvirtd.service: Unit process 3063 (dnsmasq) remains running after unit stopped.
Jan 12 10:43:16 fedora systemd[1]: Stopped Virtualization daemon.
Jan 12 10:44:31 fedora dnsmasq-dhcp[3062]: DHCPDISCOVER(virbr0) 52:54:00:f9:81:4f
Jan 12 10:44:31 fedora dnsmasq-dhcp[3062]: DHCPOFFER(virbr0) 192.168.122.113 52:54:00:f9:81:4f
Jan 12 10:44:31 fedora dnsmasq-dhcp[3062]: DHCPDISCOVER(virbr0) 52:54:00:f9:81:4f
Jan 12 10:44:31 fedora dnsmasq-dhcp[3062]: DHCPOFFER(virbr0) 192.168.122.113 52:54:00:f9:81:4f
Jan 12 10:44:31 fedora dnsmasq-dhcp[3062]: DHCPREQUEST(virbr0) 192.168.122.113 52:54:00:f9:81:4f
Jan 12 10:44:31 fedora dnsmasq-dhcp[3062]: DHCPACK(virbr0) 192.168.122.113 52:54:00:f9:81:4f
– Boot 24cfe3293d5d49caa67aea0be131ba8d –
Jan 12 10:49:02 fedora systemd[1]: Starting Virtualization daemon…
Jan 12 10:49:03 fedora systemd[1]: Started Virtualization daemon.
Jan 12 10:49:34 fedora systemd[1]: Stopping Virtualization daemon…
Jan 12 10:49:34 fedora systemd[1]: libvirtd.service: Deactivated successfully.
Jan 12 10:49:34 fedora systemd[1]: Stopped Virtualization daemon.
Jan 12 10:49:34 fedora systemd[1]: Starting Virtualization daemon…
Jan 12 10:49:34 fedora systemd[1]: Started Virtualization daemon.
Jan 12 10:49:39 fedora systemd[1]: Stopping Virtualization daemon…
Jan 12 10:49:39 fedora systemd[1]: libvirtd.service: Deactivated successfully.
Jan 12 10:49:39 fedora systemd[1]: Stopped Virtualization daemon.
– Boot 07b9346c2f35444f8f35a761fed9a620 –
Jan 12 10:51:27 fedora systemd[1]: Starting Virtualization daemon…
Jan 12 10:51:27 fedora systemd[1]: Started Virtualization daemon.
Jan 12 10:51:28 fedora dnsmasq[2613]: started, version 2.86 cachesize 150
Jan 12 10:51:28 fedora dnsmasq[2613]: compile time options: IPv6 GNU-getopt DBus no-UBus no-i18n IDN2 DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth cryptohash DNSSEC loop-detect inotify dumpfile
Jan 12 10:51:28 fedora dnsmasq-dhcp[2613]: DHCP, IP range 192.168.122.2 – 192.168.122.254, lease time 1h
Jan 12 10:51:28 fedora dnsmasq-dhcp[2613]: DHCP, sockets bound exclusively to interface virbr0
Jan 12 10:51:28 fedora dnsmasq[2613]: reading /etc/resolv.conf
Jan 12 10:51:28 fedora dnsmasq[2613]: using nameserver 127.0.0.53#53
Jan 12 10:51:28 fedora dnsmasq[2613]: read /etc/hosts - 2 addresses
Jan 12 10:51:28 fedora dnsmasq[2613]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
Jan 12 10:51:28 fedora dnsmasq-dhcp[2613]: read /var/lib/libvirt/dnsmasq/default.hostsfile
Jan 12 10:52:13 fedora systemd[1]: Stopping Virtualization daemon…
Jan 12 10:52:13 fedora systemd[1]: libvirtd.service: Deactivated successfully.
Jan 12 10:52:13 fedora systemd[1]: libvirtd.service: Unit process 2613 (dnsmasq) remains running after unit stopped.
Jan 12 10:52:13 fedora systemd[1]: libvirtd.service: Unit process 2614 (dnsmasq) remains running after unit stopped.
Jan 12 10:52:13 fedora systemd[1]: Stopped Virtualization daemon.
– Boot bb7abae69a244d3b8425704d75a8676b –
Jan 12 10:58:44 fedora systemd[1]: Starting Virtualization daemon…
Jan 12 10:58:44 fedora systemd[1]: Started Virtualization daemon.
Jan 12 10:58:45 fedora dnsmasq[3703]: started, version 2.86 cachesize 150
Jan 12 10:58:45 fedora dnsmasq[3703]: compile time options: IPv6 GNU-getopt DBus no-UBus no-i18n IDN2 DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth cryptohash DNSSEC loop-detect inotify dumpfile
Jan 12 10:58:45 fedora dnsmasq-dhcp[3703]: DHCP, IP range 192.168.122.2 – 192.168.122.254, lease time 1h
Jan 12 10:58:45 fedora dnsmasq-dhcp[3703]: DHCP, sockets bound exclusively to interface virbr0
Jan 12 10:58:45 fedora dnsmasq[3703]: reading /etc/resolv.conf
Jan 12 10:58:45 fedora dnsmasq[3703]: using nameserver 127.0.0.53#53
Jan 12 10:58:45 fedora dnsmasq[3703]: read /etc/hosts - 2 addresses
Jan 12 10:58:45 fedora dnsmasq[3703]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
Jan 12 10:58:45 fedora dnsmasq-dhcp[3703]: read /var/lib/libvirt/dnsmasq/default.hostsfile
Jan 12 10:59:41 fedora systemd[1]: Stopping Virtualization daemon…
Jan 12 10:59:41 fedora systemd[1]: libvirtd.service: Deactivated successfully.
Jan 12 10:59:41 fedora systemd[1]: libvirtd.service: Unit process 3703 (dnsmasq) remains running after unit stopped.
Jan 12 10:59:41 fedora systemd[1]: libvirtd.service: Unit process 3704 (dnsmasq) remains running after unit stopped.
Jan 12 10:59:41 fedora systemd[1]: Stopped Virtualization daemon.
Jan 12 11:00:34 fedora dnsmasq-dhcp[3703]: DHCPDISCOVER(virbr0) 52:54:00:97:03:f9
Jan 12 11:00:34 fedora dnsmasq-dhcp[3703]: DHCPOFFER(virbr0) 192.168.122.153 52:54:00:97:03:f9
Jan 12 11:00:34 fedora dnsmasq-dhcp[3703]: DHCPDISCOVER(virbr0) 52:54:00:97:03:f9
Jan 12 11:00:34 fedora dnsmasq-dhcp[3703]: DHCPOFFER(virbr0) 192.168.122.153 52:54:00:97:03:f9
Jan 12 11:00:34 fedora dnsmasq-dhcp[3703]: DHCPREQUEST(virbr0) 192.168.122.153 52:54:00:97:03:f9
Jan 12 11:00:34 fedora dnsmasq-dhcp[3703]: DHCPACK(virbr0) 192.168.122.153 52:54:00:97:03:f9
Jan 12 11:02:33 fedora dnsmasq-dhcp[3703]: DHCPREQUEST(virbr0) 192.168.122.153 52:54:00:97:03:f9
Jan 12 11:02:33 fedora dnsmasq-dhcp[3703]: DHCPACK(virbr0) 192.168.122.153 52:54:00:97:03:f9
– Boot 7470d0f59ffb4b44ac7897eecfbb2bbd –
Jan 12 11:12:01 fedora systemd[1]: Starting Virtualization daemon…
Jan 12 11:12:01 fedora systemd[1]: Started Virtualization daemon.
Jan 12 11:12:02 fedora dnsmasq[2647]: started, version 2.86 cachesize 150
Jan 12 11:12:02 fedora dnsmasq[2647]: compile time options: IPv6 GNU-getopt DBus no-UBus no-i18n IDN2 DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth cryptohash DNSSEC loop-detect inotify dumpfile
Jan 12 11:12:02 fedora dnsmasq-dhcp[2647]: DHCP, IP range 192.168.122.2 – 192.168.122.254, lease time 1h
Jan 12 11:12:02 fedora dnsmasq-dhcp[2647]: DHCP, sockets bound exclusively to interface virbr0
Jan 12 11:12:02 fedora dnsmasq[2647]: reading /etc/resolv.conf
Jan 12 11:12:02 fedora dnsmasq[2647]: using nameserver 127.0.0.53#53
Jan 12 11:12:02 fedora dnsmasq[2647]: read /etc/hosts - 2 addresses
Jan 12 11:12:02 fedora dnsmasq[2647]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
Jan 12 11:12:02 fedora dnsmasq-dhcp[2647]: read /var/lib/libvirt/dnsmasq/default.hostsfile
Jan 12 11:12:05 fedora systemd[1]: Stopping Virtualization daemon…
Jan 12 11:12:05 fedora systemd[1]: libvirtd.service: Deactivated successfully.
Jan 12 11:12:05 fedora systemd[1]: libvirtd.service: Unit process 2647 (dnsmasq) remains running after unit stopped.
Jan 12 11:12:05 fedora systemd[1]: libvirtd.service: Unit process 2648 (dnsmasq) remains running after unit stopped.
Jan 12 11:12:05 fedora systemd[1]: Stopped Virtualization daemon.
Jan 12 11:12:51 fedora dnsmasq-dhcp[2647]: DHCPREQUEST(virbr0) 192.168.122.153 52:54:00:97:03:f9
Jan 12 11:12:51 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.153 52:54:00:97:03:f9
Jan 12 11:16:12 fedora dnsmasq-dhcp[2647]: DHCPDISCOVER(virbr0) 52:54:00:1c:c5:8a
Jan 12 11:16:12 fedora dnsmasq-dhcp[2647]: DHCPOFFER(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 11:16:14 fedora dnsmasq-dhcp[2647]: DHCPDISCOVER(virbr0) 52:54:00:1c:c5:8a
Jan 12 11:16:14 fedora dnsmasq-dhcp[2647]: DHCPOFFER(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 11:16:14 fedora dnsmasq-dhcp[2647]: DHCPREQUEST(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 11:16:14 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 11:16:28 fedora dnsmasq-dhcp[2647]: DHCPINFORM(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 11:16:28 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 11:19:12 fedora dnsmasq-dhcp[2647]: DHCPINFORM(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 11:19:12 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 11:20:25 fedora dnsmasq-dhcp[2647]: DHCPINFORM(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 11:20:25 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 11:24:14 fedora dnsmasq-dhcp[2647]: DHCPINFORM(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 11:24:14 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 11:25:18 fedora dnsmasq-dhcp[2647]: DHCPINFORM(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 11:25:18 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 11:31:09 fedora dnsmasq-dhcp[2647]: DHCPINFORM(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 11:31:09 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 11:32:41 fedora dnsmasq-dhcp[2647]: DHCPINFORM(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 11:32:41 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 11:35:57 fedora dnsmasq-dhcp[2647]: DHCPINFORM(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 11:35:57 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 11:37:46 fedora dnsmasq-dhcp[2647]: DHCPINFORM(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 11:37:46 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 11:41:23 fedora dnsmasq-dhcp[2647]: DHCPINFORM(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 11:41:23 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 11:44:49 fedora dnsmasq-dhcp[2647]: DHCPINFORM(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 11:44:49 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 11:46:14 fedora dnsmasq-dhcp[2647]: DHCPREQUEST(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 11:46:14 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 11:46:21 fedora dnsmasq-dhcp[2647]: DHCPINFORM(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 11:46:21 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 12:13:53 fedora dnsmasq-dhcp[2647]: DHCPREQUEST(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 12:13:53 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 12:15:28 fedora dnsmasq-dhcp[2647]: DHCPINFORM(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 12:15:28 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 12:20:27 fedora systemd[1]: libvirtd.service: Found left-over process 2647 (dnsmasq) in control group while starting unit. Ignoring.
Jan 12 12:20:27 fedora systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Jan 12 12:20:27 fedora systemd[1]: libvirtd.service: Found left-over process 2648 (dnsmasq) in control group while starting unit. Ignoring.
Jan 12 12:20:27 fedora systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Jan 12 12:20:27 fedora systemd[1]: Starting Virtualization daemon…
Jan 12 12:20:29 fedora systemd[1]: Started Virtualization daemon.
Jan 12 12:20:30 fedora dnsmasq[2647]: read /etc/hosts - 2 addresses
Jan 12 12:20:30 fedora dnsmasq[2647]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
Jan 12 12:20:30 fedora dnsmasq-dhcp[2647]: read /var/lib/libvirt/dnsmasq/default.hostsfile
Jan 12 12:22:29 fedora systemd[1]: libvirtd.service: Deactivated successfully.
Jan 12 12:22:29 fedora systemd[1]: libvirtd.service: Unit process 2647 (dnsmasq) remains running after unit stopped.
Jan 12 12:22:29 fedora systemd[1]: libvirtd.service: Unit process 2648 (dnsmasq) remains running after unit stopped.
Jan 12 12:40:32 fedora dnsmasq-dhcp[2647]: DHCPREQUEST(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 12:40:32 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 12:46:24 fedora dnsmasq-dhcp[2647]: DHCPINFORM(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 12:46:24 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 12:48:49 fedora dnsmasq-dhcp[2647]: DHCPINFORM(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 12:48:49 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 13:07:35 fedora dnsmasq-dhcp[2647]: DHCPREQUEST(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 13:07:35 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 13:16:25 fedora dnsmasq-dhcp[2647]: DHCPINFORM(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 13:16:25 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 13:35:23 fedora dnsmasq-dhcp[2647]: DHCPREQUEST(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 13:35:23 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 13:46:26 fedora dnsmasq-dhcp[2647]: DHCPINFORM(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 13:46:26 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 14:02:07 fedora dnsmasq-dhcp[2647]: DHCPREQUEST(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 14:02:07 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 14:16:28 fedora dnsmasq-dhcp[2647]: DHCPINFORM(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 14:16:28 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 14:29:25 fedora dnsmasq-dhcp[2647]: DHCPINFORM(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 14:29:25 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 14:29:36 fedora dnsmasq-dhcp[2647]: DHCPREQUEST(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 14:29:36 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 14:39:53 fedora dnsmasq-dhcp[2647]: DHCPINFORM(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 14:39:53 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 14:41:17 fedora dnsmasq-dhcp[2647]: DHCPINFORM(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 14:41:17 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 14:46:24 fedora dnsmasq-dhcp[2647]: DHCPINFORM(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 14:46:24 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 14:56:57 fedora dnsmasq-dhcp[2647]: DHCPREQUEST(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 14:56:57 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 15:16:29 fedora dnsmasq-dhcp[2647]: DHCPINFORM(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 15:16:29 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 15:24:02 fedora dnsmasq-dhcp[2647]: DHCPREQUEST(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 15:24:02 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 15:46:31 fedora dnsmasq-dhcp[2647]: DHCPINFORM(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 15:46:31 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 15:51:04 fedora dnsmasq-dhcp[2647]: DHCPREQUEST(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 15:51:04 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 16:16:32 fedora dnsmasq-dhcp[2647]: DHCPINFORM(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 16:16:32 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 16:18:34 fedora dnsmasq-dhcp[2647]: DHCPREQUEST(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 16:18:34 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 16:46:14 fedora dnsmasq-dhcp[2647]: DHCPREQUEST(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 16:46:14 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 16:46:33 fedora dnsmasq-dhcp[2647]: DHCPINFORM(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 16:46:33 fedora dnsmasq-dhcp[2647]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
The command “systemctl enable libvirtd.service” is not giving any output. But, it had given some output the very first time I had executed it. It had created some symbolic links.
Please let me know if you need any details.
Thanks,
Mallikarjun
@ms-patil I meant the time when u booted So, e.g. Jan 12 16:46:14, so that I know where to look in the logs for the current boot and the behavior of libvirt at that time around. But its ok, boots are marked anyway.
Concerning the output, that is ok. It is enabled. The symlinks are intended.
Hi Christopher,
I booted sometime around 1800 today. Please find the journal logs below.
– Boot 864c60d389c94c19a824c4d6448f6472 –
Jan 12 18:10:30 fedora systemd[1]: Starting Virtualization daemon…
Jan 12 18:10:31 fedora systemd[1]: Started Virtualization daemon.
Jan 12 18:10:31 fedora dnsmasq[3256]: started, version 2.86 cachesize 150
Jan 12 18:10:31 fedora dnsmasq[3256]: compile time options: IPv6 GNU-getopt DBus no-UBus no-i18n IDN2 DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth cryptohash DNSSEC>
Jan 12 18:10:31 fedora dnsmasq-dhcp[3256]: DHCP, IP range 192.168.122.2 – 192.168.122.254, lease time 1h
Jan 12 18:10:31 fedora dnsmasq-dhcp[3256]: DHCP, sockets bound exclusively to interface virbr0
Jan 12 18:10:31 fedora dnsmasq[3256]: reading /etc/resolv.conf
Jan 12 18:10:31 fedora dnsmasq[3256]: using nameserver 127.0.0.53#53
Jan 12 18:10:31 fedora dnsmasq[3256]: read /etc/hosts - 2 addresses
Jan 12 18:10:31 fedora dnsmasq[3256]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
Jan 12 18:10:31 fedora dnsmasq-dhcp[3256]: read /var/lib/libvirt/dnsmasq/default.hostsfile
Jan 12 18:10:39 fedora systemd[1]: Stopping Virtualization daemon…
Jan 12 18:10:39 fedora systemd[1]: libvirtd.service: Deactivated successfully.
Jan 12 18:10:39 fedora systemd[1]: libvirtd.service: Unit process 3256 (dnsmasq) remains running after unit stopped.
Jan 12 18:10:39 fedora systemd[1]: libvirtd.service: Unit process 3257 (dnsmasq) remains running after unit stopped.
Jan 12 18:10:39 fedora systemd[1]: Stopped Virtualization daemon.
Jan 12 18:12:41 fedora dnsmasq-dhcp[3256]: DHCPDISCOVER(virbr0) 52:54:00:1c:c5:8a
Jan 12 18:12:41 fedora dnsmasq-dhcp[3256]: DHCPOFFER(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 18:12:41 fedora dnsmasq-dhcp[3256]: DHCPDISCOVER(virbr0) 52:54:00:1c:c5:8a
Jan 12 18:12:41 fedora dnsmasq-dhcp[3256]: DHCPOFFER(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 18:12:49 fedora dnsmasq-dhcp[3256]: DHCPDISCOVER(virbr0) 52:54:00:1c:c5:8a
Jan 12 18:12:49 fedora dnsmasq-dhcp[3256]: DHCPOFFER(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 18:12:49 fedora dnsmasq-dhcp[3256]: DHCPREQUEST(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 18:12:49 fedora dnsmasq-dhcp[3256]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 18:13:03 fedora dnsmasq-dhcp[3256]: DHCPINFORM(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 18:13:03 fedora dnsmasq-dhcp[3256]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 18:14:04 fedora dnsmasq-dhcp[3256]: DHCPINFORM(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 18:14:04 fedora dnsmasq-dhcp[3256]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 18:17:36 fedora dnsmasq-dhcp[3256]: DHCPINFORM(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 18:17:36 fedora dnsmasq-dhcp[3256]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 18:22:44 fedora dnsmasq-dhcp[3256]: DHCPINFORM(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 18:22:44 fedora dnsmasq-dhcp[3256]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 18:42:50 fedora dnsmasq-dhcp[3256]: DHCPREQUEST(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 18:42:50 fedora dnsmasq-dhcp[3256]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
Jan 12 18:43:46 fedora dnsmasq-dhcp[3256]: DHCPINFORM(virbr0) 192.168.122.119 52:54:00:1c:c5:8a
Jan 12 18:43:46 fedora dnsmasq-dhcp[3256]: DHCPACK(virbr0) 192.168.122.119 52:54:00:1c:c5:8a mspatil
lines 245-281/281 (END)
Thanks,
Mallikarjun
@ms-patil it seems that Fedora 35 native installations are no longer intended to use the “monolithic” libvirtd, which is why it gets deactivated after boot.
You have to use the modular daemon for the network. So disable libvirtd with systemctl disable libvirtd.service
Now, enable the modular daemon: systemctl enable virtnetworkd.service.
Does it now work after reboot? 
Hi Christopher,
I executed the two commands you told.
19:18:46 ~ > sudo systemctl disable libvirtd.service
[sudo] password for ms.patil:
Removed /etc/systemd/system/multi-user.target.wants/libvirtd.service.
Removed /etc/systemd/system/sockets.target.wants/virtlockd.socket.
Removed /etc/systemd/system/sockets.target.wants/virtlogd.socket.
Removed /etc/systemd/system/sockets.target.wants/libvirtd.socket.
Removed /etc/systemd/system/sockets.target.wants/libvirtd-ro.socket.
[2]+ Done gnome-boxes -f > /dev/null 2>&1
19:33:47 ~ > sudo systemctl enable virtnetworkd.service
Created symlink /etc/systemd/system/multi-user.target.wants/virtnetworkd.service → /usr/lib/systemd/system/virtnetworkd.service.
Created symlink /etc/systemd/system/sockets.target.wants/virtnetworkd-ro.socket → /usr/lib/systemd/system/virtnetworkd-ro.socket.
Created symlink /etc/systemd/system/sockets.target.wants/virtnetworkd-admin.socket → /usr/lib/systemd/system/virtnetworkd-admin.socket.
Then, I rebooted my computer. I see that the “virbr0” bridge is created by default as shown by the output of the “ip address” command.
19:37:35 ~ > ip address
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether b4:b5:2f:36:ca:92 brd ff:ff:ff:ff:ff:ff
altname enp1s0
3: wlo1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 74:e5:43:c3:04:5f brd ff:ff:ff:ff:ff:ff
altname wlp2s0
inet 192.168.45.194/24 brd 192.168.45.255 scope global dynamic noprefixroute wlo1
valid_lft 3559sec preferred_lft 3559sec
inet6 2409:4071:2409:c79f:f018:3a9f:b186:f757/64 scope global dynamic noprefixroute
valid_lft 3562sec preferred_lft 3562sec
inet6 fe80::7a45:7d2e:e345:fc8d/64 scope link noprefixroute
valid_lft forever preferred_lft forever
4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 52:54:00:86:64:d2 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
valid_lft forever preferred_lft forever
The VM also gets the IP address in the range 192.168* as shown by the output of “ifconfig” in the VM. So, I can do “ssh” from host to VM now.
19:40:48 ~ > ifconfig
enp1s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.122.153 netmask 255.255.255.0 broadcast 192.168.122.255
inet6 fe80::137d:5d80:68fa:693d prefixlen 64 scopeid 0x20
ether 52:54:00:97:03:f9 txqueuelen 1000 (Ethernet)
RX packets 190 bytes 20979 (20.4 KiB)
RX errors 0 dropped 84 overruns 0 frame 0
TX packets 112 bytes 11611 (11.3 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Local Loopback)
RX packets 31 bytes 3288 (3.2 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 31 bytes 3288 (3.2 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
I guess, this solves the issue? I hope so. Thanks a lot for your suggestions.
Thanks,
Mallikarjun
@ms-patil Great! Finally we did it. But as this thread has become very complex, it would be good if you mark the post that solved your original ssh-connection issue as solution. This will help others with the same problem.
Theoretically, you could also remove the virtual network because you now use the bridge directly at the VM, without a virtual network in between. But it is no (security/performance) issue to keep it as it is: the current configuraiton is fine (and working : )
Yeah, that’s great! We solved this problem.
I have marked your earlier post where you suggested to use the command “sudo systemctl enable virtnetworkd.service” as the solution to the issue.
Thanks a lot for your time and your suggestions.
Mallikarjun
Hi Christopher,
I forgot to mention that the package “libvirt-daemon-config-network” would be required, otherwise the issue will not solve.
So, I’m summarizing the two step solution below:
Thanks,
Mallikarjun
