Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2025-08-14 09:25:59 -04:00
Code Issues Projects Releases Packages Wiki Activity

Convert to RST

Browse source 
This is done using tools at
https://github.com/maiska/qubes-translation-utilz, commit
4c8e2a7f559fd37e29b51769ed1ab1c6cf92e00d.
This commit is contained in:
Marek Marczykowski-Górecki 2025-07-04 14:23:09 +02:00
parent e3db139fe3
commit 7e464d0f40
No known key found for this signature in database
GPG key ID: F32894BE9684938A
428 changed files with 32833 additions and 29703 deletions
Download patch file Download diff file Expand all files Collapse all files

102
user/troubleshooting/hvm-troubleshooting.rst Normal file
View file

@ -0,0 +1,102 @@
===================
HVM troubleshooting
===================
HVM pauses on boot, followed by kernel error
--------------------------------------------
The HVM may pause on boot, showing a fixed cursor. After a while a series of warnings may be shown similar to this:
.. code:: bash
BUG: soft lockup - CPU#0 stuck for 23s! [systemd-udevd:244]
To fix this:
1. Kill the HVM.
2. Start the HVM
3. Press “e” at the grub screen to edit the boot parameters
4. Find the /vmlinuz line, and edit it to replace “rhgb” with “modprobe.blacklist=bochs_drm”
5. Press “Ctrl-x” to start the HVM
If this solves the problem then you will want to make the change permanent:
1. Edit the file ``/etc/default/grub``.
2. Find the line which starts:
.. code:: bash
GRUB_CMDLINE_LINUX=
3. Remove this text from that line:
.. code:: bash
rhgb
4. Add this text to that line:
.. code:: bash
modprobe.blacklist=bochs_drm
5. Run this command:
.. code:: bash
grub2-mkconfig --output=/boot/grub2/grub.cfg
The HVM should now start normally.
Can't start an OS in an HVM / "Probing EDD (edd=off to disable!… ok" message
----------------------------------------------------------------------------
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:
.. code:: bash
qvm-prefs <HVMname> kernel ""
HVM crashes when booting from ISO
---------------------------------
If your HVM crashes when trying to boot an ISO, first ensure that ``qvm-prefs <HVMname> kernel`` is empty, as shown above. 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:
.. code:: bash
qvm-prefs <HVMname> memory 2000
Attached devices in Windows HVM stop working on suspend/resume
--------------------------------------------------------------
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 :ref:`Suspend/resume Troubleshooting <user/troubleshooting/resume-suspend-troubleshooting:attached devices in windows hvm stop working on suspend\/resume>`.