From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 39A6D633DE for ; Tue, 24 Nov 2020 17:52:18 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 37D6A115AF for ; Tue, 24 Nov 2020 17:52:18 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [212.186.127.180]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id F3622115A1 for ; Tue, 24 Nov 2020 17:52:16 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id BCBE143FB1 for ; Tue, 24 Nov 2020 17:52:16 +0100 (CET) From: Stefan Reiter To: pve-devel@lists.proxmox.com Date: Tue, 24 Nov 2020 17:52:04 +0100 Message-Id: <20201124165205.31952-2-s.reiter@proxmox.com> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20201124165205.31952-1-s.reiter@proxmox.com> References: <20201124165205.31952-1-s.reiter@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.034 Adjusted score from AWL reputation of From: address KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] [PATCH docs 2/3] qm: add section about VM boot order X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Nov 2020 16:52:18 -0000 ...and fix outdated example config Signed-off-by: Stefan Reiter --- qm.adoc | 35 ++++++++++++++++++++++++++++++++++- 1 file changed, 34 insertions(+), 1 deletion(-) diff --git a/qm.adoc b/qm.adoc index d30672e..809154a 100644 --- a/qm.adoc +++ b/qm.adoc @@ -840,6 +840,39 @@ recommended to always use a limiter to avoid guests using too many host resources. If desired, a value of '0' for `max_bytes` can be used to disable all limits. +[[qm_bootorder]] +Guest Boot Order +~~~~~~~~~~~~~~~~ + +QEMU can tell the guest which devices it should boot from, and in which order. +This can be specified in the config via the `boot` property, e.g.: + +---- +boot: order=scsi0;net0;hostpci0 +---- + +[thumbnail="screenshot/gui-qemu-edit-bootorder.png"] + +This way, the guest would first attempt to boot from the disk `scsi0`, if that +fails, it would go on to attempt network boot from `net0`, and in case that +fails too, finally attempt to boot from a passed through PCIe device (seen as +disk in case of NVMe, otherwise tries to launch into an option ROM). + +On the GUI you can use a drag-and-drop editor to specify the boot order, and use +the checkbox to enable or disable certain devices for booting altogether. + +NOTE: If your guest uses multiple disks to boot the OS or load the bootloader, +all of them must be marked as 'bootable' (that is, they must have the checkbox +enabled or appear in the list in the config) for the guest to be able to boot. +This is because recent SeaBIOS and OVMF versions only initialize disks if they +are marked 'bootable'. + +In any case, even devices not appearing in the list or having the checkmark +disabled will still be available to the guest, once it's operating system has +booted and initialized them. The 'bootable' flag only affects the guest BIOS and +bootloader. + + [[qm_startup_and_shutdown]] Automatic Start and Shutdown of Virtual Machines ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -1308,12 +1341,12 @@ unique cluster wide. .Example VM Configuration ---- +boot: order=virtio0;net0 cores: 1 sockets: 1 memory: 512 name: webmail ostype: l26 -bootdisk: virtio0 net0: e1000=EE:D2:28:5F:B6:3E,bridge=vmbr0 virtio0: local:vm-100-disk-1,size=32G ---- -- 2.20.1