#Help installing Whonix on virt-manager
1 messages · Page 1 of 1 (latest)
??is this anything to do with secureblue?
I'm assuming they're using virt-manager on secureblue 🙂
that said, if this is about whonix not working in virt manager, and not about setting up virt manager on secureblue, then @glossy thorn is correct in that this is a question better suited for the whonix forums
I followed the steps here to set up Whonix in virt-manager on secureblue and it worked just fine: https://www.whonix.org/wiki/KVM
so if you were following a different guide maybe try this ^ instead
oh I think this is a bug with group management in Fedora Atomic, you need to add the group manually to /etc/group first
so you can run getent group | grep libvirt to get the entry that should be there, add your username to the end of it, and put the line in /etc/group
if you open a root shell using run0 and run the following command:
virsh -c qemu:///system net-list
what's the output?
oh actually if you've added yourself to the libvirt group you might not need to do it from a root shell
so you can just run it from a regular terminal, and if that doesn't work then try running it in a root shell
no, I just meant for the virsh command
so what this shows is that you haven't imported the Whonix virtual networks. when I run the same command, here's the output:
Name State Autostart Persistent
----------------------------------------------------
default active yes yes
Whonix-External active yes yes
Whonix-Internal active yes yes
you need to run the commands here to add the virtual networks, activate them, and import the Whonix Gatework and Workstation images to qemu: https://www.whonix.org/wiki/KVM#Importing_Whonix_VM_Templates
except since you've added yourself to the libvirt group, I don't think you need to run those commands as root, so remove sudo from the commands they give
if you did need to run them as root, you'd want to open a root shell using run0 and run the commands in there, rather than prepending run0 to each command individually—the latter approach runs into problems with SELinux, it's currently a known issue with run0