~~~ -> ```

For `.adoc` compatibility
This commit is contained in:
awokd 2018-10-14 12:10:59 +00:00 committed by GitHub
parent a879175625
commit f17a44470c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -16,9 +16,9 @@ Set `xpti=false` option in Xen command line (xen.gz option in grub, or options=
### How can I switch R4.0 stubdomains back to qemu-traditional? ### How can I switch R4.0 stubdomains back to qemu-traditional?
~~~ ```
qvm-features VMNAME linux-stubdom '' qvm-features VMNAME linux-stubdom ''
~~~ ```
### How can I upgrade to testing? ### How can I upgrade to testing?
@ -36,7 +36,7 @@ For that, under debian/whonix do: `sudo apt-get check && sudo apt-get update -t
Make a dom0 script with the following: Make a dom0 script with the following:
~~~ ```
#!/bin/sh #!/bin/sh
for domain in $(qvm-ls --fields NAME,CLASS | \ for domain in $(qvm-ls --fields NAME,CLASS | \
@ -45,7 +45,7 @@ for domain in $(qvm-ls --fields NAME,CLASS | \
done done
sudo qubes-dom0-update sudo qubes-dom0-update
~~~ ```
From https://gist.github.com/JimmyAx/818bcf11a14e85531516ef999c8c5765. From https://gist.github.com/JimmyAx/818bcf11a14e85531516ef999c8c5765.
See also the scripts listed under [`OS-administration`](https://github.com/Qubes-Community/Contents/tree/master/code). See also the scripts listed under [`OS-administration`](https://github.com/Qubes-Community/Contents/tree/master/code).
@ -58,11 +58,11 @@ But this thin volume is actually there.
Also the volume `vm-test-private-snap` is still present. Also the volume `vm-test-private-snap` is still present.
Try this in dom0: Try this in dom0:
~~~ ```
sudo pvscan --cache --activate ay sudo pvscan --cache --activate ay
sudo systemctl restart qubesd sudo systemctl restart qubesd
qvm-start test qvm-start test
~~~ ```
### Slow VM startup ### Slow VM startup
@ -70,10 +70,10 @@ Use tools like 'systemd-analyze blame' as your guide.
Another service that shows up with significant time is wpa_supplicant. Another service that shows up with significant time is wpa_supplicant.
You can have it start only for network VMs by creating `/lib/systemd/system/wpa_supplicant.service.d/20_netvms` with the following: You can have it start only for network VMs by creating `/lib/systemd/system/wpa_supplicant.service.d/20_netvms` with the following:
~~~ ```
[Unit] [Unit]
ConditionPathExists=/var/run/qubes/this-is-netvm ConditionPathExists=/var/run/qubes/this-is-netvm
~~~ ```
### Xen passthrough compatible video cards ### Xen passthrough compatible video cards
@ -184,14 +184,15 @@ Alternatively you can increase the size afterwards with `mount -o remount,size=5
If you need to have a disk based tmp you'll have to mask the systemd unit (`systemctl mask tmp.mount`) and put a fstab entry for /tmp. If you need to have a disk based tmp you'll have to mask the systemd unit (`systemctl mask tmp.mount`) and put a fstab entry for /tmp.
Alternatively you can add swap with a file inside the vm but it's a bit ugly: Alternatively you can add swap with a file inside the vm but it's a bit ugly:
~~~ ```
dd if=/dev/zero of=swapfile bs=1M count=1000 dd if=/dev/zero of=swapfile bs=1M count=1000
mkswap swapfile mkswap swapfile
swapon swapfile swapon swapfile
~~~ ```
### How do I attach an `.img` file to a Qube? ### How do I attach an `.img` file to a Qube?
```
# a file cannot be attached if it is in directory /var/lib/qubes/appvms, so create a link first # a file cannot be attached if it is in directory /var/lib/qubes/appvms, so create a link first
ln /var/lib/qubes/appvms/$1/private.img /home/user/private.img ln /var/lib/qubes/appvms/$1/private.img /home/user/private.img
LOOPDEV=`sudo losetup -f` LOOPDEV=`sudo losetup -f`
@ -203,6 +204,7 @@ swapon swapfile
qvm-block detach backupvm dom0:$(basename "$LOOPDEV") qvm-block detach backupvm dom0:$(basename "$LOOPDEV")
sudo losetup -d $LOOPDEV sudo losetup -d $LOOPDEV
rm /home/user/private.img rm /home/user/private.img
```
See https://groups.google.com/d/msg/qubes-users/LLSo_3oWXJI/0clWN0BUBgAJ for more details. See https://groups.google.com/d/msg/qubes-users/LLSo_3oWXJI/0clWN0BUBgAJ for more details.
@ -267,7 +269,7 @@ You can just edit that file to remove them from the list.
You only get one resolution at a time. You only get one resolution at a time.
In the HVM's `/etc/X11/xorg.conf`, in Subsection "Display" for Depth 24, make a single mode like this: In the HVM's `/etc/X11/xorg.conf`, in Subsection "Display" for Depth 24, make a single mode like this:
~~~ ```
... ...
Subsection "Display" Subsection "Display"
Viewport 0 0 Viewport 0 0
@ -275,7 +277,7 @@ In the HVM's `/etc/X11/xorg.conf`, in Subsection "Display" for Depth 24, make a
Modes "1200x800" Modes "1200x800"
EndSubSection EndSubSection
EndSection EndSection
~~~ ```
Only some modes will work. check wikipedia. if your host display is Only some modes will work. check wikipedia. if your host display is
1080p(1920x1080), then an hvm at 1440x900 works well. if its more than that, might 1080p(1920x1080), then an hvm at 1440x900 works well. if its more than that, might
@ -290,7 +292,7 @@ Either use a 3.5mm jack to BT adapter, or see [this](https://m7i.org/tips/qubes-
Note: See the [official documentation](https://www.whonix.org/wiki/Qubes/Install) for supported installation methods. Note: See the [official documentation](https://www.whonix.org/wiki/Qubes/Install) for supported installation methods.
There should be no need to complete the following procedure manually any more. There should be no need to complete the following procedure manually any more.
~~~ ```
sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable qubes-core-admin-addon-whonix sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable qubes-core-admin-addon-whonix
sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable qubes-template-whonix-gw-14 sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable qubes-template-whonix-gw-14
@ -306,21 +308,21 @@ qvm-prefs whonix-ws-dvm-14 template_for_dispvms true
qvm-prefs whonix-ws-dvm-14 netvm sys-whonix-14 qvm-prefs whonix-ws-dvm-14 netvm sys-whonix-14
qvm-prefs whonix-ws-dvm-14 default_dispvm whonix-ws-dvm-14 qvm-prefs whonix-ws-dvm-14 default_dispvm whonix-ws-dvm-14
qvm-tags whonix-ws-14 a whonix-updatevm qvm-tags whonix-ws-14 a whonix-updatevm
~~~ ```
To use the new `sys-whonix-14` for your UpdateVM, perform the following steps: To use the new `sys-whonix-14` for your UpdateVM, perform the following steps:
~~~ ```
qubes-prefs updatevm sys-whonix-14 qubes-prefs updatevm sys-whonix-14
~~~ ```
Then, edit `/etc/qubes-rpc/policy/qubes.UpdatesProxy` and modify the top lines: Then, edit `/etc/qubes-rpc/policy/qubes.UpdatesProxy` and modify the top lines:
~~~ ```
$type:TemplateVM $default allow,target=sys-whonix $type:TemplateVM $default allow,target=sys-whonix
$tag:whonix-updatevm $default allow,target=sys-whonix $tag:whonix-updatevm $default allow,target=sys-whonix
~~~ ```
to become: to become:
~~~ ```
$type:TemplateVM $default allow,target=sys-whonix-14 $type:TemplateVM $default allow,target=sys-whonix-14
$tag:whonix-updatevm $default allow,target=sys-whonix-14 $tag:whonix-updatevm $default allow,target=sys-whonix-14
~~~ ```