I use tumbleweed-cli to manage the update on my two laptops running tumbleweed. I just recently updated from 20200907 to 20201023 using tumbleweed-cli and I have just noticed that virt-manager and libvirt no longer detects the host’s connected network adapter card.
Just to clarify, both the wired and the wireless card are working fine at the OS level and also on VMWare Workstation but just won’t work on Libvirt and virt-manager.
The place where I don’t see it on virt-manager is:
Virt-Manager > Open any VM window > view > Details > Virtual Network Interface (Already present or newly added) > Network Source > Connected Host Network Adapter Cards missing from the drop down menu list.
also at the Terminal virsh can’t seem to be able to list host interfaces, throwing and error trying.
10:~> virsh iface-list --all
error: Failed to list active interfaces
error: this function is not supported by the connection driver: virConnectNumOfInterfaces
I was wondering if anyone else witnessing the same issue and more importantly if anyone have any idea on how to fix or work around this issue, I have many VMs on these two laptops and they all use the host’s network adapter cards to communicate outward.
Unless something has changed I’m not aware of and would be the type of change that hasn’t happened… ever before…
I don’t suspect anything related to IOMMU. AFAIK libvirt functionality is very generic and avoids requiring anything like IOMMU and IOMMU is relevant only to GPU pass-through configurations.
From your description, I also don’t suspect ACS (Automatic Channel Selection) which I would think is functionality at a lower level than virtualization management.
My question:
Are you running VMware and whatever other virtualization on the same machine?
If you are, then you need to stop a variety of VMware related services that automatically start on boot up else there will be contention and the non-VMware services won’t start.
I don’t have the exact service names and processes on Linux off the top of my head, but they relate to
VMware authentication
VMware networking (NAT service)
VMware networking (DHCP service)
VMware USB support
VMware workstation
All of the above must be located and stopped before you can launch any other virtualization.
Just checked, on both machines no less, and this does not seem to be the reason for the issue. Booted with the 5.8 kernel and the issue still persists.
I have two laptops with Tumbleweed and the same snapshot update (20201023) but one with VMWare workstation and another **without **it. The issue persists on both machines.
But since the one ***with ***the VMWare workstation pro is my (main) work laptop I just uninstalled the VMWare Workstation pro outright and tried again, but the issue still remains after a system reboot.
Hi
Are you using wicked or NetworkManager? There is a bug in wicked 0.6.63 version that only appeared when I upgraded to 0.6.64… I see there was an update to libvirt (20201105), can you update.
I was am using NetworkManager on both machines that I have had this happen to after the update. I also found at two more person with three more machines between them which are being affected on the OpenSUSE subreddit page so this thing is not happening only to me. I have no clue they are using wicked or NetworkManager though.
I will try updating forward (to 20201105) since as I mentioned before KVM / Libvirt VMs are like 95% of the current use case of this device for me which means I am currently being horribly inefficient because of this bug, and will report back.
Wanted to inform you that I just updated to 20201106 and while it did fix my other issues with akonadi sadly this issue still remains.
As mentioned previously by @Sauerland I have already filed a bug report on this subject which has not yet received much of an attention. I know this is not the community to be pushy, and that is the last thing I want to do / be but is there anywhere else I can raise this issue that might get some (more) attention maybe? As mentioned previously this has hampered my daily efficiency to a great degree and not having a workaround is just excruciating.