virt-manager NAT networks inactive on system boot

[ilvipero]

Hello,
I am using libvirt-kvm and virt-manager on my opensuse tumbleweed desktops and I noticed an issue.

All virtual networks created via virt-manager and configured to be active at boot, do not actually come up when I boot the computers. Those remain defined in virt-manager but are not active, unless i manually go and turn them to active. This is on my 2 desktop system, both on KDE plasma and both using networkmanager network service.
If I use the command “sudo virsh net-list” on boot, list turns out empty. If I manually start the NAT networks from virt-manager and re run “sudo virsh net-list”, the networks show up as active persistent and autostart.

Interesting enough, if I do the same on a 3rd openSUSE tumbleweed box, that is a headless server, no gui and using wicked network service, NAT networks do come up on system boot as expected.

Is there anyone that can help me troubleshoot the issue and fix it on the desktops that run KDE plasma and networkmanager?

[tsu2]

Ok,
Took me awhile to work my way through the issues…

First,
I suspect you may have installed your Hypervisor and Tools during your initial install…
On a whim I did this (which I have always heavily criticized) to review what happens…
Which produced the problem described…
libvirtd fails to start on boot.
libvirtd can be started manually, but on close inspection is only partially functional.
KVM kernel modules built and working which can be viewed by running dmesg or journalctl -b.

The first issue I ran into is that there is a libvirtd issue where it will fail connecting to libnetcontrol if you’re running Network Manager.
Since Network Manager is enabled by default in 15.1,
So, that’s the first issue… You can’t run libvirt using Network Manager, you’ll have to switch to Wicked… This can be seen and verified running

systemctl status libvirtd.service

That’s important to know, and an interesting issue I didn’t run into before… but seems to be a documented issue at least since LEAP 15.0.

But,
At least for my situation where I installed Hypervisor and Tools during the initial install, that isn’t enough, you’ll still see something else (I’ve forgotten what that is for the moment and don’t want to roll everything back just to identify it) won’t start, and force-re-installing the kvm-server and kvm-tools and their patterns didn’t fix the problem. I completely removed Kvm-server and kvm-tools and libvirt packages to get a working system.

zypper rm kvm-server kvm-tools patterns-kvm_server kvm-tools patterns-kvm_tools 'libvirt*'    

Followed by using YaST to install Hypervisor and Tools.

After completing the above,
Finally libvirtd started up on boot and everything looks normal.

It’s interesting that when incorrectly installed,
Libvirtd fails to start on boot silently without throwing any events marked as errors, but starting the service manually revealed the failures that had to be overcome…

TSU

[ilvipero]

Hello,

Thanks for your reply. I had a look at the services and did not notice anything failed. Very interesting indeed.
I am sure that on my desktop+networkmanager based machines I installed KVM from Yast after I installed and updated tumbleweed.
On the headless server+wicked, I don’t recall if I installed KVM during installation or later on. That never had any issues so I did not pay too much attention to it.

I also tried disabling apparmor on my desktop to see if it was any help, but not that I can say.

Going to run the action you recommended and follow up.

Thank you!
Mauro

[ilvipero]

I tried remove all kvm components, reboot, reinstall, reboot, no change.
I changed apparmor settings on all profiles to complain, reboot and no change.

After the changes above, situation is the same:
If I reboot my laptop/deskop, open virt-manager, go to QEMU/KVM I see my virtual networks defied there, marked to start on boot. but currently inactive.
If I run sudo virsh net-list, the list is empty
If I check service status by running sudo systemctl status libvirtd.service, I see it active (running) no issue that I can see.

So what I tried next:

1. went to check the logs and found a lot of errors regarding libvirtd on startup, as Tsu2 said. Attaching error logs below.
2. without rebooting, I issued a sudo systemctl stop libvirtd.service
3. without rebooting, I issued a sudo systemctl start libvirtd.service

libvirtd came back, and from both virt-manager and sudo virsh net-list, I can see my virtual networks active.

