[HOME] [DOWNLOAD] [DOCS] [BLOG] [SUPPORT] [TIPS] [ISSUES] [Priority Support]

Whonix VirtualBox 14.0.0.6.6 - Testers Wanted!

#1

Originally published at: https://www.whonix.org/blog/whonix-14-0-0-6-6-testers-wanted

RAM was increased from 768 MB RAM to 1024 MB RAM for Whonix-Workstation. For now it is temporary, but it may also be permanently depending on near time developments. Discussion ongoing. Please contribute if you can share ideas or code on how to reduce RAM usage.

https://forums.whonix.org/t/whonix-14-increase-ram-to-1024-mb

Due to the mentioned RAM issue, Whonix-Workstation might freeze. In that case, increase VM RAM.

Download links can be found here:
https://www.whonix.org/wiki/VirtualBox_Testers_Only_Version

Testers Wanted!

Release Notes:
https://www.whonix.org/wiki/Whonix_Release_Notes#Whonix_14

[Help Welcome] KVM Development - staying the course
#2

Everything is good and connection works flawlessly. anon-cnnection wizard looks sexy. Thanks @iry!

whonixcheck on GW complains that QEMU is unsupported although its KVM. So users might be needlessly alarmed.

ERROR: Virtualizer qemu unsupported by Whonix developers! Whonixcheck aborted! (qubes_detected: false)
Using Virtualizer qemu together with Whonix is recommended against, because it is rarely tested. [1] [2] [3]
It could be made possible, but would require more Whonix contributors.
It may already work, but is highly experimental.
This might endanger your anonymity. Do not proceed unless you know what you are doing.
If you wish to ignore this warning and to continue whonixcheck anyway, you can set
WHONIXCHECK_NO_EXIT_ON_UNSUPPORTED_VIRTUALIZER="1"
in /etc/whonix.d/30_whonixcheck_default.conf.
Recommended action:

  • Shut down.
  • Read Whonix documentation [4].
  • Use Whonix with a supported virtualizer or Physical Isolation [5].
#3

Should be easily fixable.

Can you confirm the output of

echo "$(systemd-detect-virt)"

is

qemu

?

Can you confirm the output of

echo "'$(systemd-detect-virt)'"

is

'qemu'

?

#4

Please try if this fix works for you. (If so, my above question is void.)

(Full file available from master https://github.com/Whonix/whonixcheck/blob/master/usr/lib/whonixcheck/check_virtualizer.bsh)

If it works, it will be included in next Whonix testers-only version.

#5

Shared folders seems to be broken. While a folder named after the mount point is visible, nothing from the host shows up in it. It could be that I’m not familiar with a new path that it was changed to when the feature was revamped by Jason

#6

Yep

#7

When talking to Debian servers apt fetches from onions and clearnet. Seems redundant. Is this the correct behavior or did you forget to remove clearnet repo links?

#8

Yes, intended. We’re making a wide scale testing of apt-get onion with Whonix 14.

If they’re not flaky, Whonix 15 will use onions and drop clearnet whenever possible.

#9

I see but you won’t be able to test it that way since every package I installed always got pulled from the clearnet mirror exclusively.

From my experience using Onionized apt only for almost a year now, the Debian servers have never disappointed.

#10

I can second that. But don’t know if those servers have the capacity to handle an influx of all Whonix users.

#11

What if you swap onion and clearnet lines in sources.list? Does it prefer onions over clearnet then?

#12

Yes it does!

#13

Right, so we ought to swap them.

#14
#15

Thanks for the update on the GW after running sudo apt-update && sudo apt-get dist-upgrade - and rebooting I get a message No command arguments supplied! Usage: kdesudo [-u ] KdeSudo will now exit…

Just ran a new instance of the WS same message

I have only run the update - using the testers repo and changed passwords?

[graphical gui] Whonix Setup Wizard / Anon Connection Wizard - Technical Discussion
#16

It’s about auto starting anon-connection-wizard. Or not. So in worst case a usability bug. No security involved.

Not clear how that could happen. We checked all the related code and added some safeguards against this which will end up in updates and the next release.

#17

Multiple users are affected by this.

#18

HulaHoop:

Shared folders seems to be broken. While a folder named after the mount point is visible, nothing from the host shows up in it. It could be that I’m not familiar with a new path that it was changed to when the feature was revamped by Jason

No changes where done.

Is package shared-folder-help installed?

/lib/systemd/system/mnt-shared-vbox.service was removed since no longer
needed. Unrelated to KVM.

/lib/systemd/system/mnt-shared-kvm.service is untouched.

It’s all there is.

#19

I figured out why: start condition failed - conditionvirtualization=kvm as not met

#20

Could you please fix this so this can find its way into the next (and perhaps final before release) build?