Works fine in 126.96.36.199.2-developers-only.
May 11 2020
May 2 2020
Apr 28 2020
Apr 23 2020
xfce4-power-manager is installed on Whonix-Host in 188.8.131.52.2-developers-only.
Fixed in 184.108.40.206.2-developers-only.
Setting quiet loglevel=0 in that exact order as per https://github.com/Whonix/security-misc/commit/6485df8126b52a2072824fa442e8d1dd5cb18981 does now hide [sda] Incomplete mode parameter data. However, messages by LKRG are not yet hidden.
Great news! I am rebuilding the whole package Host+gw+ws now, excited to test it out! Will report asap.
echo "options overlay metacopy=on" > /etc/modprobe.d/overlay.conf update-initramfs -u
Apr 21 2020
That would be OK but this is not my preferred solution. Reason: an unclean shutdown in Whonix installed persistent mode would with a subsequent boot into live mode would result in a failed reboot into Whonix installed live mode.
Awesome analysis and description!
Likely fixed in next build already. Updated, relevant code is here:
Not 100% sure it would also be fixed inside VMs.
Excellent work. Thanks for researching this!
Some progress made as of Whonix-Host 220.127.116.11.7:
As of Whonix-Host 18.104.22.168.7 each environment (Host, gw, ws) has its own background color.
Should we close this ticket?
Do we need more tests or can we close this ticket?
Also, just tried it on Whonix-Host 22.214.171.124.7. It works.
Apr 19 2020
Apr 16 2020
Something like that. Maybe covering all of /etc/sysctl.conf and
/etc/sysctl.d folder to GRUB_CMDLINE_LINUX expansion.
We shouldn't stop using /etc/sysctl.d for compatibility. I think the best way would be to create /etc/default/grub.d/40_sysctl.cfg with:
Even kernel parameter quiet loglevel=3 rd.systemd.show_status=auto rd.udev.log_priority=3
does not hide [sda] Incomplete mode parameter data.
I can't work on this. Please go for T977.
T977 more important for now.
kernel.printk = 3 3 3 3
And of course these messages are attributed to whatever Whonix issue someone is having.
Apr 15 2020
Apr 14 2020
Apr 13 2020
Apr 10 2020
All tests done in KVM with 4 logical host CPUs, but I would expect to have similar (if not better) results on real hardware.
Apr 8 2020
Apr 7 2020
marmarek (Marek Marczykowski-Górecki):
Have you checked how it behaves with multiple Whonix Gateways?
Apr 3 2020
But we couldn't just set that IP inside sys-whonix without touching dom0?
qvm-prefs sys-whonix ip 10.152.152.10 works great so far. Will test more. And call for testers.
qvm-prefs -D sys-whonix ip
How can I undo qvm-prefs sys-whonix ip 10.152.152.10 back to default?
Mar 30 2020
 There is currently no trigger (systemd unit file) to execute /usr/lib/whonix-libvirt/persistent-mode-to-read-write.
Mar 29 2020
Mar 28 2020
That looks much better!
Mar 27 2020
Included since Whonix 126.96.36.199.8-developers-only.
Mar 26 2020
As of 188.8.131.52.7, the following behavior is observed:
Mar 22 2020
These tests are fully independent.
another way, with the main menu stuff horizontal
Ok, so you want me to:
- boot a Whonix-Host ISO
- Install on HDD
- Reboot on Whonix-Host ISO, do some stuff, shutdown
- See if HDD has been modified (why would it be?)