Yes, this apply to both, files are verified.
After extract with ‘‘atool -x’’ command, the files are large 101GB but when I run the command ‘‘du -x Whonix-Gateway-*.qcow2’’ to see the real size it shows me always 101GB (I don’t believe that this is the problem)
I have download Whonix three times but nothing
Is the problem in virt-manager?
I have switched to Debian (hoping to haven’t problems). During installation I have choose to not allow root login, done automatic partition and when was encrypting the volume I cancelled inserting only passphrase. Do these choices weaken the security? (this is the first time that install Debian)
About your question, I already did this step before to install KVM, this is the result:
INFO: /dev/kvm exists
KVM acceleration can be used
Resume this topic because I want an explanation.
In the guide of the Debian installation there is this command but it’s invalid:
sudo ln -s /etc/apparmor.d/libvirt/TEMPLATE.qemu /etc/apparmor.d/libvirt/TEMPLATE.kvm
Have I to change TEMPLATE with anything?
Then there are
virsh -c qemu:///system net-autostart Whonix
virsh -c qemu:///system net-start Whonix
Do they refer about start whonix when I turn on the PC?
I’m being affected by this same problem. I’ve tried installing both 22.214.171.124.4 and 126.96.36.199.6 in Debian Stretch and got these same results. In both cases, I followed this guide (http://kkkkkkkkkk63ava6.onion/wiki/KVM), the only thing I’ve done differently is to download alternative packages for libvirt-bin, as suggested by apt:
[sudo] password for thoreau:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package libvirt-bin is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
libvirt-daemon-system libvirt-dev libvirt-clients
E: Package 'libvirt-bin' has no installation candidate