As a temporary workaround I guess I can make a small login script that restarts libvirtd.service.
As for a permanent solution, unless you guys have other ideas, I will search openSUSE bugzilla if there are open bugs. If not, I will file one.

PS
I have a couple of centOS7 installs, using networkmanager and it seems there is no problem with virtual networks after reboot.

ilvipero@MGLT-AERO14:~> sudo journalctl -b | grep libvirt
Jul 08 14:22:13 MGLT-AERO14 systemd[1]: /usr/lib/systemd/system/virtlockd.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/libvirt/virtlockd-sock → /run/libvirt/virtlockd-sock; please update the unit file accordingly.
Jul 08 14:22:13 MGLT-AERO14 systemd[1]: /usr/lib/systemd/system/virtlockd-admin.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/libvirt/virtlockd-admin-sock → /run/libvirt/virtlockd-admin-sock; please update the unit file accordingly.
Jul 08 14:22:13 MGLT-AERO14 systemd[1]: /usr/lib/systemd/system/virtlogd.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/libvirt/virtlogd-sock → /run/libvirt/virtlogd-sock; please update the unit file accordingly.
Jul 08 14:22:13 MGLT-AERO14 systemd[1]: /usr/lib/systemd/system/virtlogd-admin.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/libvirt/virtlogd-admin-sock → /run/libvirt/virtlogd-admin-sock; please update the unit file accordingly.
Jul 08 14:22:18 MGLT-AERO14 systemd[1]: /usr/lib/systemd/system/virtlogd.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/libvirt/virtlogd-sock → /run/libvirt/virtlogd-sock; please update the unit file accordingly.
Jul 08 14:22:18 MGLT-AERO14 systemd[1]: /usr/lib/systemd/system/virtlogd-admin.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/libvirt/virtlogd-admin-sock → /run/libvirt/virtlogd-admin-sock; please update the unit file accordingly.
Jul 08 14:22:18 MGLT-AERO14 systemd[1]: /usr/lib/systemd/system/virtlockd.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/libvirt/virtlockd-sock → /run/libvirt/virtlockd-sock; please update the unit file accordingly.
Jul 08 14:22:18 MGLT-AERO14 systemd[1]: /usr/lib/systemd/system/virtlockd-admin.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/libvirt/virtlockd-admin-sock → /run/libvirt/virtlockd-admin-sock; please update the unit file accordingly.
Jul 08 14:22:19 MGLT-AERO14 systemd[1]: /usr/lib/systemd/system/virtlogd.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/libvirt/virtlogd-sock → /run/libvirt/virtlogd-sock; please update the unit file accordingly.
Jul 08 14:22:19 MGLT-AERO14 systemd[1]: /usr/lib/systemd/system/virtlogd-admin.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/libvirt/virtlogd-admin-sock → /run/libvirt/virtlogd-admin-sock; please update the unit file accordingly.
Jul 08 14:22:19 MGLT-AERO14 systemd[1]: /usr/lib/systemd/system/virtlockd.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/libvirt/virtlockd-sock → /run/libvirt/virtlockd-sock; please update the unit file accordingly.
Jul 08 14:22:19 MGLT-AERO14 systemd[1]: /usr/lib/systemd/system/virtlockd-admin.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/libvirt/virtlockd-admin-sock → /run/libvirt/virtlockd-admin-sock; please update the unit file accordingly.
Jul 08 14:22:19 MGLT-AERO14 systemd[1]: /usr/lib/systemd/system/virtlogd.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/libvirt/virtlogd-sock → /run/libvirt/virtlogd-sock; please update the unit file accordingly.
Jul 08 14:22:19 MGLT-AERO14 systemd[1]: /usr/lib/systemd/system/virtlogd-admin.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/libvirt/virtlogd-admin-sock → /run/libvirt/virtlogd-admin-sock; please update the unit file accordingly.
Jul 08 14:22:19 MGLT-AERO14 systemd[1]: /usr/lib/systemd/system/virtlockd.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/libvirt/virtlockd-sock → /run/libvirt/virtlockd-sock; please update the unit file accordingly.
Jul 08 14:22:19 MGLT-AERO14 systemd[1]: /usr/lib/systemd/system/virtlockd-admin.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/libvirt/virtlockd-admin-sock → /run/libvirt/virtlockd-admin-sock; please update the unit file accordingly.
Jul 08 14:22:20 MGLT-AERO14 systemd[1]: /usr/lib/systemd/system/virtlogd.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/libvirt/virtlogd-sock → /run/libvirt/virtlogd-sock; please update the unit file accordingly.
Jul 08 14:22:20 MGLT-AERO14 systemd[1]: /usr/lib/systemd/system/virtlogd-admin.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/libvirt/virtlogd-admin-sock → /run/libvirt/virtlogd-admin-sock; please update the unit file accordingly.
Jul 08 14:22:20 MGLT-AERO14 systemd[1]: /usr/lib/systemd/system/virtlockd.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/libvirt/virtlockd-sock → /run/libvirt/virtlockd-sock; please update the unit file accordingly.
Jul 08 14:22:20 MGLT-AERO14 systemd[1]: /usr/lib/systemd/system/virtlockd-admin.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/libvirt/virtlockd-admin-sock → /run/libvirt/virtlockd-admin-sock; please update the unit file accordingly.
Jul 08 14:22:21 MGLT-AERO14 libvirtd[1757]: 2019-07-08 06:22:21.560+0000: 1757: info : libvirt version: 5.4.0
Jul 08 14:22:21 MGLT-AERO14 libvirtd[1757]: 2019-07-08 06:22:21.560+0000: 1757: info : hostname: MGLT-AERO14
Jul 08 14:22:21 MGLT-AERO14 libvirtd[1757]: 2019-07-08 06:22:21.560+0000: 1757: warning : virGetHostnameImpl:540 : getaddrinfo failed for ‘MGLT-AERO14’: Name or service not known
Jul 08 14:22:21 MGLT-AERO14 libvirtd[1757]: libvirt version: 5.4.0
Jul 08 14:22:21 MGLT-AERO14 libvirtd[1757]: hostname: MGLT-AERO14
Jul 08 14:22:21 MGLT-AERO14 libvirtd[1757]: Failed to intialize libnetcontrol. Management of interface devices is disabled
Jul 08 14:22:23 MGLT-AERO14 libvirtd[1757]: internal error: Child process (VIR_BRIDGE_NAME=virbr1 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/nat.conf --leasefile-ro --dhcp-script=/usr/lib64/libvirt/libvirt_leaseshelper) unexpected exit status 5:
Jul 08 14:22:24 MGLT-AERO14 libvirtd[1757]: internal error: Child process (VIR_BRIDGE_NAME=virbr0 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib64/libvirt/libvirt_leaseshelper) unexpected exit status 5:
Jul 08 14:26:52 MGLT-AERO14 libvirtd[1757]: this function is not supported by the connection driver: virConnectNumOfInterfaces
ilvipero@MGLT-AERO14:~>

