diff --git a/pages/bare_metal_cloud/dedicated_servers/boot-process/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/boot-process/guide.en-gb.md new file mode 100644 index 00000000000..350eaaec4f5 --- /dev/null +++ b/pages/bare_metal_cloud/dedicated_servers/boot-process/guide.en-gb.md @@ -0,0 +1,136 @@ +--- +title: "Understanding the dedicated server boot process" +excerpt: "Learn how OVHcloud dedicated servers boot and why PXE must remain first in the boot order" +updated: 2026-02-06 +--- + +## Objective + +OVHcloud dedicated servers use a network-based boot process (netboot) that provides flexibility and security benefits. This guide explains how the boot process works and why you should not change the default boot order directly in the BIOS/UEFI settings, but instead use the [OVHcloud Control Panel](/links/manager) or the [OVHcloud API](/links/api). + +**This guide will help you understand:** + +- How the OVHcloud boot process works +- The available boot modes +- Why PXE must remain first in the BIOS/UEFI boot order +- How microcode updates are applied automatically + +## Requirements + +- A [dedicated server](/links/bare-metal/bare-metal) in your OVHcloud account +- Access to the [OVHcloud Control Panel](/links/manager) or to the [OVHcloud API](/links/api) + +## Instructions + +### How the boot process works + +OVHcloud dedicated servers use [iPXE](https://ipxe.org/), an advanced network boot firmware, to boot from the network. When you set a boot mode for your server, OVHcloud automatically configures the corresponding iPXE script. When the server powers on, it follows this sequence: + +![Boot process overview](images/boot-process.svg){.thumbnail} + +1. **PXE boot via DHCP**: The server boots from the network using DHCP on the public interface. +2. **Download iPXE**: The DHCP server provides the server's public IP address and a filename to download iPXE. +3. **Query boot service**: iPXE queries an internal OVHcloud boot service to retrieve the script to execute. +4. **Execute script**: iPXE executes the script based on your configured boot mode. + +This process happens every time your server boots. + +### Boot modes + +You can configure your server to boot in one of the following modes: + +| Boot mode | Description | Use case | +|-----------|-------------|----------| +| **Boot to disk** | Boots the operating system installed on disk | Normal operation | +| **Customer rescue** | Boots into a temporary operating system | Troubleshooting, recovery, first-time setup | +| **Custom boot script** | Executes a user-defined iPXE script | Advanced use cases (volatile OS, custom deployment) | + +#### Boot to disk + +When set to **boot to disk**, the boot process follows these steps: + +**1\. Microcode update** + +The system downloads and applies the latest [CPU microcode](https://blog.ovhcloud.com/ovhcloud-microcode-management-at-scale/) for your processor (AMD or Intel). This happens transparently and provides security patches without requiring OS-level or BIOS/UEFI updates. + +> [!primary] +> +> Microcode updates are verified (signature checked) before being applied. If the microcode download fails, the boot process continues normally — your server will still boot. +> + +**2\. Boot to operating system** + +- **Legacy boot servers**: iPXE uses [`sanboot`](https://ipxe.org/cmd/sanboot) to boot directly from the first disk. +- **UEFI boot servers**: iPXE uses [`sanboot`](https://ipxe.org/cmd/sanboot) to boot the EFI bootloader path (`efiBootloaderPath`) specified during [OS installation](/pages/bare_metal_cloud/dedicated_servers/getting-started-with-dedicated-server#install) (e.g. `\efi\debian\grubx64.efi`). + + When OVHcloud installs an operating system, the boot order is not modified (e.g. GRUB is installed with the `--no-nvram` option) to ensure PXE remains first. + + If `sanboot` fails (e.g. the specified file is broken or cannot be found), iPXE falls back to rEFInd, which auto-detects EFI bootloaders. + + The `efiBootloaderPath` can be changed via the [OVHcloud API](/links/api): + + > [!api] + > + > @api {v1} /dedicated/server PUT /dedicated/server/{serviceName} + > + +#### Customer rescue mode + +A temporary operating system for troubleshooting, recovery, and initial configuration. Microcode updates are applied before booting into rescue, just as with boot to disk. For more information, see [Activating and using rescue mode](/pages/bare_metal_cloud/dedicated_servers/rescue_mode). + +#### Custom boot scripts + +For advanced use cases, you can configure a custom iPXE script via the [OVHcloud API](/links/api). For more information, see [Configuring a custom iPXE script](/pages/bare_metal_cloud/dedicated_servers/ipxe-scripts). + +> [!warning] +> +> Custom boot scripts skip the automatic microcode loading described above. +> + +### Why you must not change the boot order + +> [!warning] +> +> Do not change the boot order in your server's BIOS/UEFI settings or via tools like `efibootmgr`. PXE (network boot) must remain the first boot option. +> +> If you install an operating system manually, ensure your bootloader does not modify the NVRAM boot order (e.g. use `grub-install --no-nvram`). +> + +OVHcloud relies on the network boot process for: + +- **Boot mode selection**: The boot service determines whether to boot to rescue, disk, or a custom script. +- **UEFI boot to disk**: OVHcloud does not create EFI boot entries — iPXE uses `efiBootloaderPath` to chain to the bootloader. +- **Microcode updates**: Security patches are applied during the boot process. + +**If you change the boot order:** + +- ❌ Boot mode changes made in the OVHcloud Control Panel or via the OVHcloud API will have no effect. +- ❌ UEFI servers may fail to boot (no EFI boot entry exists for the on-disk bootloader). +- ❌ Rescue mode will no longer be accessible. +- ❌ Microcode updates will no longer be applied automatically. +- ❌ OVHcloud support may be unable to assist with boot issues. + +### Servers with private-only interfaces (OLA) + +If your server uses **[OLA (OVHcloud Link Aggregation)](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)** — a vRack-only configuration with no public interface — the standard netboot process will not work. Private networks cannot reach the OVHcloud DHCP and boot infrastructure. + +In this case, you must deploy your own DHCP, TFTP, and boot services within your private network. For detailed instructions, see the guide on [Managing server reboot with OVHcloud Link Aggregation](/pages/bare_metal_cloud/dedicated_servers/pxe-with-full-private-dedicated). + +> [!primary] +> +> As of February 2026, OVHcloud is working on native support for netboot over private networks. This guide will be updated when the feature becomes available. +> + +## Go further + +[OS installation](/pages/bare_metal_cloud/dedicated_servers/getting-started-with-dedicated-server#install) + +[Activating and using rescue mode](/pages/bare_metal_cloud/dedicated_servers/rescue_mode) + +[Configuring a custom iPXE script](/pages/bare_metal_cloud/dedicated_servers/ipxe-scripts) + +[Managing server reboot with OVHcloud Link Aggregation](/pages/bare_metal_cloud/dedicated_servers/pxe-with-full-private-dedicated) + +[OVHcloud microcode management at scale](https://blog.ovhcloud.com/ovhcloud-microcode-management-at-scale/) + +Join our [community of users](/links/community). diff --git a/pages/bare_metal_cloud/dedicated_servers/boot-process/guide.fr-fr.md b/pages/bare_metal_cloud/dedicated_servers/boot-process/guide.fr-fr.md new file mode 100644 index 00000000000..1ce661e51e8 --- /dev/null +++ b/pages/bare_metal_cloud/dedicated_servers/boot-process/guide.fr-fr.md @@ -0,0 +1,136 @@ +--- +title: "Comprendre le processus de démarrage des serveurs dédiés" +excerpt: "Découvrez comment les serveurs dédiés OVHcloud démarrent et pourquoi le PXE doit rester en premier dans l'ordre de boot" +updated: 2026-02-06 +--- + +## Objectif + +Les serveurs dédiés OVHcloud utilisent un processus de démarrage réseau (netboot) qui offre flexibilité et sécurité. Ce guide explique le fonctionnement du processus de démarrage et pourquoi vous ne devez pas modifier l'ordre de boot directement dans les paramètres BIOS/UEFI, mais plutôt via l'[espace client OVHcloud](/links/manager) ou l'[API OVHcloud](/links/api). + +**Ce guide vous aidera à comprendre :** + +- Le fonctionnement du processus de démarrage OVHcloud +- Les modes de démarrage disponibles +- Pourquoi le PXE doit rester en premier dans l'ordre de boot BIOS/UEFI +- Comment les mises à jour de microcode sont appliquées automatiquement + +## Prérequis + +- Un [serveur dédié](/links/bare-metal/bare-metal) dans votre compte OVHcloud +- Un accès à l'[espace client OVHcloud](/links/manager) ou à l'[API OVHcloud](/links/api) + +## En pratique + +### Fonctionnement du processus de démarrage + +Les serveurs dédiés OVHcloud utilisent [iPXE](https://ipxe.org/), un firmware de démarrage réseau avancé. Lorsque vous définissez un mode de démarrage pour votre serveur, OVHcloud configure automatiquement le script iPXE correspondant. Au démarrage du serveur, la séquence suivante s'exécute : + +![Aperçu du processus de démarrage](images/boot-process.svg){.thumbnail} + +1. **Démarrage PXE via DHCP** : Le serveur démarre depuis le réseau en utilisant DHCP sur l'interface publique. +2. **Téléchargement d'iPXE** : Le serveur DHCP fournit l'adresse IP publique du serveur et un nom de fichier pour télécharger iPXE. +3. **Requête au service de boot** : iPXE interroge un service de boot interne OVHcloud pour récupérer le script à exécuter. +4. **Exécution du script** : iPXE exécute le script en fonction du mode de démarrage configuré. + +Ce processus se produit à chaque démarrage de votre serveur. + +### Modes de démarrage + +Vous pouvez configurer votre serveur pour démarrer dans l'un des modes suivants : + +| Mode de démarrage | Description | Cas d'usage | +|-------------------|-------------|-------------| +| **Démarrage sur disque** | Démarre le système d'exploitation installé sur le disque | Fonctionnement normal | +| **Mode rescue** | Démarre sur un système d'exploitation temporaire | Dépannage, récupération, configuration initiale | +| **Script de boot personnalisé** | Exécute un script iPXE défini par l'utilisateur | Cas avancés (OS volatile, déploiement personnalisé) | + +#### Démarrage sur disque + +En mode **démarrage sur disque**, le processus de boot suit ces étapes : + +**1\. Mise à jour du microcode** + +Le système télécharge et applique le dernier [microcode CPU](https://blog.ovhcloud.com/ovhcloud-microcode-management-at-scale/) pour votre processeur (AMD ou Intel). Cela se fait de manière transparente et fournit des correctifs de sécurité sans nécessiter de mises à jour au niveau de l'OS ou du BIOS/UEFI. + +> [!primary] +> +> Les mises à jour de microcode sont vérifiées (signature contrôlée) avant d'être appliquées. Si le téléchargement du microcode échoue, le processus de démarrage continue normalement — votre serveur démarrera quand même. +> + +**2\. Démarrage du système d'exploitation** + +- **Serveurs en boot Legacy** : iPXE utilise [`sanboot`](https://ipxe.org/cmd/sanboot) pour démarrer directement depuis le premier disque. +- **Serveurs en boot UEFI** : iPXE utilise [`sanboot`](https://ipxe.org/cmd/sanboot) pour démarrer le bootloader EFI (`efiBootloaderPath`) spécifié lors de l'[installation de l'OS](/pages/bare_metal_cloud/dedicated_servers/getting-started-with-dedicated-server#install) (par exemple, `\efi\debian\grubx64.efi`). + + Lorsqu'OVHcloud installe un système d'exploitation, l'ordre de boot n'est pas modifié (par exemple, GRUB est installé avec l'option `--no-nvram`) afin que le PXE reste en premier. + + Si `sanboot` échoue (par exemple, le fichier spécifié est corrompu ou introuvable), iPXE bascule sur rEFInd, qui détecte automatiquement les bootloaders EFI. + + Le paramètre `efiBootloaderPath` peut être modifié via l'[API OVHcloud](/links/api) : + + > [!api] + > + > @api {v1} /dedicated/server PUT /dedicated/server/{serviceName} + > + +#### Mode rescue + +Un système d'exploitation temporaire pour le dépannage, la récupération et la configuration initiale. Les mises à jour de microcode sont appliquées avant le démarrage en rescue, comme pour le démarrage sur disque. Pour plus d'informations, consultez notre guide « [Activer et utiliser le mode rescue](/pages/bare_metal_cloud/dedicated_servers/rescue_mode) ». + +#### Scripts de boot personnalisés + +Pour les cas d'usage avancés, vous pouvez configurer un script iPXE personnalisé via l'[API OVHcloud](/links/api). Pour plus d'informations, consultez notre guide « [Configurer un script iPXE personnalisé](/pages/bare_metal_cloud/dedicated_servers/ipxe-scripts) ». + +> [!warning] +> +> Les scripts de boot personnalisés ne bénéficient pas du chargement automatique du microcode décrit ci-dessus. +> + +### Pourquoi ne pas modifier l'ordre de boot + +> [!warning] +> +> Ne modifiez pas l'ordre de boot dans les paramètres BIOS/UEFI de votre serveur ou via des outils comme `efibootmgr`. Le PXE (démarrage réseau) doit rester la première option de boot. +> +> Si vous installez un système d'exploitation manuellement, assurez-vous que votre bootloader ne modifie pas l'ordre de boot NVRAM (par exemple, utilisez `grub-install --no-nvram`). +> + +OVHcloud s'appuie sur le processus de démarrage réseau pour : + +- **Sélectionner le mode de boot** : Le service de boot détermine s'il faut démarrer en rescue, sur disque ou avec un script personnalisé. +- **Démarrage sur disque UEFI** : OVHcloud ne crée pas d'entrées de boot EFI — iPXE utilise `efiBootloaderPath` pour chaîner vers le bootloader. +- **Appliquer les mises à jour de microcode** : Les correctifs de sécurité sont appliqués pendant le processus de démarrage. + +**Si vous modifiez l'ordre de boot :** + +- ❌ Les changements de mode de boot effectués dans l'espace client OVHcloud ou via l'API OVHcloud n'auront aucun effet. +- ❌ Les serveurs UEFI pourraient ne pas démarrer (aucune entrée de boot EFI n'existe pour le bootloader sur disque). +- ❌ Le mode rescue ne sera plus accessible. +- ❌ Les mises à jour de microcode ne seront plus appliquées automatiquement. +- ❌ Le support OVHcloud pourrait ne pas être en mesure de vous aider en cas de problème de démarrage. + +### Serveurs avec interfaces privées uniquement (OLA) + +Si votre serveur utilise **[OLA (OVHcloud Link Aggregation)](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)** — une configuration *vRack-only* sans interface publique — le processus netboot standard ne fonctionnera pas. Les réseaux privés ne peuvent pas atteindre l'infrastructure DHCP et de boot OVHcloud. + +Dans ce cas, vous devez déployer vos propres services DHCP, TFTP et de boot au sein de votre réseau privé. Pour des instructions détaillées, consultez le guide « [Gérer le redémarrage de votre serveur avec OVHcloud Link Aggregation](/pages/bare_metal_cloud/dedicated_servers/pxe-with-full-private-dedicated) ». + +> [!primary] +> +> En février 2026, OVHcloud travaille sur le support natif du netboot sur les réseaux privés. Ce guide sera mis à jour lorsque la fonctionnalité sera disponible. +> + +## Aller plus loin + +[Installation de l'OS](/pages/bare_metal_cloud/dedicated_servers/getting-started-with-dedicated-server#install) + +[Activer et utiliser le mode rescue](/pages/bare_metal_cloud/dedicated_servers/rescue_mode) + +[Configurer un script iPXE personnalisé](/pages/bare_metal_cloud/dedicated_servers/ipxe-scripts) + +[Gérer le redémarrage de votre serveur avec OVHcloud Link Aggregation](/pages/bare_metal_cloud/dedicated_servers/pxe-with-full-private-dedicated) + +[OVHcloud microcode management at scale](https://blog.ovhcloud.com/ovhcloud-microcode-management-at-scale/) + +Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/bare_metal_cloud/dedicated_servers/boot-process/images/boot-process.mmd b/pages/bare_metal_cloud/dedicated_servers/boot-process/images/boot-process.mmd new file mode 100644 index 00000000000..2cc4ce55c62 --- /dev/null +++ b/pages/bare_metal_cloud/dedicated_servers/boot-process/images/boot-process.mmd @@ -0,0 +1,33 @@ +flowchart TD + subgraph NETBOOT["Network Boot (every boot)"] + A["1. PXE boot via DHCP
on public interface"] + A --> B["2. Download iPXE"] + B --> C["3. Query boot service"] + end + + C --> D{"4. Execute script"} + + subgraph RESCUE["Customer Rescue"] + G1[Download, verify and apply
CPU microcode] + G1 --> G2[Boot live
rescue system] + end + + subgraph DISK["Boot to Disk"] + H[Download, verify and apply
CPU microcode] + H --> I{Firmware?} + I -->|UEFI boot| J[sanboot to
efiBootloaderPath] + I -->|Legacy boot| K[sanboot to
first disk] + J --> L{Success?} + L -->|Yes| M[OS loads] + L -->|No| N[rEFInd fallback
auto-detects EFI bootloaders] + K --> M + N --> M + end + + subgraph CUSTOM["Custom boot script"] + O[Execute user-defined
iPXE script
no microcode loading] + end + + D -->|Customer rescue| G1 + D -->|Boot to disk| H + D -->|Custom script| O diff --git a/pages/bare_metal_cloud/dedicated_servers/boot-process/images/boot-process.svg b/pages/bare_metal_cloud/dedicated_servers/boot-process/images/boot-process.svg new file mode 100644 index 00000000000..df34e27dcda --- /dev/null +++ b/pages/bare_metal_cloud/dedicated_servers/boot-process/images/boot-process.svg @@ -0,0 +1 @@ +

