With F34 Workstation, I've been using a VM I set up with Cockpit to run
F34 Server. Here are then packages I install and settings I did to do this.
sudo dnf install cockpit
sudo dnf install cockpit-machines
sudo dnf install virt-viewer
sudo systemctl enable --now cockpit.socket
sudo firewall-cmd --add-service=cockpit --permanent
sudo firewall-cmd --reload
I download the F34 Server ISO and put it in /var/lib/libvirt/
I set up a bridge and then I setup a VM with F34 server. Everything
works fine.
Today I decided to try this with F35 Workstation. I did everything that
same way as with F34, but when I started to set up a VM I got
"Virtualization service (libvirt) is not active" as soon as I clicked on
the "VirtualMachines" in cockpit. I tried starting it with the button in
the Cockpit VM screen, but it would not start. I looked and saw that
libvirtd was not installed so I installed it. at lot of other virt items
got installed with it. I tried the cockpit button again and it failed to
start, I tried starting libvirtd.service with systemctl and that did not
work. When I click the "troubleshoot" link on the Cockpit VM screen, it
shows that there apparently several virt related items not running.
Is this a bug or do I need to install more/different things to geting
this to work?
Have a Great Day!
Pat (tablepc)
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