[ilvipero]

Quick update for the record.I added this line to my crontab:
@reboot root ( sleep 30 ; systemctl restart libvirtd.service )

Dirty hack but works for me, I hope it helps others down the road.

[tsu2]

@ilvipero

Quick update for the record.I added this line to my crontab:
@reboot root ( sleep 30 ; systemctl restart libvirtd.service )

Dirty hack but works for me, I hope it helps others down the road.

On the other hand…
As I described, you’d likely determine the cause of your failure by running

systemctl start libvirtd && systemctl status libvirtd

And,
If the problem you see is as I described, then you can fix it as I described (properly re-install).

TSU

[ilvipero]

Hi,

Actually I did but there are no errors when I restart the service manually. Also re-installing per your recommendation was tried but did not help in my case.

But yes your help was of great value because I had another better look at my logs during boot up and found the errors with libvirtd .you can see in the logs i posted above.

Thanks!
Mauro

[tsu2]

Post the entire result of

systemctl start libvirtd.service

Or, if it’s already running, then restart instead of start…

TSU

[ilvipero]

Tsu2, thank you for your help.

libvirtd.service - Virtualization daemon
Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: disabled)
Active: active (running) since Tue 2019-07-09 17:19:55 CST; 16s ago
Docs: man:libvirtd(8)
https://libvirt.org
Main PID: 11568 (libvirtd)
Tasks: 19 (limit: 32768)
Memory: 15.9M
CGroup: /system.slice/libvirtd.service
├─ 2729 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib6>
├─ 2730 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib6>
└─11568 /usr/sbin/libvirtd --listen

