[pve-devel] [PATCH docs 1/3] cloud init: use 'order' variant for 'boot' property

[pve-devel] [PATCH docs 1/3] cloud init: use 'order' variant for 'boot' property

[Fiona Ebner]

instead of the legacy 'boot: c'+bootdisk combination.

Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
---
 qm-cloud-init.adoc | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/qm-cloud-init.adoc b/qm-cloud-init.adoc
index 8363f10..25cd700 100644
--- a/qm-cloud-init.adoc
+++ b/qm-cloud-init.adoc
@@ -86,13 +86,12 @@ the Cloud-Init data to the VM.
 qm set 9000 --ide2 local-lvm:cloudinit
 ----
 
-To be able to boot directly from the Cloud-Init image, set the
-`bootdisk` parameter to `scsi0`, and restrict BIOS to boot from disk
-only. This will speed up booting, because VM BIOS skips the testing for
-a bootable CD-ROM.
+To be able to boot directly from the Cloud-Init image, set the `boot` parameter
+to `order=scsi0` to restrict BIOS to boot from this disk only. This will speed
+up booting, because VM BIOS skips the testing for a bootable CD-ROM.
 
 ----
-qm set 9000 --boot c --bootdisk scsi0
+qm set 9000 --boot order=scsi0
 ----
 
 For many Cloud-Init images, it is required to configure a serial console and use
-- 
2.30.2

[pve-devel] [PATCH docs 2/3] cloud init: use expected disk number in example

[Fiona Ebner]

Starting from a storage with no disks for the VM ID in question, the
imported disk will be called vm-9000-disk-0.

Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
---
 qm-cloud-init.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/qm-cloud-init.adoc b/qm-cloud-init.adoc
index 25cd700..618d0f7 100644
--- a/qm-cloud-init.adoc
+++ b/qm-cloud-init.adoc
@@ -69,7 +69,7 @@ qm create 9000 --memory 2048 --net0 virtio,bridge=vmbr0
 qm importdisk 9000 bionic-server-cloudimg-amd64.img local-lvm
 
 # finally attach the new disk to the VM as scsi drive
-qm set 9000 --scsihw virtio-scsi-pci --scsi0 local-lvm:vm-9000-disk-1
+qm set 9000 --scsihw virtio-scsi-pci --scsi0 local-lvm:vm-9000-disk-0
 ----
 
 NOTE: Ubuntu Cloud-Init images require the `virtio-scsi-pci`
-- 
2.30.2

[pve-devel] [PATCH/RFC docs 3/3] cloud init: use 'import-from' disk syntax to avoid a step

[Fiona Ebner]

Put the 'scsihw' part into the previous command, so that the rather
complicated import command can stand on its own.

Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
---

Not entirely sure about this one, because it does make the commands a
bit more involved.

 qm-cloud-init.adoc | 11 ++++-------
 1 file changed, 4 insertions(+), 7 deletions(-)

diff --git a/qm-cloud-init.adoc b/qm-cloud-init.adoc
index 618d0f7..b275d7a 100644
--- a/qm-cloud-init.adoc
+++ b/qm-cloud-init.adoc
@@ -62,14 +62,11 @@ image provided by Ubuntu at https://cloud-images.ubuntu.com.
 # download the image
 wget https://cloud-images.ubuntu.com/bionic/current/bionic-server-cloudimg-amd64.img
 
-# create a new VM
-qm create 9000 --memory 2048 --net0 virtio,bridge=vmbr0
+# create a new VM with VirtIO SCSI controller
+qm create 9000 --memory 2048 --net0 virtio,bridge=vmbr0 --scsihw virtio-scsi-pci
 
-# import the downloaded disk to local-lvm storage
-qm importdisk 9000 bionic-server-cloudimg-amd64.img local-lvm
-
-# finally attach the new disk to the VM as scsi drive
-qm set 9000 --scsihw virtio-scsi-pci --scsi0 local-lvm:vm-9000-disk-0
+# import the downloaded disk to the local-lvm storage, attaching it as a SCSI drive
+qm set 9000 --scsi0 local-lvm:0,import-from=/path/to/bionic-server-cloudimg-amd64.img
 ----
 
 NOTE: Ubuntu Cloud-Init images require the `virtio-scsi-pci`
-- 
2.30.2

[pve-devel] applied-series: [PATCH docs 1/3] cloud init: use 'order' variant for 'boot' property

[Thomas Lamprecht]

Am 29/09/2022 um 09:52 schrieb Fiona Ebner:
> instead of the legacy 'boot: c'+bootdisk combination.
> 
> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
> ---
>  qm-cloud-init.adoc | 9 ++++-----
>  1 file changed, 4 insertions(+), 5 deletions(-)
> 
>

applied series, thanks!