Custom boot script

Boot to Disk

Customer Rescue

Network Boot (every boot)

UEFI boot

Legacy boot

Yes

No

Customer rescue

Boot to disk

Custom script

1. PXE boot via DHCP
on public interface
2. Download iPXE
3. Query boot service
4. Execute script

Download, verify and apply
CPU microcode

Boot live
rescue system

Download, verify and apply
CPU microcode

Firmware?

sanboot to
efiBootloaderPath

sanboot to
first disk

Success?

OS loads

rEFInd fallback
auto-detects EFI bootloaders

Execute user-defined
iPXE script
no microcode loading

 \ No newline at end of file diff --git a/pages/bare_metal_cloud/dedicated_servers/boot-process/meta.yaml b/pages/bare_metal_cloud/dedicated_servers/boot-process/meta.yaml new file mode 100644 index 00000000000..c17e5a8519d --- /dev/null +++ b/pages/bare_metal_cloud/dedicated_servers/boot-process/meta.yaml @@ -0,0 +1,2 @@ +id: 00d8ab6e-71ee-4a64-aaf3-7c2cbd52acaf +full_slug: dedicated-servers-boot-process \ No newline at end of file diff --git a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.de-de.md b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.de-de.md index 0260ff67219..e0760f607fd 100644 --- a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.de-de.md +++ b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.de-de.md @@ -1,7 +1,7 @@ --- title: Bring Your Own Image (BYOI) (EN) excerpt: Find out how to easily deploy your own images on dedicated servers -updated: 2025-04-29 +updated: 2026-02-06 --- ## Objective @@ -153,7 +153,7 @@ Once you completed the fields, start the deployment by clicking `Execute`{.actio ¹ Can either be a `#cloud-config` or a script. It must be in one-line, and have `\n` for line-return
