Merge pull request #99 from mvermaes/patch-2

Change qrexec-timeout references to qrexec_timeout
This commit is contained in:
Axon 2016-02-02 19:03:27 +00:00
commit 10e07da111

View File

@ -67,10 +67,10 @@ Qubes (R2 Beta 3 and later releases) will automatically detect the tools has bee
qvm-prefs <your-appvm-name>
~~~
NOTE: it is recommended to increase the default value of `qrexec-timeout` property from 60 (seconds) to, for example, 300. During one of the first reboots after Windows Tools installation Windows user profiles are moved onto the private VM's virtual disk (private.img) and this operation can take some time. Moving profiles is performed in an early boot phase when qrexec is not yet running, so timeout may occur with the default value. To change the property use this command in dom0:
NOTE: it is recommended to increase the default value of `qrexec_timeout` property from 60 (seconds) to, for example, 300. During one of the first reboots after Windows Tools installation Windows user profiles are moved onto the private VM's virtual disk (private.img) and this operation can take some time. Moving profiles is performed in an early boot phase when qrexec is not yet running, so timeout may occur with the default value. To change the property use this command in dom0:
~~~
qvm-prefs -s <vm-name> qrexec-timeout 300
qvm-prefs -s <vm-name> qrexec_timeout 300
~~~
Using Windows AppVMs in seamless mode (Qubes R2 Beta 3 and later)