[tsu2]

@ilvipero

Tsu2, thank you for your help.

libvirtd.service - Virtualization daemon
Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: disabled)
Active: active (running) since Tue 2019-07-09 17:19:55 CST; 16s ago
Docs: man:libvirtd(8)
https://libvirt.org
Main PID: 11568 (libvirtd)
Tasks: 19 (limit: 32768)
Memory: 15.9M
CGroup: /system.slice/libvirtd.service
├─ 2729 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib6>
├─ 2730 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib6>
└─11568 /usr/sbin/libvirtd --listen

OK, and it’s customary to enclose console output (and input) in CODE tagas (the hash button in the text editor).
According to what you posted, your system is working.
The object was to try to capture output when it sin’t working.

TSU

[ilvipero]

Hello Tsu2

Got it on the quotes, sorry about that.

And yes my only issue with virt-manager virtual networks is they fail at startup, per my logs attached. Once I restart the service after login, everything works fine.
But it still fails every time I reboot my desktop and laptop. Do you think I should open a bug in openSUSE bugzilla?

Thanks
Mauro

[tsu2]

@ilvipero

Hello Tsu2

Got it on the quotes, sorry about that.

And yes my only issue with virt-manager virtual networks is they fail at startup, per my logs attached. Once I restart the service after login, everything works fine.
But it still fails every time I reboot my desktop and laptop. Do you think I should open a bug in openSUSE bugzilla?

Thanks
Mauro

No,
Sounds like you need to disable your auto reboot so that your error can happen,
Then start the service to see if the error is displayed.

If the error doesn’t display,
Then you’ll have no choice but to inspect your boot log, you can try the following filters

The following didn’t return anything useful for me, but you should try it anyway

journalctl -p err -b

Should display useful info

journalctl -u libvirtd.service -b

TSU

[knurpht]

@ilvipero

Hello Tsu2

Got it on the quotes, sorry about that.

And yes my only issue with virt-manager virtual networks is they fail at startup, per my logs attached. Once I restart the service after login, everything works fine.
But it still fails every time I reboot my desktop and laptop. Do you think I should open a bug in openSUSE bugzilla?

Thanks
Mauro

Yes, please do so. Looks like it’s NM related, it probably tries to start before NM establishes a connection. That would have to be fixed in the systemd units, AFAIK.

[tsu2]

@Knurpht

Yes, please do so. Looks like it’s NM related, it probably tries to start before NM establishes a connection. That would have to be fixed in the systemd units, AFAIK.

That’s only one possibility, and if that is the cause you would see a timeout error.
There are other possible causes like what I found which means you have to actually see what the journal says.

TSU

[ilvipero]

Hello, Thanks for your help and sorry for delayed response, I have been away.

I did some more testing per your recommendations. Before doing all those tests, I disabled apparmor, to eliminate one extra variable. I also disabled my crontab script that restarts libvirtd.service after 45 seconds @reboot.

1. Disabled libvirtd.service from auto start on boot. Rebooted the system. Logged in. started libvirtd.service manually. No problem. Virtual networks are available.

● libvirtd.service - Virtualization daemon
   Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; disabled; vendor preset: disabled)
   Active: active (running) since Sat 2019-07-20 11:11:55 CST; 16s ago
     Docs: man:libvirtd(8)
           https://libvirt.org
 Main PID: 2993 (libvirtd)
    Tasks: 19 (limit: 32768)
   Memory: 81.5M
   CGroup: /system.slice/libvirtd.service
           ├─2993 /usr/sbin/libvirtd --listen
           ├─3091 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib64/libvirt/libvirt_leaseshelper
           └─3092 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib64/libvirt/libvirt_leaseshelper

