Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2025-07-29 17:49:11 -04:00
Code Issues Projects Releases Packages Wiki Activity

minor formatting & url fix

Browse source
This commit is contained in:
qubedmaiska 2025-03-26 17:20:33 -04:00
parent cbf4baa9c6
commit 66c0baff53
No known key found for this signature in database
GPG key ID: 204BCE0FD52C0501
2 changed files with 5 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

4
user/advanced-topics/secondary-storage.md
View file

@ -62,7 +62,7 @@ In theory, you can still use file-based disk images ("file" pool driver), but it
### Example HDD setup
Assuming the secondary hard disk is at /dev/sdb (it will be completely erased), you can set it up for encryption by doing in a dom0 terminal (use the same passphrase as the main Qubes disk to avoid a second password prompt at boot):
Assuming the secondary hard disk is at `/dev/sdb` (it will be completely erased), you can set it up for encryption by doing in a dom0 terminal (use the same passphrase as the main Qubes disk to avoid a second password prompt at boot):
```
sudo cryptsetup luksFormat --hash=sha512 --key-size=512 --cipher=aes-xts-plain64 --verify-passphrase /dev/sdb
@ -81,7 +81,7 @@ And adding this line (change both "b209..." for your device's UUID from blkid) t
luks-b20975aa-8318-433d-8508-6c23982c6cde UUID=b20975aa-8318-433d-8508-6c23982c6cde none
```
Reboot the computer so the new luks device appears at /dev/mapper/luks-b209... and we can then create its pool, by doing this on a dom0 terminal (substitute the b209... UUIDs with yours):
Reboot the computer so the new luks device appears at `/dev/mapper/luks-b209...` and we can then create its pool, by doing this on a dom0 terminal (substitute the "b209..." UUIDs with yours):
First create the physical volume

8
user/advanced-topics/standalones-and-hvms.md
View file

@ -202,7 +202,7 @@ as is, then any HVMs based on it will effectively be disposables. All file
system changes will be wiped when the HVM is shut down.
Please see [this
page](https://github.com/Qubes-Community/Contents/blob/master/docs/os/windows/windows-tools.md)
page](/doc/templates/windows/windows-qubes-4-1/#windows-as-a-template)
for specific advice on installing and using Windows-based templates.
## Cloning HVMs
@ -366,9 +366,7 @@ device again. This is illustrated in the screenshot below:
You can convert any VirtualBox VM to a Qubes HVM using this method.
For example, Microsoft provides [free 90-day evaluation VirtualBox VMs for
browser
testing](https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/).
For example, Microsoft provides [virtual machines containing an evaluation version of Windows](https://developer.microsoft.com/en-us/windows/downloads/virtual-machines/).
About 60 GB of disk space is required for conversion. Use an external hard
drive if needed. The final `root.img` size is 40 GB.
@ -447,5 +445,5 @@ qemu-img -h | tail -n1
Other documents related to HVMs:
- [Windows VMs](https://github.com/Qubes-Community/Contents/blob/master/docs/os/windows/windows-vm.md)
- [Windows VMs](https://forum.qubes-os.org/search?q=windows%20hvm%20%23guides)
- [Linux HVM Tips](https://forum.qubes-os.org/t/19008)