From: Luis Chamberlain <mcgrof@kernel.org>
To: kdevops@lists.linux.dev
Cc: Luis Chamberlain <mcgrof@kernel.org>
Subject: [PATCH 0/5] guestfs: start moving guest data to macros
Date: Wed, 6 Mar 2024 16:14:21 -0800 [thread overview]
Message-ID: <20240307001426.565390-1-mcgrof@kernel.org> (raw)
This implements initial macro support usage for using guestfs for
dynamic libvirt XML data for the guests, it starts with moving the
existing extra drive support to its own file as macros, and later
builds on this to demonstrate more complex functionality like support
for large IO experimentation.
Luis Chamberlain (5):
bringup_guestfs.sh: use bash as the default shell
guestfs_q35: use hex for pci addr
guestfs_q35: use libvirt_extra_storage_nvme_logical_block_size
gen_nodes: move drive generation for guestfs to macros
guestfs: add large IO support
playbooks/roles/gen_nodes/defaults/main.yml | 2 +
playbooks/roles/gen_nodes/templates/drives.j2 | 148 ++++++++++++++++++
.../gen_nodes/templates/guestfs_q35.j2.xml | 83 ++++++----
scripts/bringup_guestfs.sh | 42 +++--
4 files changed, 233 insertions(+), 42 deletions(-)
create mode 100644 playbooks/roles/gen_nodes/templates/drives.j2
--
2.43.0
next reply other threads:[~2024-03-07 0:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 0:14 Luis Chamberlain [this message]
2024-03-07 0:14 ` [PATCH 1/5] bringup_guestfs.sh: use bash as the default shell Luis Chamberlain
2024-03-07 0:14 ` [PATCH 2/5] guestfs_q35: use hex for pci addr Luis Chamberlain
2024-03-07 0:14 ` [PATCH 3/5] guestfs_q35: use libvirt_extra_storage_nvme_logical_block_size Luis Chamberlain
2024-03-07 0:14 ` [PATCH 4/5] gen_nodes: move drive generation for guestfs to macros Luis Chamberlain
2024-03-07 0:14 ` [PATCH 5/5] guestfs: add large IO support Luis Chamberlain
2024-03-07 18:43 ` [PATCH 0/5] guestfs: start moving guest data to macros Luis Chamberlain
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=20240307001426.565390-1-mcgrof@kernel.org \
--to=mcgrof@kernel.org \
--cc=kdevops@lists.linux.dev \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).