Bugzilla – Bug 1139507
libvirt virtual network not start on boot
Last modified: 2020-02-04 13:29:25 UTC
hello, i have changed the name of the default virtual network of the device virbr0, so when i restart the pc or boot up the pc after a state of off, when i open virt-manager, and try to start the VM, appear the next error: Error starting domain: Requested operation is not valid: network 'virtlan0' (new name) is not active. Details: Error starting domain: Requested operation is not valid: network 'virtlan0' is not active Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 111, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 66, in newfn ret = fn(self, *args, **kwargs) File "/usr/share/virt-manager/virtManager/domain.py", line 1422, in startup self._backend.create() File "/usr/lib64/python3.6/site-packages/libvirt.py", line 1089, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirt.libvirtError: Requested operation is not valid: network 'virtlan0' is not active systemctl status -l libvirtd ● libvirtd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: disabled) Active: active (running) since Wed 2019-06-26 20:54:22 AST; 7min ago Docs: man:libvirtd(8) https://libvirt.org Main PID: 1810 (libvirtd) Tasks: 17 (limit: 32768) CGroup: /system.slice/libvirtd.service └─1810 /usr/sbin/libvirtd --listen Jun 26 20:54:20 DevWEDC libvirtd[1810]: 2019-06-27 00:54:20.448+0000: 1810: info : libvirt version: 5.1.0 Jun 26 20:54:20 DevWEDC libvirtd[1810]: 2019-06-27 00:54:20.448+0000: 1810: info : hostname: DevWEDC Jun 26 20:54:20 DevWEDC libvirtd[1810]: 2019-06-27 00:54:20.448+0000: 1810: warning : virGetHostnameImpl:713 : getaddrinfo failed for 'DevWEDC': Name or service not known Jun 26 20:54:21 DevWEDC libvirtd[1810]: libvirt version: 5.1.0 Jun 26 20:54:21 DevWEDC libvirtd[1810]: hostname: DevWEDC Jun 26 20:54:21 DevWEDC libvirtd[1810]: Failed to intialize libnetcontrol. Management of interface devices is disabled Jun 26 20:54:22 DevWEDC systemd[1]: Started Virtualization daemon. Jun 26 20:54:27 DevWEDC dnsmasq[2172]: directory /etc/resolv.conf for resolv-file is missing, cannot poll Jun 26 20:54:27 DevWEDC libvirtd[1810]: internal error: Child process (VIR_BRIDGE_NAME=virbr0 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/virtlan0.conf --leasefile-ro --dhcp-script=/usr/lib64/libvirt/lib> dnsmasq: directory /etc/resolv.conf for resolv-file is missing, cannot poll Jun 26 20:55:00 DevWEDC libvirtd[1810]: this function is not supported by the connection driver: virConnectNumOfInterfaces Now if i manually start will work, but i need to auto start function.
Looks like a duplicate of bug #1123699. Reopen if it is not the case. *** This bug has been marked as a duplicate of bug 1123699 ***
the https://bugzilla.opensuse.org/show_bug.cgi?id=1123699 is about when you do a clean install of the virtualization pattern. when i did the installation the default network start and autostart too, my problem appear after i change the default network name, start, but when i check autostart and restart the service or the pc, this wont autostart solo.
The way you got there might be different, but the root cause is most probably the same: dnsmasq refuses to start, because the /etc/resolv.conf symlink points to a file in a not yet existing directory. Please try the solution given in bug 1123699 comment 34 and feel free to reopen if that doesn't help. *** This bug has been marked as a duplicate of bug 1123699 ***
(In reply to Reinhard Max from comment #3) > The way you got there might be different, but the root cause is most > probably the same: dnsmasq refuses to start, because the /etc/resolv.conf > symlink points to a file in a not yet existing directory. > > Please try the solution given in bug 1123699 comment 34 and feel free to > reopen if that doesn't help. > > *** This bug has been marked as a duplicate of bug 1123699 *** ok, thank you, i will test.
(In reply to Reinhard Max from comment #3) > The way you got there might be different, but the root cause is most > probably the same: dnsmasq refuses to start, because the /etc/resolv.conf > symlink points to a file in a not yet existing directory. > > Please try the solution given in bug 1123699 comment 34 and feel free to > reopen if that doesn't help. > > *** This bug has been marked as a duplicate of bug 1123699 *** that solve the problem, thank you.
(In reply to Reinhard Max from comment #3) > The way you got there might be different, but the root cause is most > probably the same: dnsmasq refuses to start, because the /etc/resolv.conf > symlink points to a file in a not yet existing directory. > > Please try the solution given in bug 1123699 comment 34 and feel free to > reopen if that doesn't help. That also helped in my case, thanks!