manual fixes

Manual fixes after the conversion tool. Mostly based on sphinx warnings.
This commit is contained in:
Marek Marczykowski-Górecki 2025-07-04 14:47:18 +02:00
parent d3f5fafcde
commit 5432f95705
No known key found for this signature in database
GPG key ID: F32894BE9684938A
13 changed files with 23 additions and 26 deletions

View file

@ -9,7 +9,7 @@ List of Download Mirrors
------------------------
The full list of known Qubes download mirrors is available `here <https://www.qubes-os.org/downloads/#mirrors>__.
The full list of known Qubes download mirrors is available `here <https://www.qubes-os.org/downloads/#mirrors>`__.
Instructions for Mirror Operators
---------------------------------

View file

@ -161,7 +161,7 @@ Because of above limitations, you will need to configure some of those manually.
2. Start the VM from command line:
.. code:: bash
.. code::
[user@dom0 ~]$ qvm-start custom-template
--> Loading the VM (type = template)...
@ -177,7 +177,7 @@ Because of above limitations, you will need to configure some of those manually.
3. Access VM console:
.. code:: bash
.. code::
[user@dom0 ~]$ virsh -c xen:/// console custom-template

View file

@ -238,7 +238,7 @@ Set the debug flag in order to have a graphical console:
The second part of the installation process will crash with the standard VGA video adapter and the VM will stay in “transient” mode with the following error in ``guest-win7new-dm.log``:
.. code:: bash
.. code::
qemu: /home/user/qubes-src/vmm-xen-stubdom-linux/build/qemu/exec.c:1187: cpu_physical_memory_snapshot_get_dirty: Assertion `start + length <= snap->end' failed.

View file

@ -90,7 +90,7 @@ Never Install Unsigned Packages
If you see something like this:
.. code:: bash
.. code::
WARNING: The following packages cannot be authenticated!
icedove
@ -106,7 +106,7 @@ Signature Verification Warnings
There should be none at the moment. If there was such a warning, it would look like this:
.. code:: bash
.. code::
W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://deb.torproject.org stable Release: The following signatures were invalid: KEYEXPIRED 1409325681 KEYEXPIRED 1409325681 KEYEXPIRED 1409325681 KEYEXPIRED 1409325681
@ -120,7 +120,7 @@ In past various apt repositories were signed with expired key: `The Tor Project
You saw the following warning:
.. code:: bash
.. code::
W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://deb.torproject.org stable Release: The following signatures were invalid: KEYEXPIRED 1409325681 KEYEXPIRED 1409325681 KEYEXPIRED 1409325681 KEYEXPIRED 1409325681
@ -139,7 +139,7 @@ Changed Configuration Files
If you see something like the following.
.. code:: bash
.. code::
Setting up ifupdown ...
Configuration file /etc/network/interfaces

View file

@ -26,7 +26,7 @@ There are a variety of other problems that could arise when using a USB installa
"**Warning:** dracut-initqueue timeout - starting timeout scripts" during installation
----------------------------------------------------------------------------------
--------------------------------------------------------------------------------------
This error message is related to the faulty creation of the USB installation medium. If you receive this error message during installation, please make sure you have followed the instructions on :ref:`how to write your ISO to a USB key <user/downloading-installing-upgrading/installation-guide:copying the iso onto the installation medium>`. Specifically, the ``dd`` command listed on that page has been verified to solve this issue on multiple Qubes installation versions.

View file

@ -51,7 +51,7 @@ Errors suggesting this issue:
- in ``xl dmesg`` output:
.. code:: bash
.. code::
(XEN) [VT-D] It's disallowed to assign 0000:00:1a.0 with shared RMRR at dbe9a000 for Dom19.
(XEN) XEN_DOMCTL_assign_device: assign 0000:00:1a.0 to dom19 failed (-1)
@ -60,7 +60,7 @@ Errors suggesting this issue:
- during ``qvm-start sys-usb``:
.. code:: bash
.. code::
internal error: Unable to reset PCI device [...] no FLR, PM reset or bus reset available.