Apple MacBook Troubleshooting

MacBook Air 13” mid 2011 (MacBookAir 4,2)

In this section, I explain how to install Qubes on a MacBook Air 13” mid 2011 (MacBookAir 4,2).

This model has the following features:

  • Dual Intel i7-2677M 1.80 Ghz CPU (2 dual cores)
  • Intel HD Graphics 3000
  • 4Gb RAM
  • 256Gb SDD
  • Broadcom BCM43224 802.11 a/b/g/n wifi and Bluetooth adapter
  • Intel DSL2310 Thunderbolt controller
  • It has 1 DVI/Thunderbolt display port, 2 USB2.0 ports, a Magsafe power adapter, a standard 3.5mm audio jack and SD reader.

I first tried to install Qubes using the UEFI boot, but it failed. Not wanting to waste too much time, I quickly opted for the legacy BIOS install.

1. Boot from Mac OS X (or Internet Recovery Image with CMD+R during bootup)

Run in a terminal [1]:

# diskutil list
(find your usb device)
# bless –device /dev/diskX –legacy –setBoot –nextonly  # bless the disk not the partition
# reboot

Insert your Qubes 3.2 USB flash drive. The ISOLINUX boot screen should come up. Install Qubes normally.

If you try to boot Qubes now, it will freeze while “setting up networking.” You need to put the Broadcom wireless device into PCI passtrough [2,3]. Or, as an alternative remove it from your Mac and Qubes will boot up smoothly. If you choose to remove the card, jump to step 3.

2. Boot from Mac OS X again

Run in a terminal:

# diskutil list
(find your usb device)
# bless –device /dev/diskX –legacy –setBoot –nextonly  # bless the disk not the partition
# reboot

Insert your Qubes 3.2 USB flash drive. The ISOLINUX boot screen should come up. Select Troubleshooting and Boot the Rescue image. Enter your disk password when prompted. Select continue and after mounting the HD filesystem and launching a shell, chroot as instructed.

Then find your Bluetooth card:

# lspci
02:00.0 Network controller: Broadcom Corporation BCM43224 802.11a/b/g/n (rev 01)
# qvm-pci -a sys-net 02:00.0 # this assigns the device to sys-net VM

Then create /etc/systemd/system/qubes-pre-netvm.service with:

Description=Netvm fix for Broadcom

ExecStart=/bin/sh -c 'echo 02:00.0 > /sys/bus/pci/drivers/pciback/permissive'



systemctl enable qubes-pre-netvm.service

And that’s it.

3. After reboot, boot Mac OS X again

Run in a terminal:

# diskutil list
(find the HD device where you installed Qubes)
# bless –device /dev/diskX –legacy –setBoot  # bless the disk not the partition
# reboot


  • System booted and running smoothly
  • Youtube video: OK (including full screen after configuration)
  • Trackpad: OK
  • Audio control: OK
  • Brightness control: OK
  • Keyboard light control:OK
  • SD card access: OK (tested at dom0)
  • Lid-close suspend: OK
  • Wifi: +10%-20% ICMP packet loss when comparing with OSX (have similar rates with tails Linux, more tests are required)



MacBook Air 2012 (MacBookAir 5,1)

Please see this thread o the qubes-devel mailing list.

MacBook Pro Retina, 15 inch, Mid-2015 (MacBookPro 11,5)

In this section, I explain how I installed Qubes 3.2 on a MacBook Pro Retina 2015 (MacBookPro 11,5). Good news: the relevant stuff works. Bad news: still some minor issue to investigate.

For the time being, my setup is just for testing purposes and help to bypass some blocking issues: do not use it in production or on machine where security is a concern! I hope to improve it as soon as possible.

During my nigths trying to get Qubes OS working, I faced tow main and blocking issues:

  • no boot, due to empty xen.cfg file
  • system freeze, due to Broadcom BCM43602 wifi card

I am already using Qubes for my daily job on Intel NUC. For the time being, I installed Qubes on Macbook for test purposes. Later on I will review the security implications.

This model has the following features:

  • 2,5 GHz Intel Core i7-4870HQ (2 quad cores)
  • Dual Graphic Card
    • Intel Iris Pro
    • AMD Radeon R9 M370X
  • 16Gb RAM
  • 512Gb SDD
  • Broadcom BCM43602 802.11ac wifi adapter

1. Reclaim space to be able to multiboot OSX

For security reasons, you should install Qubes using the whole disk. I preferred to keep OSX, so I shrunk OS partition:

  • reboot in recovery mode
  • run disk utility and shrink OSX partition, eg 150GB for OSX and the remaining space for Qubes OS
  • reboot

2. Boot installer

Download and prepare a USB with Qubes 3.2

You can install Qubes using BIOS or UEFI:

  • BIOS/CSM/Legacy: I have not been able to install using legagy, but I did not spent a lot of time on it.
  • UEFI plain: grub menu appears, but any gave me a quick flash and returned the main menu. I can boot it manually fixing the grub.cfg file, adding commands linuexefi and initrdefi, pointing proper files in /efi/boot. After boot, I end up with not root file system.
  • UEFI, using rEFInd: I have been successful, despite some issues to be fixed manually, after installation completion
    • download rEFInd this file is not signed, so decide if you trust it or not. SHA1 sum is 3d69c23b7d338419e5559a93cd6ae3ec66323b1e
    • unzip it and run installer, which install rEFIind on the internal SSD
    • if installation fails due to SIP, reboot in recovery mode, open a terminal and issue command
      crsutil disable
    • reboot and you will see some icons
    • choose Boot EFI\BOOT\xen.efi from ANACONDA
    • after a will the graphical installer is up and running, with keyboard and touchpad working

