Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: virt-manager (Read 833 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

virt-manager

Hi,

I know there is a similar topic but I am struggling with wierd behaviour on my laptop. I would like to move from Virtualbox to Qemu/Virt-manager.
I have installed all necesery parts.
I use following steps to start networking before I run Virt-manager
Code: [Select]
1.sudo rc-service libvirtd start
2.sudo rc-service dnsmasq start
3.sudo rc-service libvirt-guests start
5.sudo virsh net-list --all
6.sudo virsh net-start default

But when I run
sudo virsh net-list --all i get
Code: [Select]
Name      State      Autostart   Persistent
----------------------------------------------
 default   inactive   yes         yes


and then
sudo virsh net-start default
Code: [Select]
error: Failed to start network default
error: Unable to create bridge virbr0: Package not installed


I get message that the virbr0 does not exists. I have reinstalled the bridge-utils several times but it did not help.However when iI reinstall bridge-utils, reboot and repeat the commands above the networking starts to work

bridge-utils >
Code: [Select]
warning: bridge-utils-1.7.1-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) bridge-utils-1.7.1-1

Total Download Size:   0.02 MiB
Total Installed Size:  0.04 MiB
Net Upgrade Size:      0.00 MiB

:: Proceed with installation? [Y/n]

Any idea what is wrong?

Thanks

Re: virt-manager

Reply #1 –
These packages need to be installed:
virt-manager qemu edk2-ovmf vde2 ebtables dnsmasq bridge-utils openbsd-netcat dmidecode virt-viewer libvirt-openrc

Services dnsmasq and libvirt-guests are not needed for a basic install.

These services need to be started: libvirtd and virtlogd
If these are enabled, everything - including virbr0: - should be present and working after each boot.

artist
 

Re: virt-manager

Reply #2 –
Hi ,

This is embarrassing but i have found the reason why it did not work. I did update (including kernel) and did not reboot laptop after.
After reboot everything works fine.
Consider this thread resolved.
Thank you for support.