² Use only if you need HTTP Headers, such as `Basic Auth`
-³ Examples of Efi bootloader path: +³ The EFI bootloader path is used by iPXE to boot your operating system. For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). Examples: | Operating System | efiBootloaderPath | |-|-| @@ -192,4 +192,6 @@ The following table gives an overview of well known customer errors and how to f [Bring Your Own Image (BYOI) / Bring Your Own Linux (BYOLinux), a comparison sheet](/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image-versus-bring-your-own-linux) +[Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process) + Join our user community on . diff --git a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.en-asia.md b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.en-asia.md index c569cc73f05..3d47be3a29a 100644 --- a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.en-asia.md +++ b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.en-asia.md @@ -1,7 +1,7 @@ --- title: Bring Your Own Image (BYOI) excerpt: Find out how to easily deploy your own images on dedicated servers -updated: 2025-04-29 +updated: 2026-02-06 --- ## Objective @@ -153,7 +153,7 @@ Once you completed the fields, start the deployment by clicking `Execute`{.actio ¹ Can either be a `#cloud-config` or a script. It must be in one-line, and have `\n` for line-return
² Use only if you need HTTP Headers, such as `Basic Auth`
-³ Examples of Efi bootloader path: +³ The EFI bootloader path is used by iPXE to boot your operating system. For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). Examples: | Operating System | efiBootloaderPath | |-|-| @@ -192,4 +192,6 @@ The following table gives an overview of well known customer errors and how to f [Bring Your Own Image (BYOI) / Bring Your Own Linux (BYOLinux), a comparison sheet](/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image-versus-bring-your-own-linux) +[Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process) + Join our user community on . diff --git a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.en-au.md b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.en-au.md index c569cc73f05..3d47be3a29a 100644 --- a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.en-au.md +++ b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.en-au.md @@ -1,7 +1,7 @@ --- title: Bring Your Own Image (BYOI) excerpt: Find out how to easily deploy your own images on dedicated servers -updated: 2025-04-29 +updated: 2026-02-06 --- ## Objective @@ -153,7 +153,7 @@ Once you completed the fields, start the deployment by clicking `Execute`{.actio ¹ Can either be a `#cloud-config` or a script. It must be in one-line, and have `\n` for line-return
² Use only if you need HTTP Headers, such as `Basic Auth`
-³ Examples of Efi bootloader path: +³ The EFI bootloader path is used by iPXE to boot your operating system. For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). Examples: | Operating System | efiBootloaderPath | |-|-| @@ -192,4 +192,6 @@ The following table gives an overview of well known customer errors and how to f [Bring Your Own Image (BYOI) / Bring Your Own Linux (BYOLinux), a comparison sheet](/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image-versus-bring-your-own-linux) +[Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process) + Join our user community on . diff --git a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.en-ca.md b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.en-ca.md index c569cc73f05..3d47be3a29a 100644 --- a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.en-ca.md +++ b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.en-ca.md @@ -1,7 +1,7 @@ --- title: Bring Your Own Image (BYOI) excerpt: Find out how to easily deploy your own images on dedicated servers -updated: 2025-04-29 +updated: 2026-02-06 --- ## Objective @@ -153,7 +153,7 @@ Once you completed the fields, start the deployment by clicking `Execute`{.actio ¹ Can either be a `#cloud-config` or a script. It must be in one-line, and have `\n` for line-return
² Use only if you need HTTP Headers, such as `Basic Auth`
-³ Examples of Efi bootloader path: +³ The EFI bootloader path is used by iPXE to boot your operating system. For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). Examples: | Operating System | efiBootloaderPath | |-|-| @@ -192,4 +192,6 @@ The following table gives an overview of well known customer errors and how to f [Bring Your Own Image (BYOI) / Bring Your Own Linux (BYOLinux), a comparison sheet](/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image-versus-bring-your-own-linux) +[Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process) + Join our user community on . diff --git a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.en-gb.md index c569cc73f05..3d47be3a29a 100644 --- a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.en-gb.md +++ b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.en-gb.md @@ -1,7 +1,7 @@ --- title: Bring Your Own Image (BYOI) excerpt: Find out how to easily deploy your own images on dedicated servers -updated: 2025-04-29 +updated: 2026-02-06 --- ## Objective @@ -153,7 +153,7 @@ Once you completed the fields, start the deployment by clicking `Execute`{.actio ¹ Can either be a `#cloud-config` or a script. It must be in one-line, and have `\n` for line-return
² Use only if you need HTTP Headers, such as `Basic Auth`
-³ Examples of Efi bootloader path: +³ The EFI bootloader path is used by iPXE to boot your operating system. For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). Examples: | Operating System | efiBootloaderPath | |-|-| @@ -192,4 +192,6 @@ The following table gives an overview of well known customer errors and how to f [Bring Your Own Image (BYOI) / Bring Your Own Linux (BYOLinux), a comparison sheet](/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image-versus-bring-your-own-linux) +[Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process) + Join our user community on . diff --git a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.en-ie.md b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.en-ie.md index c569cc73f05..3d47be3a29a 100644 --- a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.en-ie.md +++ b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.en-ie.md @@ -1,7 +1,7 @@ --- title: Bring Your Own Image (BYOI) excerpt: Find out how to easily deploy your own images on dedicated servers -updated: 2025-04-29 +updated: 2026-02-06 --- ## Objective @@ -153,7 +153,7 @@ Once you completed the fields, start the deployment by clicking `Execute`{.actio ¹ Can either be a `#cloud-config` or a script. It must be in one-line, and have `\n` for line-return
² Use only if you need HTTP Headers, such as `Basic Auth`
-³ Examples of Efi bootloader path: +³ The EFI bootloader path is used by iPXE to boot your operating system. For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). Examples: | Operating System | efiBootloaderPath | |-|-| @@ -192,4 +192,6 @@ The following table gives an overview of well known customer errors and how to f [Bring Your Own Image (BYOI) / Bring Your Own Linux (BYOLinux), a comparison sheet](/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image-versus-bring-your-own-linux) +[Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process) + Join our user community on . diff --git a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.en-sg.md b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.en-sg.md index c569cc73f05..3d47be3a29a 100644 --- a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.en-sg.md +++ b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.en-sg.md @@ -1,7 +1,7 @@ --- title: Bring Your Own Image (BYOI) excerpt: Find out how to easily deploy your own images on dedicated servers -updated: 2025-04-29 +updated: 2026-02-06 --- ## Objective @@ -153,7 +153,7 @@ Once you completed the fields, start the deployment by clicking `Execute`{.actio ¹ Can either be a `#cloud-config` or a script. It must be in one-line, and have `\n` for line-return
² Use only if you need HTTP Headers, such as `Basic Auth`
-³ Examples of Efi bootloader path: +³ The EFI bootloader path is used by iPXE to boot your operating system. For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). Examples: | Operating System | efiBootloaderPath | |-|-| @@ -192,4 +192,6 @@ The following table gives an overview of well known customer errors and how to f [Bring Your Own Image (BYOI) / Bring Your Own Linux (BYOLinux), a comparison sheet](/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image-versus-bring-your-own-linux) +[Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process) + Join our user community on . diff --git a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.en-us.md b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.en-us.md index c569cc73f05..3d47be3a29a 100644 --- a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.en-us.md +++ b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.en-us.md @@ -1,7 +1,7 @@ --- title: Bring Your Own Image (BYOI) excerpt: Find out how to easily deploy your own images on dedicated servers -updated: 2025-04-29 +updated: 2026-02-06 --- ## Objective @@ -153,7 +153,7 @@ Once you completed the fields, start the deployment by clicking `Execute`{.actio ¹ Can either be a `#cloud-config` or a script. It must be in one-line, and have `\n` for line-return
² Use only if you need HTTP Headers, such as `Basic Auth`
-³ Examples of Efi bootloader path: +³ The EFI bootloader path is used by iPXE to boot your operating system. For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). Examples: | Operating System | efiBootloaderPath | |-|-| @@ -192,4 +192,6 @@ The following table gives an overview of well known customer errors and how to f [Bring Your Own Image (BYOI) / Bring Your Own Linux (BYOLinux), a comparison sheet](/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image-versus-bring-your-own-linux) +[Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process) + Join our user community on . diff --git a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.es-es.md b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.es-es.md index 0260ff67219..e0760f607fd 100644 --- a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.es-es.md +++ b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.es-es.md @@ -1,7 +1,7 @@ --- title: Bring Your Own Image (BYOI) (EN) excerpt: Find out how to easily deploy your own images on dedicated servers -updated: 2025-04-29 +updated: 2026-02-06 --- ## Objective @@ -153,7 +153,7 @@ Once you completed the fields, start the deployment by clicking `Execute`{.actio ¹ Can either be a `#cloud-config` or a script. It must be in one-line, and have `\n` for line-return
² Use only if you need HTTP Headers, such as `Basic Auth`
-³ Examples of Efi bootloader path: +³ The EFI bootloader path is used by iPXE to boot your operating system. For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). Examples: | Operating System | efiBootloaderPath | |-|-| @@ -192,4 +192,6 @@ The following table gives an overview of well known customer errors and how to f [Bring Your Own Image (BYOI) / Bring Your Own Linux (BYOLinux), a comparison sheet](/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image-versus-bring-your-own-linux) +[Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process) + Join our user community on . diff --git a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.es-us.md b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.es-us.md index 0260ff67219..e0760f607fd 100644 --- a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.es-us.md +++ b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.es-us.md @@ -1,7 +1,7 @@ --- title: Bring Your Own Image (BYOI) (EN) excerpt: Find out how to easily deploy your own images on dedicated servers -updated: 2025-04-29 +updated: 2026-02-06 --- ## Objective @@ -153,7 +153,7 @@ Once you completed the fields, start the deployment by clicking `Execute`{.actio ¹ Can either be a `#cloud-config` or a script. It must be in one-line, and have `\n` for line-return
² Use only if you need HTTP Headers, such as `Basic Auth`
-³ Examples of Efi bootloader path: +³ The EFI bootloader path is used by iPXE to boot your operating system. For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). Examples: | Operating System | efiBootloaderPath | |-|-| @@ -192,4 +192,6 @@ The following table gives an overview of well known customer errors and how to f [Bring Your Own Image (BYOI) / Bring Your Own Linux (BYOLinux), a comparison sheet](/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image-versus-bring-your-own-linux) +[Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process) + Join our user community on . diff --git a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.fr-ca.md b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.fr-ca.md index 7baa36b4a39..863601f296a 100644 --- a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.fr-ca.md +++ b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.fr-ca.md @@ -1,7 +1,7 @@ --- title: Bring Your Own Image (BYOI) excerpt: Découvrez comment déployer facilement vos propres images sur des serveurs dédiés -updated: 2025-04-29 +updated: 2026-02-06 --- ## Objectif @@ -153,7 +153,7 @@ Une fois les champs complétés, démarrez le déploiement en cliquant sur `Exec ¹ Il peut s'agir d'un `#cloud-config` ou d'un script. Il doit être sur une ligne et avoir `\n` pour la ligne-retour.
² À utiliser uniquement si vous avez besoin d'en-têtes HTTP, tels que `Basic Auth`
-³ Exemples de chemin EFI : +³ Le chemin du bootloader EFI est utilisé par iPXE pour démarrer votre système d'exploitation. Pour plus d'informations, consultez notre guide « [Comprendre le processus de démarrage des serveurs dédiés](/pages/bare_metal_cloud/dedicated_servers/boot-process) ». Exemples : | Système d'exploitation | efiBootloaderPath | |-|-| diff --git a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.fr-fr.md b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.fr-fr.md index 7baa36b4a39..863601f296a 100644 --- a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.fr-fr.md +++ b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.fr-fr.md @@ -1,7 +1,7 @@ --- title: Bring Your Own Image (BYOI) excerpt: Découvrez comment déployer facilement vos propres images sur des serveurs dédiés -updated: 2025-04-29 +updated: 2026-02-06 --- ## Objectif @@ -153,7 +153,7 @@ Une fois les champs complétés, démarrez le déploiement en cliquant sur `Exec ¹ Il peut s'agir d'un `#cloud-config` ou d'un script. Il doit être sur une ligne et avoir `\n` pour la ligne-retour.
² À utiliser uniquement si vous avez besoin d'en-têtes HTTP, tels que `Basic Auth`
-³ Exemples de chemin EFI : +³ Le chemin du bootloader EFI est utilisé par iPXE pour démarrer votre système d'exploitation. Pour plus d'informations, consultez notre guide « [Comprendre le processus de démarrage des serveurs dédiés](/pages/bare_metal_cloud/dedicated_servers/boot-process) ». Exemples : | Système d'exploitation | efiBootloaderPath | |-|-| diff --git a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.it-it.md b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.it-it.md index 0260ff67219..e0760f607fd 100644 --- a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.it-it.md +++ b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.it-it.md @@ -1,7 +1,7 @@ --- title: Bring Your Own Image (BYOI) (EN) excerpt: Find out how to easily deploy your own images on dedicated servers -updated: 2025-04-29 +updated: 2026-02-06 --- ## Objective @@ -153,7 +153,7 @@ Once you completed the fields, start the deployment by clicking `Execute`{.actio ¹ Can either be a `#cloud-config` or a script. It must be in one-line, and have `\n` for line-return
² Use only if you need HTTP Headers, such as `Basic Auth`
-³ Examples of Efi bootloader path: +³ The EFI bootloader path is used by iPXE to boot your operating system. For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). Examples: | Operating System | efiBootloaderPath | |-|-| @@ -192,4 +192,6 @@ The following table gives an overview of well known customer errors and how to f [Bring Your Own Image (BYOI) / Bring Your Own Linux (BYOLinux), a comparison sheet](/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image-versus-bring-your-own-linux) +[Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process) + Join our user community on . diff --git a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.pl-pl.md b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.pl-pl.md index 0260ff67219..e0760f607fd 100755 --- a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.pl-pl.md +++ b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.pl-pl.md @@ -1,7 +1,7 @@ --- title: Bring Your Own Image (BYOI) (EN) excerpt: Find out how to easily deploy your own images on dedicated servers -updated: 2025-04-29 +updated: 2026-02-06 --- ## Objective @@ -153,7 +153,7 @@ Once you completed the fields, start the deployment by clicking `Execute`{.actio ¹ Can either be a `#cloud-config` or a script. It must be in one-line, and have `\n` for line-return
² Use only if you need HTTP Headers, such as `Basic Auth`
-³ Examples of Efi bootloader path: +³ The EFI bootloader path is used by iPXE to boot your operating system. For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). Examples: | Operating System | efiBootloaderPath | |-|-| @@ -192,4 +192,6 @@ The following table gives an overview of well known customer errors and how to f [Bring Your Own Image (BYOI) / Bring Your Own Linux (BYOLinux), a comparison sheet](/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image-versus-bring-your-own-linux) +[Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process) + Join our user community on . diff --git a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.pt-pt.md b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.pt-pt.md index 0260ff67219..e0760f607fd 100644 --- a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.pt-pt.md +++ b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.pt-pt.md @@ -1,7 +1,7 @@ --- title: Bring Your Own Image (BYOI) (EN) excerpt: Find out how to easily deploy your own images on dedicated servers -updated: 2025-04-29 +updated: 2026-02-06 --- ## Objective @@ -153,7 +153,7 @@ Once you completed the fields, start the deployment by clicking `Execute`{.actio ¹ Can either be a `#cloud-config` or a script. It must be in one-line, and have `\n` for line-return
² Use only if you need HTTP Headers, such as `Basic Auth`
-³ Examples of Efi bootloader path: +³ The EFI bootloader path is used by iPXE to boot your operating system. For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). Examples: | Operating System | efiBootloaderPath | |-|-| @@ -192,4 +192,6 @@ The following table gives an overview of well known customer errors and how to f [Bring Your Own Image (BYOI) / Bring Your Own Linux (BYOLinux), a comparison sheet](/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image-versus-bring-your-own-linux) +[Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process) + Join our user community on . diff --git a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.de-de.md b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.de-de.md index 26d5553fc6c..7b1836d7d95 100644 --- a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.de-de.md +++ b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.de-de.md @@ -1,7 +1,7 @@ --- title: Bring Your Own Linux (BYOLinux) (EN) excerpt: Find out how to easily deploy your own Linux images on dedicated servers -updated: 2025-09-30 +updated: 2026-02-06 --- ## Objective @@ -21,7 +21,7 @@ In addition to the requirement and limitations mentioned below, you must ensure - Access to the [OVHcloud Control Panel](/links/manager) (for the "[Deployment via Control Panel](#viacontrolpanel)" method) - Access to the [OVHcloud API](/pages/manage_and_operate/api/first-steps) (for the "[Deployment via API](#viaapi)" section of this guide) - Your image must be smaller than the Server RAM minus 3GiB -- An executable script `/root/.ovh/make_image_bootable.sh`, which will reinstall and configure the bootloader, [for example GRUB](https://github.com/ovh/bringyourownlinux/blob/main/example_build/files/make_image_bootable.sh) +- An executable script `/root/.ovh/make_image_bootable.sh`, which will reinstall and configure the bootloader, [for example GRUB](https://github.com/ovh/bringyourownlinux/blob/main/example_build/files/make_image_bootable.sh). This script must not alter the NVRAM boot order (e.g. use `grub-install --no-nvram`). For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). > [!warning] > @@ -148,7 +148,7 @@ Once you completed the fields, start the deployment by clicking `Execute`{.actio ¹ Can either be a `#cloud-config` or a script. It must be in one-line, and have `\n` for line-return
² Use only if you need HTTP Headers, such as `Basic Auth`
-³ Examples of Efi bootloader path: +³ The EFI bootloader path is used by iPXE to boot your operating system. For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). Examples: | Operating System | efiBootloaderPath | |-|-| @@ -192,4 +192,6 @@ See OVHcloud API and Storage [Common customer errors](/pages/bare_metal_cloud/de [Bring Your Own Image (BYOI) / Bring Your Own Linux (BYOLinux), a comparison sheet](/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image-versus-bring-your-own-linux) +[Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process) + Join our user community on . diff --git a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.en-asia.md b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.en-asia.md index db59e88b438..30ced83c7e6 100644 --- a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.en-asia.md +++ b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.en-asia.md @@ -1,7 +1,7 @@ --- title: Bring Your Own Linux (BYOLinux) excerpt: Find out how to easily deploy your own Linux images on dedicated servers -updated: 2025-09-30 +updated: 2026-02-06 --- ## Objective @@ -21,7 +21,7 @@ In addition to the requirement and limitations mentioned below, you must ensure - Access to the [OVHcloud Control Panel](/links/manager) (for the "[Deployment via Control Panel](#viacontrolpanel)" method) - Access to the [OVHcloud API](/pages/manage_and_operate/api/first-steps) (for the "[Deployment via API](#viaapi)" section of this guide) - Your image must be smaller than the Server RAM minus 3GiB -- An executable script `/root/.ovh/make_image_bootable.sh`, which will reinstall and configure the bootloader, [for example GRUB](https://github.com/ovh/bringyourownlinux/blob/main/example_build/files/make_image_bootable.sh) +- An executable script `/root/.ovh/make_image_bootable.sh`, which will reinstall and configure the bootloader, [for example GRUB](https://github.com/ovh/bringyourownlinux/blob/main/example_build/files/make_image_bootable.sh). This script must not alter the NVRAM boot order (e.g. use `grub-install --no-nvram`). For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). > [!warning] > @@ -148,7 +148,7 @@ Once you completed the fields, start the deployment by clicking `Execute`{.actio ¹ Can either be a `#cloud-config` or a script. It must be in one-line, and have `\n` for line-return
² Use only if you need HTTP Headers, such as `Basic Auth`
-³ Examples of Efi bootloader path: +³ The EFI bootloader path is used by iPXE to boot your operating system. For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). Examples: | Operating System | efiBootloaderPath | |-|-| @@ -192,4 +192,6 @@ See OVHcloud API and Storage [Common customer errors](/pages/bare_metal_cloud/de [Bring Your Own Image (BYOI) / Bring Your Own Linux (BYOLinux), a comparison sheet](/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image-versus-bring-your-own-linux) +[Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process) + Join our user community on . diff --git a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.en-au.md b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.en-au.md index db59e88b438..30ced83c7e6 100644 --- a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.en-au.md +++ b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.en-au.md @@ -1,7 +1,7 @@ --- title: Bring Your Own Linux (BYOLinux) excerpt: Find out how to easily deploy your own Linux images on dedicated servers -updated: 2025-09-30 +updated: 2026-02-06 --- ## Objective @@ -21,7 +21,7 @@ In addition to the requirement and limitations mentioned below, you must ensure - Access to the [OVHcloud Control Panel](/links/manager) (for the "[Deployment via Control Panel](#viacontrolpanel)" method) - Access to the [OVHcloud API](/pages/manage_and_operate/api/first-steps) (for the "[Deployment via API](#viaapi)" section of this guide) - Your image must be smaller than the Server RAM minus 3GiB -- An executable script `/root/.ovh/make_image_bootable.sh`, which will reinstall and configure the bootloader, [for example GRUB](https://github.com/ovh/bringyourownlinux/blob/main/example_build/files/make_image_bootable.sh) +- An executable script `/root/.ovh/make_image_bootable.sh`, which will reinstall and configure the bootloader, [for example GRUB](https://github.com/ovh/bringyourownlinux/blob/main/example_build/files/make_image_bootable.sh). This script must not alter the NVRAM boot order (e.g. use `grub-install --no-nvram`). For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). > [!warning] > @@ -148,7 +148,7 @@ Once you completed the fields, start the deployment by clicking `Execute`{.actio ¹ Can either be a `#cloud-config` or a script. It must be in one-line, and have `\n` for line-return
² Use only if you need HTTP Headers, such as `Basic Auth`
-³ Examples of Efi bootloader path: +³ The EFI bootloader path is used by iPXE to boot your operating system. For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). Examples: | Operating System | efiBootloaderPath | |-|-| @@ -192,4 +192,6 @@ See OVHcloud API and Storage [Common customer errors](/pages/bare_metal_cloud/de [Bring Your Own Image (BYOI) / Bring Your Own Linux (BYOLinux), a comparison sheet](/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image-versus-bring-your-own-linux) +[Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process) + Join our user community on . diff --git a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.en-ca.md b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.en-ca.md index db59e88b438..30ced83c7e6 100644 --- a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.en-ca.md +++ b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.en-ca.md @@ -1,7 +1,7 @@ --- title: Bring Your Own Linux (BYOLinux) excerpt: Find out how to easily deploy your own Linux images on dedicated servers -updated: 2025-09-30 +updated: 2026-02-06 --- ## Objective @@ -21,7 +21,7 @@ In addition to the requirement and limitations mentioned below, you must ensure - Access to the [OVHcloud Control Panel](/links/manager) (for the "[Deployment via Control Panel](#viacontrolpanel)" method) - Access to the [OVHcloud API](/pages/manage_and_operate/api/first-steps) (for the "[Deployment via API](#viaapi)" section of this guide) - Your image must be smaller than the Server RAM minus 3GiB -- An executable script `/root/.ovh/make_image_bootable.sh`, which will reinstall and configure the bootloader, [for example GRUB](https://github.com/ovh/bringyourownlinux/blob/main/example_build/files/make_image_bootable.sh) +- An executable script `/root/.ovh/make_image_bootable.sh`, which will reinstall and configure the bootloader, [for example GRUB](https://github.com/ovh/bringyourownlinux/blob/main/example_build/files/make_image_bootable.sh). This script must not alter the NVRAM boot order (e.g. use `grub-install --no-nvram`). For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). > [!warning] > @@ -148,7 +148,7 @@ Once you completed the fields, start the deployment by clicking `Execute`{.actio ¹ Can either be a `#cloud-config` or a script. It must be in one-line, and have `\n` for line-return
² Use only if you need HTTP Headers, such as `Basic Auth`
-³ Examples of Efi bootloader path: +³ The EFI bootloader path is used by iPXE to boot your operating system. For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). Examples: | Operating System | efiBootloaderPath | |-|-| @@ -192,4 +192,6 @@ See OVHcloud API and Storage [Common customer errors](/pages/bare_metal_cloud/de [Bring Your Own Image (BYOI) / Bring Your Own Linux (BYOLinux), a comparison sheet](/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image-versus-bring-your-own-linux) +[Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process) + Join our user community on . diff --git a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.en-gb.md index db59e88b438..30ced83c7e6 100644 --- a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.en-gb.md +++ b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.en-gb.md @@ -1,7 +1,7 @@ --- title: Bring Your Own Linux (BYOLinux) excerpt: Find out how to easily deploy your own Linux images on dedicated servers -updated: 2025-09-30 +updated: 2026-02-06 --- ## Objective @@ -21,7 +21,7 @@ In addition to the requirement and limitations mentioned below, you must ensure - Access to the [OVHcloud Control Panel](/links/manager) (for the "[Deployment via Control Panel](#viacontrolpanel)" method) - Access to the [OVHcloud API](/pages/manage_and_operate/api/first-steps) (for the "[Deployment via API](#viaapi)" section of this guide) - Your image must be smaller than the Server RAM minus 3GiB -- An executable script `/root/.ovh/make_image_bootable.sh`, which will reinstall and configure the bootloader, [for example GRUB](https://github.com/ovh/bringyourownlinux/blob/main/example_build/files/make_image_bootable.sh) +- An executable script `/root/.ovh/make_image_bootable.sh`, which will reinstall and configure the bootloader, [for example GRUB](https://github.com/ovh/bringyourownlinux/blob/main/example_build/files/make_image_bootable.sh). This script must not alter the NVRAM boot order (e.g. use `grub-install --no-nvram`). For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). > [!warning] > @@ -148,7 +148,7 @@ Once you completed the fields, start the deployment by clicking `Execute`{.actio ¹ Can either be a `#cloud-config` or a script. It must be in one-line, and have `\n` for line-return
² Use only if you need HTTP Headers, such as `Basic Auth`
-³ Examples of Efi bootloader path: +³ The EFI bootloader path is used by iPXE to boot your operating system. For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). Examples: | Operating System | efiBootloaderPath | |-|-| @@ -192,4 +192,6 @@ See OVHcloud API and Storage [Common customer errors](/pages/bare_metal_cloud/de [Bring Your Own Image (BYOI) / Bring Your Own Linux (BYOLinux), a comparison sheet](/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image-versus-bring-your-own-linux) +[Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process) + Join our user community on . diff --git a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.en-ie.md b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.en-ie.md index db59e88b438..30ced83c7e6 100644 --- a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.en-ie.md +++ b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.en-ie.md @@ -1,7 +1,7 @@ --- title: Bring Your Own Linux (BYOLinux) excerpt: Find out how to easily deploy your own Linux images on dedicated servers -updated: 2025-09-30 +updated: 2026-02-06 --- ## Objective @@ -21,7 +21,7 @@ In addition to the requirement and limitations mentioned below, you must ensure - Access to the [OVHcloud Control Panel](/links/manager) (for the "[Deployment via Control Panel](#viacontrolpanel)" method) - Access to the [OVHcloud API](/pages/manage_and_operate/api/first-steps) (for the "[Deployment via API](#viaapi)" section of this guide) - Your image must be smaller than the Server RAM minus 3GiB -- An executable script `/root/.ovh/make_image_bootable.sh`, which will reinstall and configure the bootloader, [for example GRUB](https://github.com/ovh/bringyourownlinux/blob/main/example_build/files/make_image_bootable.sh) +- An executable script `/root/.ovh/make_image_bootable.sh`, which will reinstall and configure the bootloader, [for example GRUB](https://github.com/ovh/bringyourownlinux/blob/main/example_build/files/make_image_bootable.sh). This script must not alter the NVRAM boot order (e.g. use `grub-install --no-nvram`). For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). > [!warning] > @@ -148,7 +148,7 @@ Once you completed the fields, start the deployment by clicking `Execute`{.actio ¹ Can either be a `#cloud-config` or a script. It must be in one-line, and have `\n` for line-return
² Use only if you need HTTP Headers, such as `Basic Auth`
-³ Examples of Efi bootloader path: +³ The EFI bootloader path is used by iPXE to boot your operating system. For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). Examples: | Operating System | efiBootloaderPath | |-|-| @@ -192,4 +192,6 @@ See OVHcloud API and Storage [Common customer errors](/pages/bare_metal_cloud/de [Bring Your Own Image (BYOI) / Bring Your Own Linux (BYOLinux), a comparison sheet](/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image-versus-bring-your-own-linux) +[Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process) + Join our user community on . diff --git a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.en-sg.md b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.en-sg.md index db59e88b438..30ced83c7e6 100644 --- a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.en-sg.md +++ b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.en-sg.md @@ -1,7 +1,7 @@ --- title: Bring Your Own Linux (BYOLinux) excerpt: Find out how to easily deploy your own Linux images on dedicated servers -updated: 2025-09-30 +updated: 2026-02-06 --- ## Objective @@ -21,7 +21,7 @@ In addition to the requirement and limitations mentioned below, you must ensure - Access to the [OVHcloud Control Panel](/links/manager) (for the "[Deployment via Control Panel](#viacontrolpanel)" method) - Access to the [OVHcloud API](/pages/manage_and_operate/api/first-steps) (for the "[Deployment via API](#viaapi)" section of this guide) - Your image must be smaller than the Server RAM minus 3GiB -- An executable script `/root/.ovh/make_image_bootable.sh`, which will reinstall and configure the bootloader, [for example GRUB](https://github.com/ovh/bringyourownlinux/blob/main/example_build/files/make_image_bootable.sh) +- An executable script `/root/.ovh/make_image_bootable.sh`, which will reinstall and configure the bootloader, [for example GRUB](https://github.com/ovh/bringyourownlinux/blob/main/example_build/files/make_image_bootable.sh). This script must not alter the NVRAM boot order (e.g. use `grub-install --no-nvram`). For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). > [!warning] > @@ -148,7 +148,7 @@ Once you completed the fields, start the deployment by clicking `Execute`{.actio ¹ Can either be a `#cloud-config` or a script. It must be in one-line, and have `\n` for line-return
² Use only if you need HTTP Headers, such as `Basic Auth`
-³ Examples of Efi bootloader path: +³ The EFI bootloader path is used by iPXE to boot your operating system. For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). Examples: | Operating System | efiBootloaderPath | |-|-| @@ -192,4 +192,6 @@ See OVHcloud API and Storage [Common customer errors](/pages/bare_metal_cloud/de [Bring Your Own Image (BYOI) / Bring Your Own Linux (BYOLinux), a comparison sheet](/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image-versus-bring-your-own-linux) +[Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process) + Join our user community on . diff --git a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.en-us.md b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.en-us.md index db59e88b438..30ced83c7e6 100644 --- a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.en-us.md +++ b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.en-us.md @@ -1,7 +1,7 @@ --- title: Bring Your Own Linux (BYOLinux) excerpt: Find out how to easily deploy your own Linux images on dedicated servers -updated: 2025-09-30 +updated: 2026-02-06 --- ## Objective @@ -21,7 +21,7 @@ In addition to the requirement and limitations mentioned below, you must ensure - Access to the [OVHcloud Control Panel](/links/manager) (for the "[Deployment via Control Panel](#viacontrolpanel)" method) - Access to the [OVHcloud API](/pages/manage_and_operate/api/first-steps) (for the "[Deployment via API](#viaapi)" section of this guide) - Your image must be smaller than the Server RAM minus 3GiB -- An executable script `/root/.ovh/make_image_bootable.sh`, which will reinstall and configure the bootloader, [for example GRUB](https://github.com/ovh/bringyourownlinux/blob/main/example_build/files/make_image_bootable.sh) +- An executable script `/root/.ovh/make_image_bootable.sh`, which will reinstall and configure the bootloader, [for example GRUB](https://github.com/ovh/bringyourownlinux/blob/main/example_build/files/make_image_bootable.sh). This script must not alter the NVRAM boot order (e.g. use `grub-install --no-nvram`). For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). > [!warning] > @@ -148,7 +148,7 @@ Once you completed the fields, start the deployment by clicking `Execute`{.actio ¹ Can either be a `#cloud-config` or a script. It must be in one-line, and have `\n` for line-return
² Use only if you need HTTP Headers, such as `Basic Auth`
-³ Examples of Efi bootloader path: +³ The EFI bootloader path is used by iPXE to boot your operating system. For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). Examples: | Operating System | efiBootloaderPath | |-|-| @@ -192,4 +192,6 @@ See OVHcloud API and Storage [Common customer errors](/pages/bare_metal_cloud/de [Bring Your Own Image (BYOI) / Bring Your Own Linux (BYOLinux), a comparison sheet](/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image-versus-bring-your-own-linux) +[Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process) + Join our user community on . diff --git a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.es-es.md b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.es-es.md index 26d5553fc6c..7b1836d7d95 100644 --- a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.es-es.md +++ b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.es-es.md @@ -1,7 +1,7 @@ --- title: Bring Your Own Linux (BYOLinux) (EN) excerpt: Find out how to easily deploy your own Linux images on dedicated servers -updated: 2025-09-30 +updated: 2026-02-06 --- ## Objective @@ -21,7 +21,7 @@ In addition to the requirement and limitations mentioned below, you must ensure - Access to the [OVHcloud Control Panel](/links/manager) (for the "[Deployment via Control Panel](#viacontrolpanel)" method) - Access to the [OVHcloud API](/pages/manage_and_operate/api/first-steps) (for the "[Deployment via API](#viaapi)" section of this guide) - Your image must be smaller than the Server RAM minus 3GiB -- An executable script `/root/.ovh/make_image_bootable.sh`, which will reinstall and configure the bootloader, [for example GRUB](https://github.com/ovh/bringyourownlinux/blob/main/example_build/files/make_image_bootable.sh) +- An executable script `/root/.ovh/make_image_bootable.sh`, which will reinstall and configure the bootloader, [for example GRUB](https://github.com/ovh/bringyourownlinux/blob/main/example_build/files/make_image_bootable.sh). This script must not alter the NVRAM boot order (e.g. use `grub-install --no-nvram`). For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). > [!warning] > @@ -148,7 +148,7 @@ Once you completed the fields, start the deployment by clicking `Execute`{.actio ¹ Can either be a `#cloud-config` or a script. It must be in one-line, and have `\n` for line-return
² Use only if you need HTTP Headers, such as `Basic Auth`
-³ Examples of Efi bootloader path: +³ The EFI bootloader path is used by iPXE to boot your operating system. For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). Examples: | Operating System | efiBootloaderPath | |-|-| @@ -192,4 +192,6 @@ See OVHcloud API and Storage [Common customer errors](/pages/bare_metal_cloud/de [Bring Your Own Image (BYOI) / Bring Your Own Linux (BYOLinux), a comparison sheet](/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image-versus-bring-your-own-linux) +[Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process) + Join our user community on . diff --git a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.es-us.md b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.es-us.md index 26d5553fc6c..7b1836d7d95 100644 --- a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.es-us.md +++ b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.es-us.md @@ -1,7 +1,7 @@ --- title: Bring Your Own Linux (BYOLinux) (EN) excerpt: Find out how to easily deploy your own Linux images on dedicated servers -updated: 2025-09-30 +updated: 2026-02-06 --- ## Objective @@ -21,7 +21,7 @@ In addition to the requirement and limitations mentioned below, you must ensure - Access to the [OVHcloud Control Panel](/links/manager) (for the "[Deployment via Control Panel](#viacontrolpanel)" method) - Access to the [OVHcloud API](/pages/manage_and_operate/api/first-steps) (for the "[Deployment via API](#viaapi)" section of this guide) - Your image must be smaller than the Server RAM minus 3GiB -- An executable script `/root/.ovh/make_image_bootable.sh`, which will reinstall and configure the bootloader, [for example GRUB](https://github.com/ovh/bringyourownlinux/blob/main/example_build/files/make_image_bootable.sh) +- An executable script `/root/.ovh/make_image_bootable.sh`, which will reinstall and configure the bootloader, [for example GRUB](https://github.com/ovh/bringyourownlinux/blob/main/example_build/files/make_image_bootable.sh). This script must not alter the NVRAM boot order (e.g. use `grub-install --no-nvram`). For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). > [!warning] > @@ -148,7 +148,7 @@ Once you completed the fields, start the deployment by clicking `Execute`{.actio ¹ Can either be a `#cloud-config` or a script. It must be in one-line, and have `\n` for line-return
² Use only if you need HTTP Headers, such as `Basic Auth`
-³ Examples of Efi bootloader path: +³ The EFI bootloader path is used by iPXE to boot your operating system. For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). Examples: | Operating System | efiBootloaderPath | |-|-| @@ -192,4 +192,6 @@ See OVHcloud API and Storage [Common customer errors](/pages/bare_metal_cloud/de [Bring Your Own Image (BYOI) / Bring Your Own Linux (BYOLinux), a comparison sheet](/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image-versus-bring-your-own-linux) +[Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process) + Join our user community on . diff --git a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.fr-ca.md b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.fr-ca.md index f1f047dc082..70b1d85200c 100644 --- a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.fr-ca.md +++ b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.fr-ca.md @@ -1,7 +1,7 @@ --- title: Bring Your Own Linux (BYOLinux) excerpt: Découvrez comment déployer facilement vos propres images Linux sur des serveurs dédiés -updated: 2025-09-30 +updated: 2026-02-06 --- ## Objectif @@ -21,7 +21,7 @@ En plus des prérequis et limitations mentionnés ci-dessous, vous devez vous as - Être connecté à l'[espace client OVHcloud](/links/manager) (pour la méthode de [déploiement via l'espace client](#viacontrolpanel) de ce guide) - Avoir accès à l'[API OVHcloud](/pages/manage_and_operate/api/first-steps) (pour la méthode de [déploiement via l'API](#viaapi) de ce guide) - Votre image doit être inférieure à la RAM du serveur moins 3 Gio -- Un script `/root/.ovh/make_image_bootable.sh` exécutable, qui installera ou configurera le bootloader, [par exemple GRUB](https://github.com/ovh/bringyourownlinux/blob/main/example_build/files/make_image_bootable.sh) +- Un script `/root/.ovh/make_image_bootable.sh` exécutable, qui installera ou configurera le bootloader, [par exemple GRUB](https://github.com/ovh/bringyourownlinux/blob/main/example_build/files/make_image_bootable.sh). Ce script ne doit pas modifier l'ordre de boot NVRAM (par exemple, utilisez `grub-install --no-nvram`). Pour plus d'informations, consultez notre guide « [Comprendre le processus de démarrage des serveurs dédiés](/pages/bare_metal_cloud/dedicated_servers/boot-process) ». > [!warning] > diff --git a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.fr-fr.md b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.fr-fr.md index f1f047dc082..70b1d85200c 100644 --- a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.fr-fr.md +++ b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.fr-fr.md @@ -1,7 +1,7 @@ --- title: Bring Your Own Linux (BYOLinux) excerpt: Découvrez comment déployer facilement vos propres images Linux sur des serveurs dédiés -updated: 2025-09-30 +updated: 2026-02-06 --- ## Objectif @@ -21,7 +21,7 @@ En plus des prérequis et limitations mentionnés ci-dessous, vous devez vous as - Être connecté à l'[espace client OVHcloud](/links/manager) (pour la méthode de [déploiement via l'espace client](#viacontrolpanel) de ce guide) - Avoir accès à l'[API OVHcloud](/pages/manage_and_operate/api/first-steps) (pour la méthode de [déploiement via l'API](#viaapi) de ce guide) - Votre image doit être inférieure à la RAM du serveur moins 3 Gio -- Un script `/root/.ovh/make_image_bootable.sh` exécutable, qui installera ou configurera le bootloader, [par exemple GRUB](https://github.com/ovh/bringyourownlinux/blob/main/example_build/files/make_image_bootable.sh) +- Un script `/root/.ovh/make_image_bootable.sh` exécutable, qui installera ou configurera le bootloader, [par exemple GRUB](https://github.com/ovh/bringyourownlinux/blob/main/example_build/files/make_image_bootable.sh). Ce script ne doit pas modifier l'ordre de boot NVRAM (par exemple, utilisez `grub-install --no-nvram`). Pour plus d'informations, consultez notre guide « [Comprendre le processus de démarrage des serveurs dédiés](/pages/bare_metal_cloud/dedicated_servers/boot-process) ». > [!warning] > diff --git a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.it-it.md b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.it-it.md index 26d5553fc6c..7b1836d7d95 100644 --- a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.it-it.md +++ b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.it-it.md @@ -1,7 +1,7 @@ --- title: Bring Your Own Linux (BYOLinux) (EN) excerpt: Find out how to easily deploy your own Linux images on dedicated servers -updated: 2025-09-30 +updated: 2026-02-06 --- ## Objective @@ -21,7 +21,7 @@ In addition to the requirement and limitations mentioned below, you must ensure - Access to the [OVHcloud Control Panel](/links/manager) (for the "[Deployment via Control Panel](#viacontrolpanel)" method) - Access to the [OVHcloud API](/pages/manage_and_operate/api/first-steps) (for the "[Deployment via API](#viaapi)" section of this guide) - Your image must be smaller than the Server RAM minus 3GiB -- An executable script `/root/.ovh/make_image_bootable.sh`, which will reinstall and configure the bootloader, [for example GRUB](https://github.com/ovh/bringyourownlinux/blob/main/example_build/files/make_image_bootable.sh) +- An executable script `/root/.ovh/make_image_bootable.sh`, which will reinstall and configure the bootloader, [for example GRUB](https://github.com/ovh/bringyourownlinux/blob/main/example_build/files/make_image_bootable.sh). This script must not alter the NVRAM boot order (e.g. use `grub-install --no-nvram`). For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). > [!warning] > @@ -148,7 +148,7 @@ Once you completed the fields, start the deployment by clicking `Execute`{.actio ¹ Can either be a `#cloud-config` or a script. It must be in one-line, and have `\n` for line-return
² Use only if you need HTTP Headers, such as `Basic Auth`
-³ Examples of Efi bootloader path: +³ The EFI bootloader path is used by iPXE to boot your operating system. For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). Examples: | Operating System | efiBootloaderPath | |-|-| @@ -192,4 +192,6 @@ See OVHcloud API and Storage [Common customer errors](/pages/bare_metal_cloud/de [Bring Your Own Image (BYOI) / Bring Your Own Linux (BYOLinux), a comparison sheet](/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image-versus-bring-your-own-linux) +[Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process) + Join our user community on . diff --git a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.pl-pl.md b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.pl-pl.md index 26d5553fc6c..7b1836d7d95 100644 --- a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.pl-pl.md +++ b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.pl-pl.md @@ -1,7 +1,7 @@ --- title: Bring Your Own Linux (BYOLinux) (EN) excerpt: Find out how to easily deploy your own Linux images on dedicated servers -updated: 2025-09-30 +updated: 2026-02-06 --- ## Objective @@ -21,7 +21,7 @@ In addition to the requirement and limitations mentioned below, you must ensure - Access to the [OVHcloud Control Panel](/links/manager) (for the "[Deployment via Control Panel](#viacontrolpanel)" method) - Access to the [OVHcloud API](/pages/manage_and_operate/api/first-steps) (for the "[Deployment via API](#viaapi)" section of this guide) - Your image must be smaller than the Server RAM minus 3GiB -- An executable script `/root/.ovh/make_image_bootable.sh`, which will reinstall and configure the bootloader, [for example GRUB](https://github.com/ovh/bringyourownlinux/blob/main/example_build/files/make_image_bootable.sh) +- An executable script `/root/.ovh/make_image_bootable.sh`, which will reinstall and configure the bootloader, [for example GRUB](https://github.com/ovh/bringyourownlinux/blob/main/example_build/files/make_image_bootable.sh). This script must not alter the NVRAM boot order (e.g. use `grub-install --no-nvram`). For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). > [!warning] > @@ -148,7 +148,7 @@ Once you completed the fields, start the deployment by clicking `Execute`{.actio ¹ Can either be a `#cloud-config` or a script. It must be in one-line, and have `\n` for line-return
² Use only if you need HTTP Headers, such as `Basic Auth`
-³ Examples of Efi bootloader path: +³ The EFI bootloader path is used by iPXE to boot your operating system. For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). Examples: | Operating System | efiBootloaderPath | |-|-| @@ -192,4 +192,6 @@ See OVHcloud API and Storage [Common customer errors](/pages/bare_metal_cloud/de [Bring Your Own Image (BYOI) / Bring Your Own Linux (BYOLinux), a comparison sheet](/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image-versus-bring-your-own-linux) +[Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process) + Join our user community on . diff --git a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.pt-pt.md b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.pt-pt.md index 26d5553fc6c..7b1836d7d95 100644 --- a/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.pt-pt.md +++ b/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux/guide.pt-pt.md @@ -1,7 +1,7 @@ --- title: Bring Your Own Linux (BYOLinux) (EN) excerpt: Find out how to easily deploy your own Linux images on dedicated servers -updated: 2025-09-30 +updated: 2026-02-06 --- ## Objective @@ -21,7 +21,7 @@ In addition to the requirement and limitations mentioned below, you must ensure - Access to the [OVHcloud Control Panel](/links/manager) (for the "[Deployment via Control Panel](#viacontrolpanel)" method) - Access to the [OVHcloud API](/pages/manage_and_operate/api/first-steps) (for the "[Deployment via API](#viaapi)" section of this guide) - Your image must be smaller than the Server RAM minus 3GiB -- An executable script `/root/.ovh/make_image_bootable.sh`, which will reinstall and configure the bootloader, [for example GRUB](https://github.com/ovh/bringyourownlinux/blob/main/example_build/files/make_image_bootable.sh) +- An executable script `/root/.ovh/make_image_bootable.sh`, which will reinstall and configure the bootloader, [for example GRUB](https://github.com/ovh/bringyourownlinux/blob/main/example_build/files/make_image_bootable.sh). This script must not alter the NVRAM boot order (e.g. use `grub-install --no-nvram`). For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). > [!warning] > @@ -148,7 +148,7 @@ Once you completed the fields, start the deployment by clicking `Execute`{.actio ¹ Can either be a `#cloud-config` or a script. It must be in one-line, and have `\n` for line-return
² Use only if you need HTTP Headers, such as `Basic Auth`
-³ Examples of Efi bootloader path: +³ The EFI bootloader path is used by iPXE to boot your operating system. For more information, see [Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process). Examples: | Operating System | efiBootloaderPath | |-|-| @@ -192,4 +192,6 @@ See OVHcloud API and Storage [Common customer errors](/pages/bare_metal_cloud/de [Bring Your Own Image (BYOI) / Bring Your Own Linux (BYOLinux), a comparison sheet](/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image-versus-bring-your-own-linux) +[Understanding the dedicated server boot process](/pages/bare_metal_cloud/dedicated_servers/boot-process) + Join our user community on . diff --git a/pages/index.md b/pages/index.md index c89d6276cbe..6f5a9e2952a 100644 --- a/pages/index.md +++ b/pages/index.md @@ -142,10 +142,11 @@ + [How to increase Public Cloud quotas for a Startup Program member](account_and_service_management/startup-program/07-increase-quota) + Bare Metal Cloud + [Dedicated Servers](products/bare-metal-cloud-dedicated-servers) - + [Key Concepts](bare-metal-cloud-dedicated-servers-key-concepts) - + [Bare Metal 3-AZ Region - Service presentation](bare_metal_cloud/dedicated_servers/3az-presentation) + + [Key Concepts](bare-metal-cloud-dedicated-servers-key-concepts) + + [Bare Metal 3-AZ Region - Service presentation](bare_metal_cloud/dedicated_servers/3az-presentation) + [Kimsufi and So You Start customers - Get to know the OVHcloud Control Panel](bare_metal_cloud/dedicated_servers/getting-familiar-with-ovhcloud-control-panel) + [Dedicated Servers - Shared responsiblity](account_and_service_management/responsibility_sharing/dedicated-servers) + + [Understanding the dedicated server boot process](bare_metal_cloud/dedicated_servers/boot-process) + [Getting Started](bare-metal-cloud-dedicated-servers-getting-started) + [How to get started with a dedicated server](bare_metal_cloud/dedicated_servers/getting-started-with-dedicated-server) + [How to get started with a Kimsufi, So You Start or Rise dedicated server](bare_metal_cloud/dedicated_servers/getting-started-with-dedicated-server-eco)