mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2025-01-24 05:31:09 -05:00
Resolve open issues mentioned on Transifex
This commit is contained in:
parent
6b33020140
commit
098f5b418c
@ -459,10 +459,10 @@ In your TemplateVMs, open a terminal and run `sudo dnf upgrade`.
|
||||
|
||||
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.
|
||||
### I created a USB VM and assigned USB controllers to it. Now the USB VM won't boot.
|
||||
|
||||
This is probably because one of the controllers does not support reset.
|
||||
See the [USB Troubleshooting guide](/doc/usb-troubleshooting/#usbvm-does-not-boot-after-creating-and-assigning-usb-controllers-to-it).
|
||||
See the [USB Troubleshooting guide](/doc/usb-troubleshooting/#usb-vm-does-not-boot-after-creating-and-assigning-usb-controllers-to-it).
|
||||
|
||||
### I assigned a PCI device to a qube, then unassigned it/shut down the qube. Why isn't the device available in dom0?
|
||||
|
||||
|
@ -431,11 +431,11 @@ System NetVM
|
||||
|
||||
#### `qvm.sys-usb`
|
||||
|
||||
System UsbVM
|
||||
System USB VM
|
||||
|
||||
#### `qvm.sys-net-with-usb`
|
||||
|
||||
System UsbVM bundled into NetVM. Do not enable together with `qvm.sys-usb`.
|
||||
System USB VM bundled into NetVM. Do not enable together with `qvm.sys-usb`.
|
||||
|
||||
#### `qvm.usb-keyboard`
|
||||
|
||||
|
@ -114,7 +114,7 @@ Maid passphrase to the new configuration. Please consult the Anti Evil Maid
|
||||
|
||||
If you use USB VM, you may encounter problem with starting it on updated Xen
|
||||
version (because of strict default settings). Take a look at
|
||||
[User FAQ](/faq/#i-created-a-usbvm-and-assigned-usb-controllers-to-it-now-the-usbvm-wont-boot)
|
||||
[User FAQ](/faq/#i-created-a-usb-vm-and-assigned-usb-controllers-to-it-now-the-usb-vm-wont-boot)
|
||||
for details.
|
||||
|
||||
Once you have upgraded dom0, you can install new templates from Qubes R3.1
|
||||
|
@ -34,7 +34,7 @@ After attaching a device to a qube, upon attempting to use the device results in
|
||||
|
||||
As a first line of defense, increase the amount of memory given to the USB VM (sys-usb). High-bandwidth devices such as webcams have been [observed](https://github.com/QubesOS/qubes-issues/issues/6200) to need more memory in sys-usb. If increasing the amount of memory does not resolve the issue, check kernel logs within sys-usb as well as the attached qube for errors before filing a bug report.
|
||||
|
||||
## usbVM does not boot after creating and assigning USB controllers to it
|
||||
## USB VM does not boot after creating and assigning USB controllers to it
|
||||
|
||||
This is probably because one of the controllers does not support reset.
|
||||
In Qubes R2 any such errors were ignored. In Qubes R3.x they are not.
|
||||
@ -43,7 +43,7 @@ In R4.x, devices that are automatically added to sys-net and sys-usb on install
|
||||
A device that does not support reset is not ideal and generally should not be assigned to a VM.
|
||||
|
||||
Most likely the offending controller is a USB 3.0 device.
|
||||
You can remove this controller from the usbVM, and see if this allows the VM to boot.
|
||||
You can remove this controller from the USB VM, and see if this allows the VM to boot.
|
||||
Alternatively you may be able to disable USB 3.0 in the BIOS.
|
||||
If the BIOS does not have the option to disable USB 3.0, try running the following command in dom0 to force USB 2.0 modes for the USB ports:
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user