On Thu, Aug 13, 2026 at 04:36:35PM +0200, Peter Krempa wrote:
due to alignment/allocation restrictions.
For block devices we support 'qcow2' formatted nvram block device for this reason so that the size can be embedded.
Yes, I'm aware of that, it's not a good fit for the way we manage this storage for a few reasons.
Can you elaborate?
Usually our nvram is from networked storage (and exactly sized). The templating stuff is not useful for us as a result. And, as a consequence, we don't want to have a completely separate path/workflow for the local storage case.
As said I see absolutely no reason to support _FILE. You'll have to come up with a good justification to persuade me.
That's fine, we don't need it either. I'll prepare a patch instead that allows slices only for raw block with offset=0. thanks john