Previously, running virt-manager it showed the connection. On rebase, I think I only installed virt-manager and not the qemu packages, which I did afterwards. So probably I just need to delete the virtmanager cache, as now all packages are installed?
Edit: I just tried the Distrobox way and it is pretty interesting. But the “browse files” does not work, which doesnt spark joy. Selecting folders works somewhat, but its pretty weird.
adding a directory doesnt let me open a directory inside that, I would need to add every damn diretory containing .iso files
After a reboot virt-manager shows my ISOs! I just tried my Opensuse Slowroll VM and it works well! The app is in english and I have no GPU acceleration though. But so far, great! I will just remove the layered bloat if it works well. Thanks Luca!
I see the same issue, my workaround right now is enabling and starting (the monolithic) libvirtd, after that libvirt works as expected so far. It seems the issue is related to libvirt’s modular architecture, similarly to the recent systemd socket activation issues (I don’t know what causes it now).
I’ve reproduced this on both Kinoite and Silverblue, I don’t have other editions ready to test on.
Update: The “reset to defaults” somehow worked now.
So the out of the box experience should just work, with one exception, which is pretty annoying, I have no internet in a Win11 and a Fedora Rawhide VM.
I created the network device as vibr0 (or how its called) and the mode is virtIO.
The Redhat Driver is even recognized in Windows, not sure about the Fedora VM. But no VM has internet connection.
The Windows one doesnt show any network even though connecting the Spice Drivers ISO, installing the gust additions, removing the network driver, reinstalling it, checking for manual updates, it reports as “already using the best driver”.
On the Fedora VM I get a “connected to wifi” but with a warning sign and I have no internet.
The default network first time just worked, how do I create this network?? Win11 may have different troubles and I didnt test that before. But even there all the rest is working great.
Btw is there a way to pass all USB devices at once, or really just one at a time?
If using a libvirt VM the default bridge device created is virbr0.
I use that device by simply telling VMM to use bridged and specifying that device when I create the VM.
If you created a new device named virbr0 then it may be interfering with the default device that libvirt creates automatically.
It also seems that a bridge device attached to a wifi interface may not function. There have been posts here on that issue as well
This is the way mine is set up, and remember I said it was the default virbr0 device
Note that the image I show was from using virt-manager. I use virt manager (VMM) to manage all my VMs and have never had an issue. The virbr0 device is created as soon as you create the first VM with VMM and remains available as long as a single VM is defined, though not active unless a VM has been started.
Libvirt also creates a vnet by default for each VM in use. You can see in this image the vnet1 and vnet2 for the 2 VMs I currently have running. One is rawhide and the other is win11.
Hello @boredsquirrel ,
If you type nmcli it should show you your network connections including the virtual ones. As @computersavvy mentioned libvirt creates virbr0 , it does this when you create the VM in Virt-Manager I think. Anyway, my virbr0 is connected to my lan port as …
enp4s0: connected to Wired connection 1
“Realtek RTL8111/8168/8411”
ethernet (r8169), CE:DD:5F:28:77:57, hw, mtu 1500
master virbr0
While my virbr0 looks like …
virbr0: connected to virbr0
“virbr0”
bridge, CE:DD:5F:28:77:57, sw, mtu 1500
ip4 default
inet4 192.168.0.105/16
route4 192.168.0.0/16 metric 425
route4 default via 192.168.0.1 metric 425
inet6 fe80::7d57:271b:2aaa:7352/64
route6 fe80::/64 metric 1024
Notice it’s a bridge device
And as a note from my experiences, VirtualBox is okay for doing a quick VM setup to test something, but if I need to actually work with it I always use Virt-Manager since it is so much more configurable.
hmm, I tried creating a new network and activating it, but it doesnt show up in virtmanager. This worked before on a vanilla install, but I would really like to avoid reinstalling.
# define config
echo '<network>
<name>network</name>
<bridge name="virbr0" />
<forward mode="nat" />
<ip address="192.168.122.1" netmask="255.255.255.0">
<dhcp>
<range start="192.168.122.2" end="192.168.122.254" />
</dhcp>
</ip>
</network>' > network.xml
# Define and start the network
virsh net-define network.xml
virsh net-start network
# Verify the status
virsh net-info network
# Set the network to autostart
virsh net-autostart network
I tried this, in this order. I restarted the libvirtd service and virt-manager, killed the programs in between. But “network” is not even showing.