Jul 20 11:11:56 MGDT-ROG dnsmasq[3091]: started, version 2.80 cachesize 2000
Jul 20 11:11:56 MGDT-ROG dnsmasq[3091]: compile time options: IPv6 GNU-getopt DBus i18n IDN2 DHCP DHCPv6 Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify dumpfile
Jul 20 11:11:56 MGDT-ROG dnsmasq-dhcp[3091]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h
Jul 20 11:11:56 MGDT-ROG dnsmasq-dhcp[3091]: DHCP, sockets bound exclusively to interface virbr0
Jul 20 11:11:56 MGDT-ROG dnsmasq[3091]: reading /etc/resolv.conf
Jul 20 11:11:56 MGDT-ROG dnsmasq[3091]: using nameserver 192.168.250.5#53
Jul 20 11:11:56 MGDT-ROG dnsmasq[3091]: using nameserver 168.95.1.1#53
Jul 20 11:11:56 MGDT-ROG dnsmasq[3091]: read /etc/hosts - 7 addresses
Jul 20 11:11:56 MGDT-ROG dnsmasq[3091]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
Jul 20 11:11:56 MGDT-ROG dnsmasq-dhcp[3091]: read /var/lib/libvirt/dnsmasq/default.hostsfile

2. Re enabled libvirtd.service to start automatically at boot. Rebooted the system. Virtual networks are not enabled. I see errors in libvirtd.service, regarding resolv.conf and dnsmasq

● libvirtd.service - Virtualization daemon
   Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: disabled)
   Active: active (running) since Sat 2019-07-20 12:06:55 CST; 7min ago
     Docs: man:libvirtd(8)
           https://libvirt.org
 Main PID: 1852 (libvirtd)
    Tasks: 17 (limit: 32768)
   Memory: 83.5M
   CGroup: /system.slice/libvirtd.service
           └─1852 /usr/sbin/libvirtd --listen

Jul 20 12:06:55 MGDT-ROG libvirtd[1852]: 2019-07-20 04:06:55.213+0000: 1852: info : hostname: MGDT-ROG
Jul 20 12:06:55 MGDT-ROG libvirtd[1852]: 2019-07-20 04:06:55.213+0000: 1852: warning : virGetHostnameImpl:540 : getaddrinfo failed for 'MGDT-ROG': Name or service not known
Jul 20 12:06:55 MGDT-ROG libvirtd[1852]: libvirt version: 5.4.0
Jul 20 12:06:55 MGDT-ROG libvirtd[1852]: hostname: MGDT-ROG
Jul 20 12:06:55 MGDT-ROG libvirtd[1852]: Failed to intialize libnetcontrol.  Management of interface devices is disabled
Jul 20 12:06:55 MGDT-ROG systemd[1]: Started Virtualization daemon.
Jul 20 12:06:55 MGDT-ROG dnsmasq[1960]: directory /etc/resolv.conf for resolv-file is missing, cannot poll
Jul 20 12:06:55 MGDT-ROG dnsmasq[1960]: FAILED to start up
Jul 20 12:06:55 MGDT-ROG libvirtd[1852]: internal error: Child process (VIR_BRIDGE_NAME=virbr0 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib64/libvirt/libvirt_leaseshelper) unexpected exit status 5: 
                                         dnsmasq: directory /etc/resolv.conf for resolv-file is missing, cannot poll
Jul 20 12:08:27 MGDT-ROG libvirtd[1852]: this function is not supported by the connection driver: virConnectNumOfInterfaces

3. After this, I manually restarted libvirtd.service and errors are gone. virtual networks start correctly.

● libvirtd.service - Virtualization daemon
   Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: disabled)
   Active: active (running) since Sat 2019-07-20 12:16:37 CST; 1s ago
     Docs: man:libvirtd(8)
           https://libvirt.org
 Main PID: 3735 (libvirtd)
    Tasks: 19 (limit: 32768)
   Memory: 17.2M
   CGroup: /system.slice/libvirtd.service
           ├─3735 /usr/sbin/libvirtd --listen
           ├─3798 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib64/libvirt/libvirt_leaseshelper
           └─3799 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib64/libvirt/libvirt_leaseshelper

