From 09b7f43b884cc8de626a90a1ef06a4b8ec961ac7 Mon Sep 17 00:00:00 2001 From: mvermaes Date: Tue, 2 Feb 2016 15:32:14 +0800 Subject: [PATCH] Change qrexec-timeout references to qrexec_timeout On at least Qubes R3.0, this option has an underscore instead of hyphen. --- managing-os/windows-appvms.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/managing-os/windows-appvms.md b/managing-os/windows-appvms.md index d25e6cf3..c62686be 100644 --- a/managing-os/windows-appvms.md +++ b/managing-os/windows-appvms.md @@ -67,10 +67,10 @@ Qubes (R2 Beta 3 and later releases) will automatically detect the tools has bee qvm-prefs ~~~ -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 qrexec-timeout 300 +qvm-prefs -s qrexec_timeout 300 ~~~ Using Windows AppVMs in seamless mode (Qubes R2 Beta 3 and later)