public inbox for kdevops@lists.linux.dev
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: Chuck Lever <cel@kernel.org>, Daniel Gomez <da.gomez@kruces.com>,
	kdevops@lists.linux.dev
Cc: Luis Chamberlain <mcgrof@kernel.org>
Subject: [RFT 0/4] guestfs: few custom image fixes
Date: Tue, 26 Aug 2025 20:57:43 -0700	[thread overview]
Message-ID: <20250827035747.3314144-1-mcgrof@kernel.org> (raw)

Here's a few custom images fixes I found along the way after deciding
to nuke my old base image and starting fresh again for debian testing.

Would appreciate feedback on testing, review. This is under the kdevops
branch: mcgrof/20250826

Luis Chamberlain (4):
  guestfs: fix custom image partition not expanded after disk resize
  guestfs: fix custom image bringup failure for Debian 13
  guestfs: fix virt-resize failure for custom images
  guestfs: fix checksum verification for resized custom images

 .../roles/base_image/tasks/custom-image.yml   | 112 ++++++++++++------
 playbooks/roles/base_image/tasks/main.yml     |   1 +
 2 files changed, 78 insertions(+), 35 deletions(-)

-- 
2.50.1


             reply	other threads:[~2025-08-27  3:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-27  3:57 Luis Chamberlain [this message]
2025-08-27  3:57 ` [RFT 1/4] guestfs: fix custom image partition not expanded after disk resize Luis Chamberlain
2025-08-27  3:57 ` [RFT 2/4] guestfs: fix custom image bringup failure for Debian 13 Luis Chamberlain
2025-08-27  3:57 ` [RFT 3/4] guestfs: fix virt-resize failure for custom images Luis Chamberlain
2025-08-27  3:57 ` [RFT 4/4] guestfs: fix checksum verification for resized " Luis Chamberlain
2025-08-29  2:01 ` [RFT 0/4] guestfs: few custom image fixes 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=20250827035747.3314144-1-mcgrof@kernel.org \
    --to=mcgrof@kernel.org \
    --cc=cel@kernel.org \
    --cc=da.gomez@kruces.com \
    --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