mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Sascha Hauer" <s.hauer@pengutronix.de>
To: "Tobias Waldekranz" <tobias@waldekranz.com>
Cc: barebox@lists.infradead.org
Subject: Re: [RFC next 0/2] dm: lvm: Initial Logical Volume Management support
Date: Mon, 31 Aug 2026 09:11:31 +0000	[thread overview]
Message-ID: <84c85354-aaab-4800-b193-49f28e4c363c@pengutronix.de> (raw)
In-Reply-To: <87ld9mofce.fsf@waldekranz.com>

On 2026-08-31 10:37, Tobias Waldekranz wrote:
> 
> Hi Sascha,
> 
> Thanks for taking the time to look at this!
> 
> On fre, aug 28, 2026 at 14:10, "Sascha Hauer" <s.hauer@pengutronix.de> wrote:
> > Hi Tobias,
> >
> > On 2026-08-24 18:31, Tobias Waldekranz wrote:
> >> [...]
> >> If the overall structure is OK with the community and maintainers,
> >> then the biggest remaining issue is testing. I have been surprised to
> >> learn that the standard LVM tools will not operate on disk images
> >> (without loopback mounting). Nor does there seem to be any other tools
> >> out there that allows you to provision PVs/VGs/LVs without having them
> >> "live" and attached to the host system. If there are any suggestions
> >> here they would be very welcome!
> >
> > Would guestfish be an option? That allows you to call pvcreate/vgcreate
> > on disk images.
> 
> Thank you, I had completely forgotten about that! I definitely think
> that it would solve the problem.
> 
> You would be okay with bringing that dependency into the barebox-ci
> container then? Do we foresee any issues with access to /dev/kvm or
> things like that from inside there? I guess it would still work in TCG
> mode, but might be slow?

It should work generally, but yes, it will be slow. I guess as long as
we only use it to create physical volumes and volume groups it should be
fine, but we should refrain from making excess data accesses like
writing verifying big images through the software emulation.

Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |




      reply	other threads:[~2026-08-31  9:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-24 18:31 Tobias Waldekranz
2026-08-24 18:31 ` [RFC next 1/2] " Tobias Waldekranz
2026-08-28 14:19   ` Sascha Hauer
2026-08-31  8:39     ` Tobias Waldekranz
2026-08-24 18:31 ` [RFC next 2/2] commands: lvm: inspect VGs, activate LVs Tobias Waldekranz
2026-08-28 14:20   ` Sascha Hauer
2026-08-31  8:40     ` Tobias Waldekranz
2026-08-28 14:10 ` [RFC next 0/2] dm: lvm: Initial Logical Volume Management support Sascha Hauer
2026-08-31  8:37   ` Tobias Waldekranz
2026-08-31  9:11     ` Sascha Hauer [this message]

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=84c85354-aaab-4800-b193-49f28e4c363c@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=tobias@waldekranz.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