Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2024-10-01 01:25:40 -04:00
Code Issues Packages Projects Releases Wiki Activity
1376696941
qubes-doc/user/troubleshooting/hvm-troubleshooting.md

79 lines
2.1 KiB
Markdown
Raw Normal View History

Add HVM Troubleshooting
2020-10-10 06:50:35 -04:00
---
Add lang + ref tags to frontmatter Those are fields used by the language switcher to correlate pages across different languages, even if they have different names/paths/titles. They are generated with the prepare_for_translation.py script.
2021-03-13 13:06:18 -05:00
lang: en
Add HVM Troubleshooting
2020-10-10 06:50:35 -04:00
layout: doc
Revert "Remove all instances of `permalink:` in YAML frontmatter" This reverts commit c815e4c54c315dfca30c66f6a33e07b1ff90b786. https://github.com/QubesOS/qubes-issues/issues/6701#issuecomment-862822827
2021-06-16 22:56:25 -04:00
permalink: /doc/hvm-troubleshooting/
Add lang + ref tags to frontmatter Those are fields used by the language switcher to correlate pages across different languages, even if they have different names/paths/titles. They are generated with the prepare_for_translation.py script.
2021-03-13 13:06:18 -05:00
ref: 232
Fix capitalization; update terms (QubesOS/qubes-issues#6769) Thank you to @unman for the initial sentence case pass.
2021-07-09 08:10:44 -04:00
title: HVM troubleshooting
Add HVM Troubleshooting
2020-10-10 06:50:35 -04:00
---
Markdown formatting fixes - mark all code blocks with ``` - unify empty lines between sections - adjust list syntax (no space before dash) - adjust headers to use Atx-style syntax - remove trailing spaces
2021-03-13 12:03:23 -05:00
## HVM pauses on boot, followed by kernel error
Add HVM Troubleshooting
2020-10-10 06:50:35 -04:00
The HVM may pause on boot, showing a fixed cursor.
After a while a series of warnings may be shown similar to this:
fix md typo
2021-10-04 06:30:58 -04:00
```
BUG: soft lockup - CPU#0 stuck for 23s! [systemd-udevd:244]
```
Add HVM Troubleshooting
2020-10-10 06:50:35 -04:00
To fix this:
Markdown formatting fixes - mark all code blocks with ``` - unify empty lines between sections - adjust list syntax (no space before dash) - adjust headers to use Atx-style syntax - remove trailing spaces
2021-03-13 12:03:23 -05:00
1. Kill the HVM.
1. Start the HVM
1. Press "e" at the grub screen to edit the boot parameters
1. Find the /vmlinuz line, and edit it to replace "rhgb" with "modprobe.blacklist=bochs_drm"
1. Press "Ctrl-x" to start the HVM
Add HVM Troubleshooting
2020-10-10 06:50:35 -04:00
If this solves the problem then you will want to make the change permanent:
Markdown formatting fixes - mark all code blocks with ``` - unify empty lines between sections - adjust list syntax (no space before dash) - adjust headers to use Atx-style syntax - remove trailing spaces
2021-03-13 12:03:23 -05:00
1. Edit the file `/etc/default/grub`.
1. Find the line which starts:
Add HVM Troubleshooting
2020-10-10 06:50:35 -04:00
~~~
GRUB_CMDLINE_LINUX=
~~~
Markdown formatting fixes - mark all code blocks with ``` - unify empty lines between sections - adjust list syntax (no space before dash) - adjust headers to use Atx-style syntax - remove trailing spaces
2021-03-13 12:03:23 -05:00
1. Remove this text from that line:
Add HVM Troubleshooting
2020-10-10 06:50:35 -04:00
~~~
rhgb
~~~
Markdown formatting fixes - mark all code blocks with ``` - unify empty lines between sections - adjust list syntax (no space before dash) - adjust headers to use Atx-style syntax - remove trailing spaces
2021-03-13 12:03:23 -05:00
1. Add this text to that line:
Add HVM Troubleshooting
2020-10-10 06:50:35 -04:00
~~~
modprobe.blacklist=bochs_drm
~~~
Markdown formatting fixes - mark all code blocks with ``` - unify empty lines between sections - adjust list syntax (no space before dash) - adjust headers to use Atx-style syntax - remove trailing spaces
2021-03-13 12:03:23 -05:00
1. Run this command:
Add HVM Troubleshooting
2020-10-10 06:50:35 -04:00
~~~
grub2-mkconfig --output=/boot/grub2/grub.cfg
~~~
The HVM should now start normally.
Markdown formatting fixes - mark all code blocks with ``` - unify empty lines between sections - adjust list syntax (no space before dash) - adjust headers to use Atx-style syntax - remove trailing spaces
2021-03-13 12:03:23 -05:00
## Can't start an OS in an HVM / "Probing EDD (edd=off to disable!... ok" message
Add HVM Troubleshooting
2020-10-10 06:50:35 -04:00
If you see a screen popup with SeaBios and 4 lines, last one being `Probing EDD (edd=off to disable!... ok`, then enter the following command from a `dom0` prompt:
Markdown formatting fixes - mark all code blocks with ``` - unify empty lines between sections - adjust list syntax (no space before dash) - adjust headers to use Atx-style syntax - remove trailing spaces
2021-03-13 12:03:23 -05:00
```sh
qvm-prefs <HVMname> kernel ""
```
## HVM crashes when booting from ISO
Add HVM Troubleshooting
2020-10-10 06:50:35 -04:00
Markdown formatting fixes - mark all code blocks with ``` - unify empty lines between sections - adjust list syntax (no space before dash) - adjust headers to use Atx-style syntax - remove trailing spaces
2021-03-13 12:03:23 -05:00
If your HVM crashes when trying to boot an ISO, first ensure that ` qvm-prefs <HVMname> kernel` is empty, as shown above.
Add HVM Troubleshooting
2020-10-10 06:50:35 -04:00
If this doesn't help, then disable memory balancing and set the minimum memory to 2GB.
You can disable memory-balancing in the settings, under the “Advanced” tab.
To give the VM a RAM of 2GB, open a terminal in `dom0` and enter:
Markdown formatting fixes - mark all code blocks with ``` - unify empty lines between sections - adjust list syntax (no space before dash) - adjust headers to use Atx-style syntax - remove trailing spaces
2021-03-13 12:03:23 -05:00
```sh
qvm-prefs <HVMname> memory 2000
```
Add HVM Troubleshooting
2020-10-10 06:50:35 -04:00
Markdown formatting fixes - mark all code blocks with ``` - unify empty lines between sections - adjust list syntax (no space before dash) - adjust headers to use Atx-style syntax - remove trailing spaces
2021-03-13 12:03:23 -05:00
## Attached devices in Windows HVM stop working on suspend/resume
Add section about attached devices in Windows HVM
2020-10-19 09:22:38 -04:00
Edit link to Suspend/resume Troubleshooting
2020-10-19 09:24:18 -04:00
After the whole system gets suspended into S3 sleep and subsequently resumed, some attached devices may stop working. To know how to make the devices work, see [Suspend/resume Troubleshooting](/doc/suspend-resume-troubleshooting/#attached-devices-in-windows-hvm-stop-working-on-suspendresume).
Reference in New Issue Copy Permalink