Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2025-08-06 05:34:27 -04:00
Code Issues Projects Releases Packages Wiki Activity

basics and customization fenced blocks replaced with standard markdown

Browse source
This commit is contained in:
Jeepler 2015-09-23 18:41:20 +02:00
parent cbdd6e00ab
commit b65aa75876
4 changed files with 33 additions and 57 deletions
Download patch file Download diff file Expand all files Collapse all files

38
basics/GettingStarted.md
View file

@ -55,15 +55,11 @@ By default, each domain's menu contains only a few shortcuts. If you'd like to a
To start apps from the console in dom0, type:
```
qvm-run -a <domain> "<app name> [arguments]"
```
qvm-run -a <domain> "<app name> [arguments]"
e.g.:
```
qvm-run -a untrusted firefox
```
qvm-run -a untrusted firefox
Adding, Removing, and Listing Domains
-------------------------------------
@ -96,27 +92,23 @@ To allow domains to enter full screen mode, one should edit the `/etc/qubes/guid
E.g. to allow all domains to enter full screen mode, set `allow_fullscreen` flag to `true` in the `global` section:
```
global: {
# default values
allow_fullscreen = false;
#allow_utf8_titles = false;
#secure_copy_sequence = "Ctrl-Shift-c";
#secure_paste_sequence = "Ctrl-Shift-v";
#windows_count_limit = 500;
};
```
global: {
# default values
allow_fullscreen = false;
#allow_utf8_titles = false;
#secure_copy_sequence = "Ctrl-Shift-c";
#secure_paste_sequence = "Ctrl-Shift-v";
#windows_count_limit = 500;
};
To allow only select AppVMs to enter full screen mode, create a per-VM section, and set `allow_fullscreen` flag there to `true`:
```
VM: {
work: {
allow_fullscreen = true;
};
VM: {
work: {
allow_fullscreen = true;
};
};
```
};
In order for the changes to take effect, restart the AppVM(s).

6
basics/UserFaq.md
View file

@ -192,7 +192,7 @@ Enable "debug mode" in the AppVM's settings, either by checking the box labelled
### I created a usbVM and assigned usb controllers to it. Now the usbVM wont boot.
This is probably because one of the controllers does not support reset. In Qubes R2 any such errors were ignored but in Qubes R3.0 they are not.
This is probably because one of the controllers does not support reset. In Qubes R2 any such errors were ignored but in Qubes R3.0 they are not.
A device that does not support reset is not safe and generally should not be assigned to a VM.
Most likely the offending controller is a USB3.0 device. You can remove this controller from the usbVM, and see if this allows the VM to boot.
@ -219,11 +219,7 @@ or
1. Go to the sysfs (`/sys/bus/pci`), find the right device, detach it from the pciback driver and attach back to the original driver. Replace `<BDF>` with your device, for example `00:1c.2`:
```
echo 0000:<BDF> > /sys/bus/pci/drivers/pciback/unbind
MODALIAS=`cat /sys/bus/pci/devices/0000:<BDF>/modalias`
MOD=`modprobe -R $MODALIAS | head -n 1`
echo <BDF> > /sys/bus/pci/drivers/$MOD/bind
```