On Tue, 16 Apr 2024, Timo Lindfors wrote:
I would very much like to have some sort of workaround to start moving some
I noticed that if I use
cmd = [
"virt-install",
"--connect", "qemu+ssh://ansi...@hypervisor.example.com/system",
"--name", "linditest",
"--cloud-init",
Hi,
I would very much like to have some sort of workaround to start moving
some systems from proprietary clouds to libvirt. I don't quite understand
how cloud-init works, does the workaround suggested in the first message
basically require me to rebuild the image? If that is the case then mayb
Package: cloud-initramfs-growroot
Followup-For: Bug #1037914
X-Debbugs-Cc: witold.bary...@gmail.com
This still is broken in stable, including with backports and in sid.
I tried to use latest cloud image,
debian-12-backports-genericcloud-amd64-20240201-1644.qcow2
and
debian-sid-genericcloud-amd
Control: tags -1 patch
Hi,
I've managed to reproduce the original report after adding 'debug' to the
kernel command line and checking "/run/initramfs/initramfs.debug"[1].
A patch was sent to the "cloud-team/cloud-initramfs-tools" Salsa repository[2].
Regards,
Tiago.
[1]: https://wiki.debian.or
4 matches
Mail list logo