Jul 20 12:16:37 MGDT-ROG dnsmasq[3798]: started, version 2.80 cachesize 2000
Jul 20 12:16:37 MGDT-ROG dnsmasq[3798]: compile time options: IPv6 GNU-getopt DBus i18n IDN2 DHCP DHCPv6 Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify dumpfile
Jul 20 12:16:37 MGDT-ROG dnsmasq-dhcp[3798]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h
Jul 20 12:16:37 MGDT-ROG dnsmasq-dhcp[3798]: DHCP, sockets bound exclusively to interface virbr0
Jul 20 12:16:37 MGDT-ROG dnsmasq[3798]: reading /etc/resolv.conf
Jul 20 12:16:37 MGDT-ROG dnsmasq[3798]: using nameserver 192.168.250.5#53
Jul 20 12:16:37 MGDT-ROG dnsmasq[3798]: using nameserver 168.95.1.1#53
Jul 20 12:16:37 MGDT-ROG dnsmasq[3798]: read /etc/hosts - 7 addresses
Jul 20 12:16:37 MGDT-ROG dnsmasq[3798]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
Jul 20 12:16:37 MGDT-ROG dnsmasq-dhcp[3798]: read /var/lib/libvirt/dnsmasq/default.hostsfile

[tsu2]

Looks like your problem has been resolved.
Whatever the problem was before,
It seems to be resolved finally by re-generating your /etc/resolv.conf which can be done on reboot or by running the command

netconfig

Note that this does not appear to be related to the frequently seen dns configuration issue that requires a forced regeneration (with -f flag).

TSU

[zabia]

Hi,
I have a similar problem but I can’t fix it.
My system is opensuse 15.1 leap. After restart, the default network is inactive, the virbr0 interface does not appear in the interface list.
Listing attached (some information may be in Polish)

autostart for the default network is enabled.
Of course, manual activation is possible. However, I would like the network to start automatically after restarting the hypervisor system

ip l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 88:ae:1d:7c:af:4c brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
    link/ether 5c:ac:4c:77:43:aa brd ff:ff:ff:ff:ff:ff

virsh # net-list 
 Name   State   Autostart   Persistent
----------------------------------------

virsh # net-list --all
 Name      State      Autostart   Persistent
----------------------------------------------
 default   inactive   yes         yes

acer:~ # ls -l /etc/resolv.conf
lrwxrwxrwx 1 root root 30 May 25 17:18 /etc/resolv.conf -> /var/run/netconfig/resolv.conf

acer:~ # systemctl is-active NetworkManager
active

