Whonix on Mac M1 (ARM) - User Support (still unsupported at time of writing)

That is really complex. Not your suggestion but overall secure network time synchronization design is really complex.

This chapter might explain it best.

To discuss this further, please open a dedicated forum thread for that or use sdwdate and sdwdate-gui development thread.

That should probably be the default.

Funny thing, it is the default in Qemu according to what I read, and there is not mention of the setting in the UTM plist file for Whonix to change it. I guess it is something UTM changed in their code for the bundled qemu helper?

Will look at the info for swdate you linked, thank you.

1 Like

OK, this is odd. I do not see anything in the plists for Whonix about time, but in the qemu options it shows -rtc base=localtime being passed to qemu. I have no idea where this setting is coming from. I was able to add -rtc base=utc, but it seems like a bad solution to have both settings passed to qemu. I will contact UTM developer and see if it is something he puts in.

EDIT:
There is already an issue with UTM project for this. https://github.com/utmapp/UTM/issues/3104

1 Like

Hi could anyone share the UTM files for whonix gateway and workstation please? Thank you :slight_smile:

Maybe ready image for all?

I built version 16.0.2.8 and still have the gz files for UTM.

https://drive.google.com/file/d/1g5N0XLtonNCvuQAgyQNjV_oQth2ZBe7x/view?usp=sharing
https://drive.google.com/file/d/1ehN5UzMT-um80Xg0P2keDmcQnzgSp8kj/view?usp=sharing

For there to be ready images, someone trusted by the developers and therefore the community would need to sign the builds. Otherwise, someone could put anything in the built images.

3 Likes

thank you all for this amazing build, I also got it working in mac M1 with UTM

1 Like

You are the best :+1: :+1: :+1: Thank you

1 Like

Hey! Thanks for the images, they are working. But I have another question, how to start Tor Browser in Workstation? At startup, an error occurs that the arm architecture does not support sse2 instructions.

I also tried to install the version for arm using the tor-deb-repo instruction on the Tor website, but at the moment of sudo apt update, an error occurs.

I can’t beat her. Are there any other ways to get Tor up and running?

Please kindly do not accidentally substitute Tor for a question related to Tor Browser, as this causes confusion.

Please review:

βˆ’ -device virtio-net-pci,netdev=external
-device virtio-net-pci,netdev=internal \ -device virtio-net-pci,netdev=internal
βˆ’ -netdev user,id=external,ipv6=off,net=10.0.2.0/24 \ + -netdev socket,id=internal,connect=:8010
βˆ’ -netdev socket,id=internal,listen=:8010 \

Grenmill (talk | contribs | block) rollback 1 edit

Workstation should connect to Gateway socket, not listen. Also it should not have external network

I just ran update-torbrowser in the terminal. This will download the latest M1 build of torbrowser bundle and install it. You can run it periodically to check for an update.

WARNING: The update script will wipe out your entire browser settings, so if you customize settings you will need to export them and then reimport them upon updating.

This may be a dumb question and I will delete it if so. Am i wrong that UTM can emulate x86 on Apple Silicon albeit at lower performance? Would it not be simpler to run cli gateway on M1 emulating x86? Again sorry if this is too off topic.

You are the best!

Anyone know how to configure discard=on qemu args for the drive in UTM? After importing the VMs the size get thick provisioned to 100+ gb

Has anyone noticed that with UTM the system clock will after time lag behind the correct time. timedatectl will show the correct time for RTC but local time will eventually run behind. I will post a ticket on UTM github just curious if anyone else is seeing this. hwclock -s fixes the issue and I guess I could setup a crontab. heh

I’m trying to build the images in a Debian VM according to the building instructions. When doing

sudo apt-get install git time curl apt-cacher-ng lsb-release fakeroot dpkg-dev fasttrack-archive-keyring

I get the error that the package fasttrack-archive-keyring can’t be located

Whonix 16 needs to be to build on Debian bullseye.

In other words Debian -- Details of package fasttrack-archive-keyring in bullseye needs to be installed as usual using apt, the process of that is unspecific to Whonix.

1 Like

Doing

git clone --depth=1 --branch 16.0.3.7-stable --jobs=4 --recurse-submodules --shallow-submodules https://gitlab.com/whonix/Whonix.git

gives

warning: Could not find remote branch 16.0.3.7-stable to clone.

fatal: Remote branch 16.0.3.7-stable not found in upstream origin

https://www.whonix.org/wiki/Dev/Build_Documentation/VM#Choose_Version