Remove Qubes 3 instructions from README

See https://www.qubes-os.org/news/2019/03/28/qubes-3-2-has-reached-eol/
This commit is contained in:
Thomas Leonard 2019-04-04 11:04:09 +01:00
parent 3fc9790203
commit bd7babeda0

View File

@ -42,22 +42,6 @@ If you want to deploy manually, unpack `mirage-firewall.tar.bz2` in dom0, inside
The tarball contains `vmlinuz`, which is the unikernel itself, plus a couple of dummy files that Qubes requires. The tarball contains `vmlinuz`, which is the unikernel itself, plus a couple of dummy files that Qubes requires.
### Qubes 3
To configure your new firewall using the Qubes 3 Manager GUI:
- Create a new ProxyVM named `mirage-firewall` to run the unikernel.
- You can use any template, and make it standalone or not. It doesnt matter, since we dont use the hard disk.
- Set the type to `ProxyVM`.
- Select `sys-net` for networking (not `sys-firewall`).
- Click `OK` to create the VM.
- Go to the VM settings, and look in the `Advanced` tab:
- Set the kernel to `mirage-firewall`.
- Turn off memory balancing and set the memory to 32 MB or so (you might have to fight a bit with the Qubes GUI to get it this low).
- Set VCPUs (number of virtual CPUs) to 1.
### Qubes 4
Run this command in dom0 to create a `mirage-firewall` VM using the `mirage-firewall` kernel you added above: Run this command in dom0 to create a `mirage-firewall` VM using the `mirage-firewall` kernel you added above:
``` ```
@ -75,6 +59,8 @@ qvm-create \
mirage-firewall mirage-firewall
``` ```
To upgrade from an earlier release, just overwrite `/var/lib/qubes/vm-kernels/mirage-firewall/vmlinuz` with the new version and restart the firewall VM.
### Configure AppVMs to use it ### Configure AppVMs to use it
You can run `mirage-firewall` alongside your existing `sys-firewall` and you can choose which AppVMs use which firewall using the GUI. You can run `mirage-firewall` alongside your existing `sys-firewall` and you can choose which AppVMs use which firewall using the GUI.