Network changes virtual machine does not want to connect shared drives

English Virtualization
1

I have virtual machine and I made change to the network. From “NAT” to “bridge”. NAT had an IP in the 192.168.x.x range. I created a bridge with a fixed IP using Networkmanager. I cleared the IP address for the NIC defined in the settings.

Upon start of the VM I’m presented with the following error:

Error starting domain: Cannot open log file: ‘/var/log/libvirt/qemu/opensusetumbleweed-fs0-virtiofsd.log’: Device or resource busy

Traceback (most recent call last):
File “/usr/share/virt-manager/virtManager/asyncjob.py”, line 71, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File “/usr/share/virt-manager/virtManager/asyncjob.py”, line 107, in tmpcb
callback(*args, **kwargs)
File “/usr/share/virt-manager/virtManager/object/libvirtobject.py”, line 57, in newfn
ret = fn(self, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/share/virt-manager/virtManager/object/domain.py”, line 1431, in startup
self._backend.create()
File “/usr/lib64/python3.11/site-packages/libvirt.py”, line 1379, in create
raise libvirtError(‘virDomainCreate() failed’)
libvirt.libvirtError: Cannot open log file: ‘/var/log/libvirt/qemu/opensusetumbleweed-fs0-virtiofsd.log’: Device or resource busy

I was able to resolve the issue by removing the defined shared filesystem.

Upon boot there was/ is no network and I need the shared directories. I reverted my network changes. After reverting my changes I still don’t get a Internet connection in the VM.

How can I regenerate the network so I get connected to the Internet again in the VM?

2

Please share the current guest IP configuration…

ip a

ip r

grep "name" /etc/resolv.conf
3

Show us the NetworkManager device connectivity…

nmcli d

More questions may follow.

4

I missed this in the opening post. Can you supply further clarification please?

5

The following is the output of the asked commands:

tneo@localhost:~> ip a
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 noprefixroute 
       valid_lft forever preferred_lft forever
2: enp12s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 52:54:00:9b:9f:47 brd ff:ff:ff:ff:ff:ff
tneo@localhost:~> ip r
tneo@localhost:~> grep "name" /etc/resolv.conf
nameserver 192.168.100.1
tneo@localhost:~> nmcli d
DEVICE   TYPE      STATE                   CONNECTION 
lo       loopback  connected (externally)  lo         
enp12s0  ethernet  disconnected            --

When I made a modification to the network to switch from NAT to Bridge, the traceback came forward. That tells that virtiofsd is having an issue. Virtiofsd is used for the shared files to be available within the VM. I removed the file sharing definitions and that resolved that issue.

6

I have it working now. I made a mistake in the virtual network configuration in Qemu.

7

However when I add the filesystem back it throws the same error. :frowning:

8

Once again, can you clarify further regarding the shared file system? A remote filesystem of some kind? Configuration files that you can share here?

9

It was not clear what kind of clarification you were looking for. :slight_smile:

The shares are just 2 directories from my local system. I have now resolved that as well by moving the target path to a different directory. My mounts are then working again.

I don’t understand what happened and why.