Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[GSoD] VM Troubleshooting #1055

Merged
merged 6 commits into from Oct 19, 2020
Merged

Conversation

enjeck
Copy link
Contributor

@enjeck enjeck commented Oct 10, 2020

No description provided.

Copy link
Member

@marmarek marmarek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Besides comments about the content itself, I see you combined this with changes already included in #1053. Either split them, or make a single PR about both things.

user/troubleshooting/vm-troubleshooting.md Show resolved Hide resolved
## Qubes starts, but no VMs load ##

This issue may occur if a dom0 update is interrupted halfway through and/or a hard power off is done without shutting down Qubes, which results in files getting corrupted.
In this case, the best fix is to reinstall Qubes and restore your files from a backup.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is nuclear option, in many cases there are less intrusive methods, depending on why exactly VMs do not start. Better option is to recommend trying to start some specific VM to see exact failure message and direct further steps based on that.

## "Cannot connect to qrexec agent" error ##

If you face this error when starting a VM, it may be due to too little initial memory.
A solution is to increase the initial memory from 200MB to 400MB by navigating to VM settings » Advanced » Initial memory.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea is also to look into /var/log/xen/console/guest-VMNAME.log. There may be other reasons than too low memory - like VM kernel crash on startup, or some corrupted files.

doc.md Outdated
@@ -135,13 +135,17 @@ Core documentation for Qubes users.
* [Making Any File Persistent Using `bind-dirs`](/doc/bind-dirs/)
* [GUI Configuration](/doc/gui-configuration/)
* [Resizing Disk Images](/doc/resize-disk-image/)
* [Troubleshooting UEFI](/doc/uefi-troubleshooting/)
* [Troubleshooting UEFI](/doc/uefi-troubleshooting/)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Spurious space at the end.

Copy link
Member

@marmarek marmarek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Content seems fine now.

@enjeck
Copy link
Contributor Author

enjeck commented Oct 19, 2020

@andrewdavidwong I've fixed the merge conflict here :)

All the content here is already available at Suspend-resume-troubleshooting.md. Plus, this page should redirect to /doc/suspend-resume-troubleshooting
@andrewdavidwong andrewdavidwong merged commit 78d2f82 into QubesOS:master Oct 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants