Starting your server on an OVH kernel
This guide explains how to network boot your server on to an OVH kernel.
This guide explains how to network boot your server on to an OVH kernel.
Last updated 25th July 2018
The Netboot feature is a service offered for free by OVH, it allows you to start your OVH dedicated server on a precompiled kernel provided by OVH. Once configured this way, your server automatically loads the kernel from the network, so you do not have to configure anything else. This method also allows you to update your kernel very simply because OVH compiles the latest version of the kernel as soon as it is available and makes it available on Netboot.
This guide will perform a network boot of your server using an OVH kernel.
The Netboot facility needs to be configured in the OVH Control Panel
To start your server on Disk, you must first connect to the Control Panel
Go to the Bare Metal Cloud
section, Dedicated Servers
on the left-hand column, then select your server in the list.
In the tab Server Status
, section General Information
, click Edit
on the Boot line.
Then select Boot from the hard disk
, click Next
, and then finally Confirm
You will now need to reboot the server so that the new netboot takes effect.
This part is intended for servers running Linux. For Windows, FreeBSD, and Virtualization distributions, only Hard Disk mode selection or Rescue modes are possible.
To start your server on a network kernel, you must first connect to your Control Panel
Go to the Bare Metal Cloud
section, Dedicated Servers
on the left-hand column, then select your server in the list.
In the tab Server Status
, section General Information
, click Edit
on the Boot line.
Select Boot in network mode
.
You will then have to choose the desired kernel from the list below.
Then enter the Root Device (partition where the root partition of your server is located).
To determine the Root Device of your server, see the /etc/fstab file on your server.
In SSH:
cat /etc/fstab
/dev/sda1 / ext3 errors=remount-ro 0 1
/dev/sda2 /home ext3 defaults,grpquota,usrquota 1 2
/dev/sda3 swap swap defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
In our example, the Root Device will be /dev/sda1.
Click Next
, and then finally Confirm
You will now need to reboot the server so that the new netboot takes effect.
To start your server in rescue mode, you must first connect to your Control Panel
Go to the Bare Metal Cloud
section, Dedicated Servers
on the left-hand column, then select your server in the list.
In the tab Server Status
, section General Information
, click Edit
on the Boot line.
Select Boot in rescue mode
, then the desired rescue mode for the server. (By default, rescue64-pro)
You can enter your email address in to the "Get your updated username" field to receive the rescue mode password at this address.
Click Next
, and then finally Confirm
You will now need to reboot the server so that the new netboot takes effect.
Join our community of users on https://community.ovh.com/en/.
Please feel free to give any suggestions in order to improve this documentation.
Whether your feedback is about images, content, or structure, please share it, so that we can improve it together.
Your support requests will not be processed via this form. To do this, please use the "Create a ticket" form.
Thank you. Your feedback has been received.
Access your community space. Ask questions, search for information, post content, and interact with other OVHcloud Community members.
Discuss with the OVHcloud community