2020-10-10 06:50:35 -04:00
---
2021-03-13 13:06:18 -05:00
lang: en
2020-10-10 06:50:35 -04:00
layout: doc
2021-06-16 01:33:51 -04:00
redirect_from:
- /doc/hvm-troubleshooting/
2021-03-13 13:06:18 -05:00
ref: 232
2021-06-16 02:19:45 -04:00
title: HVM Troubleshooting
2020-10-10 06:50:35 -04:00
---
2021-03-13 12:03:23 -05:00
# HVM Troubleshooting
2020-10-10 06:50:35 -04:00
2021-03-13 12:03:23 -05:00
## HVM pauses on boot, followed by kernel error
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:
2021-03-13 12:03:23 -05:00
`
2020-10-10 06:50:35 -04:00
BUG: soft lockup - CPU#0 stuck for 23s! [systemd-udevd:244]
2021-03-13 12:03:23 -05:00
`
2020-10-10 06:50:35 -04:00
To fix this:
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
2020-10-10 06:50:35 -04:00
If this solves the problem then you will want to make the change permanent:
2021-03-13 12:03:23 -05:00
1. Edit the file `/etc/default/grub` .
1. Find the line which starts:
2020-10-10 06:50:35 -04:00
~~~
GRUB_CMDLINE_LINUX=
~~~
2021-03-13 12:03:23 -05:00
1. Remove this text from that line:
2020-10-10 06:50:35 -04:00
~~~
rhgb
~~~
2021-03-13 12:03:23 -05:00
1. Add this text to that line:
2020-10-10 06:50:35 -04:00
~~~
modprobe.blacklist=bochs_drm
~~~
2021-03-13 12:03:23 -05:00
1. Run this command:
2020-10-10 06:50:35 -04:00
~~~
grub2-mkconfig --output=/boot/grub2/grub.cfg
~~~
The HVM should now start normally.
2021-03-13 12:03:23 -05:00
## Can't start an OS in an HVM / "Probing EDD (edd=off to disable!... ok" message
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:
2021-03-13 12:03:23 -05:00
```sh
qvm-prefs < HVMname > kernel ""
```
## HVM crashes when booting from ISO
2020-10-10 06:50:35 -04:00
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.
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:
2021-03-13 12:03:23 -05:00
```sh
qvm-prefs < HVMname > memory 2000
```
2020-10-10 06:50:35 -04:00
2021-03-13 12:03:23 -05:00
## Attached devices in Windows HVM stop working on suspend/resume
2020-10-19 09:22:38 -04:00
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 ).