### 3. Installation

  • As a general rule, keep the default values proposed during installation: you will change them later on
  • Keep English, as language, locale
  • My macbook has a US keyboard, so I cannot say what happens if you change keyboard layout
  • DO NOT CHANGE the timezone, because it will trigger the wifi card, leading to a system freeze
  • Choose the “installation destination”: do not change anything and press DONE button
  • Insert your password for Full Disk Encryption
  • If you do not already have free space on internal SSD disk, you will be prompted to reclaim some space:
  • If you shrunk OSX partition, disk utility left an empy partition: delete useless partition (eg: if you shrunk OSX parition, diskutil created an empty partition)
  • Press on “reclaim space”
  • Press on “begin installation”
  • create your user and password
  • after a while, installation completes
  • DO NOT press “Reboot button”

Qubes OS is now installed, but you cannot boot it due to some issues, with bootloader configuration and wifi card. You cannot Qubes boot using EFI/qubes/xen.efi because XEN bootloader configuration is broken. You cannot even Qubes without XEN support, using GRUB2, because its configuration is broken too.

Let’s fix it manually, switch to console, pressing Fn+CTRL+ALT+F2

4. Fix GRUB configuration

You can skip this section, but I found it very useful - during troubleshooting - to have a rescue system at hand. I could boot Qubes, without XEN support

Grub configuration file is using some wrong commands, which are not compatible with grub2-efi

chroot /mnt/sysimage
sed -i.bak -e "s/multiboot/chainloader/" -e "s/module.*--nounzip/initrdefi/" -e "s/module/linuxefi/" /etc/grub.d/20_linux_efi

Now, despite XEN configuration is still broken, you have a rescue system booting vmlinux from rEFInd screen. TBV1: chainloading XEN does not work, unless you specify the right disk prefix, eg: (hd1,gpt4) TBV2: grub.cfg set the wrong disk in “set root” command TBV3: in case you reach grub shell, you can


and also reload config file and change it manualy before booting

configfile /EFI/qubes/grub.cfg

then press “e”, edit grub cfg and boot pressing Fn+F10

5. Fix bootloader

  • Fix grub2 configuration, which uses wrong command for EFI boot
  • analyzing /mnt/sysimage/var/log/anaconda/program.log I found the faulty commands issues by Anaconda installer
    chrooot /mnt/sysimage
  • edit /boot/efi/EFI/qubes/xen.cfg file putting the following content ~~~ [global] default=4.4.14-11.pvops.qubes.x868_64

[4.4.14-11.pvops.qubes.x868_64] options=loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M kernel=vmlinuz-4.4.14-11.pvops.qubes.x86_64 ramdisk=initramfs-4.4.14-11.pvops.qubes.x86_64.img

*  The main mistake is the efibootmgr, that needs the right commands. Just in case, re-apply all the commands, adapting to your own disk layout (-d /dev/sdxxx -p partition_number)

grep Running /mnt/sysimage/var/log/anaconda/program.log | tail -n 20 efibootmgr -b 0000 -B efibootmgr -c -w -L Qubes -d /dev/sda -p 4 -l \EFI\qubes\xen-4.6.1.efi /usr/libexec/mactel-boot-setup kernel-install add 4.4.14-11.pvops.qubes.x86_64 /boot/vmlinuz-4.4.14-11.pvops.qubes.x86_64 systemctl disable qubes-netvm reboot

At rEFInd screen, choose Boot EFI/qubes/xen-4.6.1.efi
Everything should now be ok, Qubes OS boots using EFI and you will get the last setup screen
*  select "Qubes OS", do not change anything and click on "Done"
*  VMs are created, including NetVM

### 6. Fix pulseaudio, which locks CPU freezing the system often for 20 seconds

My macbook has frequent freezes. Looking at journalctl output I saw that pulseaudio locks CPU for 20 seconds, very often.

You can fix this issue, killing audio support with this quick workaround:
*  open a dom0 terminal, as root and edit /etc/pulse/client.conf
*  add "autospawn = no"
*  Then, as normal user, issue command "pulseaudio --kill"

### 7. Fix system freezes due to Broadcom BCM43602

*  If you experiences a system freeze, during VM setup, force a reboot and press OPTION key. 
   *  You will reach grub shell

configfile /EFI/qubes/grub.cfg

   press Fn+F10 to boot without XEN support
   *  Once booted, press Fn+CTRL+ALT+F4 to open a shell
   *  Log into system

sudo su - systemctl disable qubes-netvm

   Press Fn+F2 and complete setup
*  reboot and you finally have your Qubes OS
*  DO NOT launch sys-net machine
*  Open its setting and remove wifi adapter from the Selected devices, using Qubes Manager or use the following command line. Get the BFD of the adapter and remove it. On my macbook BFD is 04:00.0 and you will use it later on, also

qvm-pci -l sys-net qvm-pci -d sys-net 04:00.0

Ok, setup is complete and we are almost done.
* Open a dom0 terminal

sudo su - xl pci-assignable-list echo 04:00.0 > /sys/bus/pci/drivers/pciback/permissive qvm-start sys-net xl pci-attach sys-net 04:00.0 ~~~

This latest steps are required to launch sys-net with wifi access. They can be automated in a custom systemd service