acer:~ # journalctl -b -p err
-- Logs begin at Sun 2019-09-15 10:09:21 CEST, end at Sun 2019-09-15 11:21:25 CEST. --
Sep 15 10:09:25 acer kernel: sd 4:0:0:0: [sdb] No Caching mode page found
Sep 15 10:09:25 acer kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through
Sep 15 10:09:31 acer kernel: audit: backlog limit exceeded
Sep 15 10:09:31 acer kernel: audit: backlog limit exceeded
Sep 15 10:09:31 acer kernel: audit: backlog limit exceeded
Sep 15 10:09:31 acer dnsmasq[1890]: directory /etc/resolv.conf for resolv-file is missing, cannot poll
Sep 15 10:09:31 acer dnsmasq[1890]: FAILED to start up
Sep 15 10:09:31 acer libvirtd[1628]: internal error: Child process (VIR_BRIDGE_NAME=virbr0 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/def>
                                     dnsmasq: directory /etc/resolv.conf for resolv-file is missing, cannot poll
Sep 15 10:09:32 acer gdm[1708]: gdm_session_handle_secret_info_query: assertion 'self->priv->user_verifier_interface != NULL' failed
Sep 15 10:09:32 acer gdm-autologin][2036]: gkr-pam: couldn't get the password from user: Błąd rozmowy
Sep 15 10:09:42 acer /hp-upgrade[2697]: hp-upgrade[2697]: error: HPLIP upgrade is disabled by openSUSE for security reasons, see https://bugzilla.nov>
Sep 15 10:10:02 acer pulseaudio[2199]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a >
Sep 15 10:32:17 acer libvirtd[1628]: ta funkcja jest nieobsługiwana przez sterownik połączenia: virConnectGetCPUModelNames
Sep 15 10:32:17 acer libvirtd[1628]: ta funkcja jest nieobsługiwana przez sterownik połączenia: virConnectNumOfInterfaces
Sep 15 10:32:17 acer kernel: audit: backlog limit exceeded
Sep 15 10:32:17 acer kernel: audit: backlog limit exceeded
Sep 15 10:32:17 acer kernel: audit: backlog limit exceeded
Sep 15 10:32:17 acer libvirtd[10352]: Failed to open file '/sys/kernel/security/apparmor/profiles': Permission denied
Sep 15 10:32:17 acer libvirtd[10352]: Failed to read AppArmor profiles list '/sys/kernel/security/apparmor/profiles': Permission denied
Sep 15 10:32:17 acer libvirtd[10352]: Failed to open file '/sys/kernel/security/apparmor/profiles': Permission denied
Sep 15 10:32:17 acer libvirtd[10352]: Failed to read AppArmor profiles list '/sys/kernel/security/apparmor/profiles': Permission denied
Sep 15 10:32:17 acer libvirtd[10352]: this function is not supported by the connection driver: virConnectNumOfInterfaces
Sep 15 10:32:18 acer libvirtd[1628]: ta funkcja jest nieobsługiwana przez sterownik połączenia: virConnectNumOfInterfaces

acer:~ # journalctl -b -u libvirtd
-- Logs begin at Sun 2019-09-15 10:09:21 CEST, end at Sun 2019-09-15 11:39:26 CEST. --
Sep 15 10:09:30 acer systemd[1]: Starting Virtualization daemon...
Sep 15 10:09:30 acer libvirtd[1628]: libvirt version: 5.1.0
Sep 15 10:09:30 acer libvirtd[1628]: hostname: acer
Sep 15 10:09:30 acer libvirtd[1628]: Failed to intialize libnetcontrol.  Management of interface devices is disabled
Sep 15 10:09:30 acer systemd[1]: Started Virtualization daemon.
Sep 15 10:09:31 acer dnsmasq[1890]: directory /etc/resolv.conf for resolv-file is missing, cannot poll
Sep 15 10:09:31 acer dnsmasq[1890]: FAILED to start up
Sep 15 10:09:31 acer libvirtd[1628]: internal error: Child process (VIR_BRIDGE_NAME=virbr0 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/def>
                                     dnsmasq: directory /etc/resolv.conf for resolv-file is missing, cannot poll
Sep 15 10:32:17 acer libvirtd[1628]: ta funkcja jest nieobsługiwana przez sterownik połączenia: virConnectGetCPUModelNames
Sep 15 10:32:17 acer libvirtd[1628]: ta funkcja jest nieobsługiwana przez sterownik połączenia: virConnectNumOfInterfaces
Sep 15 10:32:18 acer libvirtd[1628]: ta funkcja jest nieobsługiwana przez sterownik połączenia: virConnectNumOfInterfaces

[tsu2]

First, be aware that it’s usually inadvisable to add your own problem to an existing thread when the problem can be complex.
In this case though, it does look like your problem also likely involves a missing /etc/resolv.conf

Did you try regenerating the missing file by running the following command?

netconfig update

And if the above doesn’t work, the file itself suggests “forcing” the update

netconfig update -f

TSU

[zabia]

Commands execute without errors.

[zabia]

There is a problem with Network Manager (the hypervisor is a laptop). As I changed to wicked it all works well.
I sense a small war between RedHat and SUSE. (btrfs, cockpit now NetworkManager)