mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2025-01-26 22:37:17 -05:00
Remove deprecated 3.2 content and update links
QubesOS/qubes-issues#4936
This commit is contained in:
Andrew David Wong
parent
34cd422b77
commit
5aeed39c83
@ -329,7 +329,7 @@ In your TemplateVMs, open a terminal and run `sudo dnf upgrade`.
|
||||
|
||||
### How do I run a Windows HVM in non-seamless mode (i.e., as a single window)?
|
||||
|
||||
Enable "debug mode" in the qube's settings, either by checking the box labeled "Run in debug mode" in the Qubes VM Manager qube settings menu or by running the [qvm-prefs command](/doc/dom0-tools/qvm-prefs/).)
|
||||
Enable "debug mode" in the qube's settings, either by checking the box labeled "Run in debug mode" in the Qubes VM Manager qube settings menu or by running the `qvm-prefs` command.
|
||||
|
||||
### I created a usbVM and assigned usb controllers to it. Now the usbVM wont boot.
|
||||
|
||||
@ -360,7 +360,7 @@ Errors suggesting this issue:
|
||||
|
||||
Another solution would be to set the pci_strictreset option in dom0:
|
||||
|
||||
- In Qubes R4.x, when attaching the PCI device to the VM (where `<BDF>` can be obtained from running [qvm-pci](/doc/dom0-tools/qvm-pci/)):
|
||||
- In Qubes R4.x, when attaching the PCI device to the VM (where `<BDF>` can be obtained from running `qvm-pci`):
|
||||
|
||||
qvm-pci attach --persistent --option no-strict-reset=true usbVM dom0:<BDF>
|
||||
|
||||
@ -369,7 +369,7 @@ Another solution would be to set the pci_strictreset option in dom0:
|
||||
qvm-prefs usbVM -s pci_strictreset false
|
||||
|
||||
These options allow the VM to ignore the error and the VM will start.
|
||||
Please review the notes on [this page](/doc/Dom0Tools/QvmPrefs/) and [here](/doc/assigning-devices/) and be aware of the potential risks.
|
||||
Please review the notes in the `qvm-prefs` man page and [here](/doc/assigning-devices/) and be aware of the potential risks.
|
||||
|
||||
### I assigned a PCI device to a qube, then unassigned it/shut down the qube. Why isn't the device available in dom0?
|
||||
|
||||
@ -430,7 +430,7 @@ For Fedora:
|
||||
|
||||
### How do I access my external drive?
|
||||
|
||||
The recommended approach is to pass only the specific partition you intend to use from [`sys-usb`](/doc/usb/) to another qube via [qvm-block](/doc/dom0-tools/qvm-block/). They will show up in the destination qube as `/dev/xvd*` and must be mounted manually. Another approach is to attach the entire USB drive to your destination qube. However, this could theoretically lead to an attack because it forces the destination qube to parse the device's partition table. If you believe your device is safe, you may proceed to attach it.
|
||||
The recommended approach is to pass only the specific partition you intend to use from [`sys-usb`](/doc/usb/) to another qube via `qvm-block`. They will show up in the destination qube as `/dev/xvd*` and must be mounted manually. Another approach is to attach the entire USB drive to your destination qube. However, this could theoretically lead to an attack because it forces the destination qube to parse the device's partition table. If you believe your device is safe, you may proceed to attach it.
|
||||
|
||||
In Qubes 4.0, this is accomplished with the Devices Widget located in the tool tray (default top right corner, look for an icon with a yellow square). From the top part of the list, click on the drive you want to attach, then select the qube to attach it to. Although you can also attach the entire USB device to a qube by selecting it from the bottom part of the list, in general this approach should not be used because you are exposing the target qube to unnecessary additional attack surface.
|
||||
|
||||
|
||||
@ -18,7 +18,7 @@ Although resolved in R4.0 and higher with the switch to scrypt, it is *strongly
|
||||
With Qubes, it's easy to back up and restore your whole system, as well as to migrate between two physical machines.
|
||||
|
||||
As of Qubes R2B3, these functions are integrated into the Qubes VM Manager GUI.
|
||||
There are also two command-line tools available which perform the same functions: [qvm-backup](/doc/dom0-tools/qvm-backup/) and [qvm-backup-restore](/doc/dom0-tools/qvm-backup-restore/).
|
||||
There are also two command-line tools available which perform the same functions: `qvm-backup` and `qvm-backup-restore`.
|
||||
|
||||
|
||||
Creating a Backup (R4.0 and later)
|
||||
|
||||
@ -33,22 +33,14 @@ GUI
|
||||
CLI
|
||||
---
|
||||
|
||||
```
|
||||
qvm-copy-to-vm [--without-progress] dest_vmname file [file]+
|
||||
```
|
||||
|
||||
Also see: [qvm-copy-to-vm](/doc/vm-tools/qvm-copy-to-vm/)
|
||||
|
||||
|
||||
Qubes 4.0
|
||||
---------
|
||||
|
||||
In Qubes 4.0, qvm-copy-to-vm and qvm-move-to-vm are deprecated (GUI behaviour is unchanged from Qubes 3.2). In the command line, use qvm-copy or qvm-move to avoid typing target qube name twice.
|
||||
|
||||
```
|
||||
qvm-copy [--without-progress] file [file]+
|
||||
```
|
||||
|
||||
```
|
||||
qvm-move [--without-progress] file [file]+
|
||||
```
|
||||
|
||||
|
||||
On inter-qube file copy security
|
||||
----------------------------------
|
||||
|
||||
@ -24,7 +24,7 @@ In case of template-based qubes, the private storage (the /home directory and us
|
||||
If you are increasing the disk image size for Linux-based qubes installed from Qubes OS repositories in Qubes 4.0 or later, changing the settings above is all you need to do - in other cases, you may need to do more, according to instructions below.
|
||||
See also [OS Specific Follow-up Instructions](/doc/resize-disk-image/#os-specific-follow-up-instructions) at the end of this page.
|
||||
|
||||
### Resize disk image (R4.0)
|
||||
### Resize disk image
|
||||
|
||||
Use either GUI tool Qube Settings (`qubes-vm-settings`) or the CLI tool `qvm-volume`.
|
||||
Maximum size which can be assigned through Qube Settings is 1048576 MiB - if you need more, use `qvm-volume`:
|
||||
@ -50,59 +50,6 @@ If you are **not** using Linux in the qube, you will also need to:
|
||||
3. Verify available space in the template using `df -h` or OS specific tools.
|
||||
4. Shutdown the template.
|
||||
|
||||
### Template disk image (R3.2)
|
||||
|
||||
If you want install a lot of software in your TemplateVM, you may need to increase the amount of disk space your TemplateVM can use.
|
||||
*Make sure changes in the TemplateVM between reboots don't exceed 10G.*
|
||||
|
||||
1. Make sure that all the VMs based on this template are shut down (including netvms etc).
|
||||
2. Resize the *root image* using the procedure below.
|
||||
3. If any netvm/proxyvm used by this template is based on it, set template's netvm to none.
|
||||
4. Start the template.
|
||||
5. Resize the filesystem using OS appropriate tools (Linux is `sudo resize2fs /dev/mapper/dmroot`).
|
||||
6. Verify available space in the template using `df -h` or OS specific tools.
|
||||
7. Shutdown the template.
|
||||
8. Restore original netvm setting (if changed), and check firewall settings (setting netvm to none causes the firewall to reset to "block all")
|
||||
|
||||
### Expand disk image (R3.2)
|
||||
|
||||
1048576 MB is the maximum size which can be assigned to storage through Qubes Manager.
|
||||
|
||||
To grow the private disk image of an AppVM beyond this limit, `qvm-grow-root` or [qvm-grow-private](/doc/dom0-tools/qvm-grow-private/) can be used:
|
||||
|
||||
~~~
|
||||
qvm-grow-root <vm-name> <size>
|
||||
~~~
|
||||
OR
|
||||
~~~
|
||||
qvm-grow-private <vm-name> <size>
|
||||
~~~
|
||||
|
||||
Note: Size is the target size (i.e. 4096MB or 16GB, ...), not the size to add to the existing disk.
|
||||
|
||||
### Resize a StandaloneVM Root Image
|
||||
|
||||
For more flexibility, you may also turn your Template into a Standalone qube.
|
||||
Doing this means it will have its own root filesystem *(Standalone qubes use a copy of the template, instead of smart sharing)*.
|
||||
To do this run `qvm-create --standalone` from `dom0` console, then perform the [OS Specific Follow-up Instructions](/doc/resize-disk-image/#os-specific-follow-up-instructions) below.
|
||||
|
||||
### Shrinking a disk image
|
||||
|
||||
Ext4 and most other filesystems do not support online shrinking, so it can't be done as conveniently as growing the image.
|
||||
Note that we don't want to touch the VM filesystem directly in dom0 for security reasons.
|
||||
|
||||
1. Create a new qube with smaller disk using Qube Manager or `qvm-create`
|
||||
2. Move data to the new qube using `qvm-copy`, backup & restore, or OS utilities
|
||||
3. Delete old qube using Qube Manager or `qvm-remove`
|
||||
|
||||
OS Specific Follow-up Instructions
|
||||
-----------------
|
||||
|
||||
In the case of Linux-based qubes installed from Qubes repositories, no further actions are required.
|
||||
In some other cases, after expanding volumes, the partition table and file-system may need to be adjusted.
|
||||
Use tools appropriate to the OS in your qube.
|
||||
Brief instructions for Windows 7, FreeBSD, and Linux are provided below.
|
||||
|
||||
#### Windows 7
|
||||
|
||||
1. Click Start
|
||||
@ -126,3 +73,4 @@ zpool online -e poolname ada0
|
||||
Qubes will automatically grow the filesystem for you on all AppVMs with Qubes packages installed (which are all AppVMs installed from templates, cloned from templates etc. - if you have not created an empty HVM and installed a Linux distribution in it, without using Qubes repositories, you are almost certainly safe).
|
||||
Otherwise, you will see that there is unallocated free space at the end of your primary disk.
|
||||
You can use standard linux tools like `fdisk` and `resize2fs` to make this space available.
|
||||
|
||||
|
||||
@ -33,7 +33,7 @@ QubesDB
|
||||
- `/qubes-timezone - name of timezone based on dom0 timezone. For example `Europe/Warsaw`
|
||||
- `/qubes-keyboard` - keyboard layout based on dom0 layout. Its syntax is suitable for `xkbcomp` command (after expanding escape sequences like `\n` or `\t`). This is meant only as some default value, VM can ignore this option and choose its own keyboard layout (this is what keyboard setting from Qubes Manager does). This entry is created as part of gui-daemon initialization (so not available when gui-daemon disabled, or not started yet).
|
||||
- `/qubes-debug-mode` - flag whether VM has debug mode enabled (qvm-prefs setting). One of `1`, `0`
|
||||
- `/qubes-service/SERVICE_NAME` - subtree for VM services controlled from dom0 (using qvm-service command or Qubes Manager). One of `1`, `0`. Note that not every service will be listed here, if entry is missing, it means "use VM default". List of currently supported services is in [qvm-service man page](/wiki/Dom0Tools/QvmService)
|
||||
- `/qubes-service/SERVICE_NAME` - subtree for VM services controlled from dom0 (using the `qvm-service` command or Qubes Manager). One of `1`, `0`. Note that not every service will be listed here, if entry is missing, it means "use VM default". A list of currently supported services is in the `qvm-service` man page.
|
||||
- `/qubes-netmask` - network mask (only when VM has netvm set); currently hardcoded "255.255.255.0"
|
||||
- `/qubes-ip - IP address for this VM (only when VM has netvm set)
|
||||
- `/qubes-gateway` - default gateway IP (only when VM has netvm set); VM should add host route to this address directly via eth0 (or whatever default interface name is)
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user