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

Unsupported Platforms
413

No.

414

what’s the reason for moving away from utm?

415

Not gonna answer for Patrick, but it seems no one had clearly said we are moving away from UTM. But it would make sense because most of the build that is made for whonix is for virtualbox. Like if you can combine a lot of the config from windows, linux and even previous macos intel that uses virtualbox. Then it would be less hassle to maintain.

1 Like
416

Also as i have understood, no one is maintaining the UTM build that i know off. Sorry not been here in a while so not followed on the project for a while. But there was no one who maintained it when i was here last time.

1 Like
417

Also wanted to point out that if we got this build working you could also run it on fedora asahi Linux on apple silicon which has been the best Linux experience so far for me

418

@Patrick would this command work for building for vbox

~/derivative-maker/derivative-maker --flavor whonix-gateway-xfce --target virtualbox --arch arm64 --repo true

419

It really helps to read a few posts before posting.

420

Any guess how much work itd be @Patrick? My company uses macbooks so i have access to apple silicon. Could give it a whirl, but havent been keeping up in a while. Life has been a lot

Just curious rough estimate of what in derivative maker might be problematic

1 Like
421

No guesses.

1 Like
422

10-4 :heart:

1 Like
423

I understand that the UTM build is no longer being supported but in case people are still using it:

If you are building Whonix-Gateway-CLI from the above script, it won’t run as there is an error (which is easily fixable).

  1. Edit the config.plist file inside Whonix-Gateway-CLI.utm directory
  2. Search for raw and change the line Whonix-Gateway-XFCE.raw to Whonix-Gateway-CLI.raw
  3. Save and exit
  4. Then import Whonix-Gateway-CLI.utm into UTM. It will now work
424

Index of /nightly-builds/tor-browser-builds/tbb-nightly.2024.12.11/nightly-linux-aarch64 aarch64 Tor browser nightly out now! Would this open the possibility of whonix adopting new architecture

425

Well it would at least make the possibility for it when a stable release is coming out maybe. Idk if there are other dependencies that is needed for a new architecture to be adopted? also isnt aarch64 possible to build now? or do you mean like released? like available in binary form.

426

Is it possible to build whonix for arm64 with the same derivative maker command we use for utm but change to qcows so I can run whonix on arm64 Linux?

$ ~/derivative-maker/derivative-maker --flavor whonix-gateway-xfce --target qcow2 --arch arm64 --tb open --repo true --vmsize 15G

427

So got whonix working on fedora asahi Linux with KVM setup. Only thing I have to get working is connecting to the Tor network

428 
[gateway user ~]% systemcheck                            
[ERROR] [systemcheck] check network interfaces Result: network interface eth0 not up!

Recommendation:
Try to manually start Whonix networking.

sudo systemctl restart networking

Or reboot.

Debugging information:
Command
sudo --non-interactive cat /sys/class/net/eth0/carrier
failed.

If this error happens only during upgrading or is transient this error can be safely ignored.

If you know what you are doing, feel free to disable this check.
Create a file /etc/systemcheck.d/50_user.conf and add:
systemcheck_skip_functions+=" check_network_interfaces "
zsh: exit 1     systemcheck

admin@localhost:~/Downloads/derivative-binary/17.1.1.8$ virsh -c qemu:///system net-dumpxml Whonix-External
<network connections='1'>
  <name>Whonix-External</name>
  <uuid>12348314-7b87-440e-9bc6-84650f4c7327</uuid>
  <forward mode='nat'>
    <nat>
      <port start='1024' end='65535'/>
    </nat>
  </forward>
  <bridge name='virbr1' stp='on' delay='0'/>
  <mac address='52:54:00:78:e6:d8'/>
  <ip address='10.0.2.2' netmask='255.255.255.0'>
  </ip>
</network>

admin@localhost:~/Downloads/derivative-binary/17.1.1.8$ virsh -c qemu:///system net-dumpxml Whonix-Internal
<network connections='2'>
  <name>Whonix-Internal</name>
  <uuid>3daed913-ceb6-498e-8e33-e3c06f70821c</uuid>
  <bridge name='virbr2' stp='on' delay='0'/>
  <mac address='52:54:00:1e:42:95'/>
</network>

admin@localhost:~/Downloads/derivative-binary/17.1.1.8$ virsh -c qemu:///system net-list --all
 Name              State    Autostart   Persistent
----------------------------------------------------
 default           active   no          no
 Whonix-External   active   yes         yes
 Whonix-Internal   active   yes         yes

admin@localhost:~/Downloads/derivative-binary/17.1.1.8$ 


[gateway user ~]% sudo ping -c 4 10.0.2.2   

PING 10.0.2.2 (10.0.2.2) 56(84) bytes of data.
64 bytes from 10.0.2.2: icmp_seq=1 ttl=64 time=0.370 ms
64 bytes from 10.0.2.2: icmp_seq=2 ttl=64 time=0.324 ms
64 bytes from 10.0.2.2: icmp_seq=3 ttl=64 time=0.375 ms
64 bytes from 10.0.2.2: icmp_seq=4 ttl=64 time=0.220 ms

--- 10.0.2.2 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3068ms
rtt min/avg/max/mdev = 0.220/0.322/0.375/0.062 ms
[gateway user ~]%

I just can’t get Tor to connect on the gateway anyone have this issue before

429
430

Hello! I’ve built 17.2.9.9 whonix gw for utm target successfully but whonix workstation build progress hangs on 'ERROR: Failed to install '\''dracut' dracut-live dracut-config-generic binutils dmsetup pigz linux-image-arm64 linux-headers-arm64 sbsigntool efibootmgr mokutil keyutils shim-signed-common efivar fwupd fwupd-signed spice-vdagent 'non-qubes-whonix-workstation-xfce'\''. (apt_get_exit_code: 100) Attempting to gather debug output to diagnose the problem...
Tryed 17.2.9.9, 17.2.9.8, 17.2.8.5 w/o any luck

431

The log output is much too short to be able to debug.

432

A post was merged into an existing topic: Whonix on Mac M1 (ARM) - Development Discussion