From fd1cd0077b685bd8050f8f07654b47dba4ac82f5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marta=20Marczykowska-G=C3=B3recka?= Date: Tue, 24 Mar 2020 16:20:56 +0100 Subject: [PATCH] Changed xl console to qvm-console-dispvm Due to changes documented in https://github.com/QubesOS/qubes-issues/issues/4544 , we can now use the (safer) qvm-console-dispvm instead of a raw xl console. --- user/advanced-configuration/managing-vm-kernel.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/user/advanced-configuration/managing-vm-kernel.md b/user/advanced-configuration/managing-vm-kernel.md index 22a2e197..c901a467 100644 --- a/user/advanced-configuration/managing-vm-kernel.md +++ b/user/advanced-configuration/managing-vm-kernel.md @@ -364,7 +364,7 @@ The output should look like this: #### Troubleshooting -In case of problems, you can access the VM console using `sudo xl console VMNAME` in dom0, then access the GRUB menu. +In case of problems, you can access the VM console using `qvm-console-dispvm VMNAME` in dom0, then access the GRUB menu. You need to call it just after starting the VM (until `GRUB_TIMEOUT` expires); for example, in a separate dom0 terminal window. In any case you can later access the VM's logs (especially the VM console log `/var/log/xen/console/guest-VMNAME.log`).