From: Stefan Reiter <s.reiter@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH v2 0/7] Improve boot device/order configuration
Date: Tue, 6 Oct 2020 15:32:11 +0200 [thread overview]
Message-ID: <20201006133218.25403-1-s.reiter@proxmox.com> (raw)
The goal of the series is to modernize boot order selection by allowing the user
to specify arbitrary VM disks and devices in any order. Fixes #3010 and #3011.
First patch is a standalone cleanup. Tests are seperated into extra patches.
v2:
* split qemu-server changes into seperate patches (hence changelog only here)
* use order= property in boot: instead of standalone bootorder:
** update API and GUI to match
* fix get_default_bootdevices and bootorder_from_legacy to *actually* match the
old behaviour, as is now verified with the test
=> see GUI patch for changes there
qemu-server: Stefan Reiter (6):
fix indentation
cfg2cmd: add test for legacy-style bootorder
add new 'boot' property format and introduce legacy conversion helpers
fix #3010: add 'bootorder' parameter for better control of boot
devices
api: add handling for new boot order format
cfg2cmd: add tests for new boot order property
PVE/API2/Qemu.pm | 37 ++++-
PVE/CLI/qm.pm | 4 +-
PVE/QemuServer.pm | 207 ++++++++++++++++++++-----
PVE/QemuServer/Drive.pm | 32 +++-
PVE/QemuServer/PCI.pm | 3 +-
PVE/QemuServer/USB.pm | 14 +-
test/cfg2cmd/bootorder-empty.conf | 16 ++
test/cfg2cmd/bootorder-empty.conf.cmd | 38 +++++
test/cfg2cmd/bootorder-legacy.conf | 17 ++
test/cfg2cmd/bootorder-legacy.conf.cmd | 38 +++++
test/cfg2cmd/bootorder.conf | 16 ++
test/cfg2cmd/bootorder.conf.cmd | 38 +++++
12 files changed, 398 insertions(+), 62 deletions(-)
create mode 100644 test/cfg2cmd/bootorder-empty.conf
create mode 100644 test/cfg2cmd/bootorder-empty.conf.cmd
create mode 100644 test/cfg2cmd/bootorder-legacy.conf
create mode 100644 test/cfg2cmd/bootorder-legacy.conf.cmd
create mode 100644 test/cfg2cmd/bootorder.conf
create mode 100644 test/cfg2cmd/bootorder.conf.cmd
manager: Stefan Reiter (1):
ui: improve boot order editor with 'bootorder' support
www/css/ext6-pve.css | 4 +
www/manager6/qemu/BootOrderEdit.js | 355 ++++++++++++++++++-----------
www/manager6/qemu/Options.js | 32 ++-
3 files changed, 257 insertions(+), 134 deletions(-)
--
2.20.1
next reply other threads:[~2020-10-06 13:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 13:32 Stefan Reiter [this message]
2020-10-06 13:32 ` [pve-devel] [PATCH v2 qemu-server 1/7] fix indentation Stefan Reiter
2020-10-06 13:32 ` [pve-devel] [PATCH v2 qemu-server 2/7] cfg2cmd: add test for legacy-style bootorder Stefan Reiter
2020-10-06 13:32 ` [pve-devel] [PATCH v2 qemu-server 3/7] add new 'boot' property format and introduce legacy conversion helpers Stefan Reiter
2020-10-06 13:32 ` [pve-devel] [PATCH v2 qemu-server 4/7] fix #3010: add 'bootorder' parameter for better control of boot devices Stefan Reiter
2020-10-16 14:53 ` Thomas Lamprecht
2020-10-06 13:32 ` [pve-devel] [PATCH v2 qemu-server 5/7] api: add handling for new boot order format Stefan Reiter
2020-10-06 13:32 ` [pve-devel] [PATCH v2 qemu-server 6/7] cfg2cmd: add tests for new boot order property Stefan Reiter
2020-10-06 13:32 ` [pve-devel] [PATCH v2 manager 7/7] ui: improve boot order editor Stefan Reiter
2020-10-16 12:50 ` [pve-devel] applied-series: [PATCH v2 0/7] Improve boot device/order configuration Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201006133218.25403-1-s.reiter@proxmox.com \
--to=s.reiter@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox