Skip to content

Commit ece634a

Browse files
committed
troubleshooting/upgrade: leave some place for other cases
Signed-off-by: Yann Dirson <yann.dirson@vates.tech>
1 parent 2154a58 commit ece634a

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

docs/troubleshooting/installation-upgrade.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -32,9 +32,11 @@ The target installation partition is mounted in `/tmp/root`.
3232
## The ISO installer does not offer to upgrade the existing install (XCP-ng or XenServer)
3333

3434
:::note
35-
This section details how to deal with the most frequent cause for the installer not detecting your current installation. There can be other, rarer cases which are not detailed here.
35+
This section details how to deal with the most frequent causes for the installer not detecting your current installation. There can be other, rarer cases which are not detailed here.
3636
:::
3737

38+
### UEFI/BIOS mismatch
39+
3840
For the installer to detect your current install (XCP-ng or XenServer), the ISO must be booted in the same firmware context.
3941
The difference is how you pick the drive at boot. This applies to physical and virtual CD/DVD/USB drives.
4042

@@ -55,7 +57,7 @@ Virtual CDROM Device <<<<<< This one is the same device, in legacy BIOS
5557
---------------------------------
5658
```
5759

58-
### How to check if a running install is using UEFI or legacy BIOS?
60+
#### How to check if a running install is using UEFI or legacy BIOS?
5961

6062
On the host, run `efibootmgr`.
6163

@@ -70,4 +72,4 @@ The main log file is `/var/log/installer/install-log`.
7072

7173
## Debugging the installer
7274

73-
You can [build your own installer](../../project/development-process/ISO-modification).
75+
You can [build your own installer](../../project/development-process/ISO-modification).

0 commit comments

Comments
 (0)