[quote=“Patrick, post:1, topic:460”]Referring to:
Wondering, why not use whonixcheck?
It is supposed to be useful exactly for this situation by running several related connectivity check (Tor pid running, Tor bootstrapped, check.torproject.org connectivity test, etc.):
systemcheck - Security Check Application
If it’s missing something or it’s output is not useful enough, I’d improve it.[/quote]
I would like to use whonixcheck instead. I didn’t use it yet, partly due to the mindset of wanting to get some working instructions published first and do optimizations later, also, as you mentioned, whonixcheck is blocked from working out of the box with Qubes/Xen, and currently requires an extra change to enable it first. So I’m certainly not opposed to whonixcheck. More was just a mindset of getting directly through the step right away, without barriers, when I wrote it.
[quote=“Patrick, post:1, topic:460”]After leak testing is done, we should also remove the warning against unsupported virtualizer:
A trivial change I could do. For that purpose, please run.
Inside a Qubes VM and tell me the result.[/quote]
Yes. This would be nice to have removed for Qubes + Whonix 9.
The “sudo virt-what” command returns the following two lines:
Yes. I was thinking people may choose to follow that warning themselves with this current blocked whonixcheck config.
Now that Qubes + Whonix seems to be really happening and moving forward, I’m sure there will be a number of tweaks and optimizations that come to light for us. Looking forward to making numerous improvements like this!