On Thu, Jul 25, 2024 at 12:14:11PM +0200, Vojtěch Dušátko wrote:
I recenly started using Debian cloud image at my PVE cluster. I wanted to
share some issues I faced.
1. I downloaded genericcloud image, imported to template, create VM and
got stuck for many hours .... It's not working. It boots up but it got
stuck at not working cloud init. Don't know why.
The genericcloud image differs from the generic image only in that it
installs the cloud kernel, rather than the standard Debian kernel. The
cloud kernel leaves out most device drivers, and primarily targets the
Amazon EC2 and Microsoft Azure VM device models. Functionality outside
of those environments is not guaranteed.
We need to better document this...
2. I realised that genericcloud is not for me - I started using generic.
It boots up, it runs cloud init correctly, but .... That image doesn't
include qemu-guest-agent (unlike the instalation I did by myself from
cloud netinstall ISO) so when I want to find that VM at network I have
to do some ARP stuff, etc. Not just look at dashboard to see which IP
it has. Also there's a problem that when you run the VM at QEMU, it
should have QEMU-GA to communicate with virtualisation platform
correctly.
qemu-guest-agent assumes a level of integration between the VM and the
underlying infrastructure that is not appropriate for a general purpose
image. Our published images need to be suitable for use in environments
where there's a trust boundary between the VM and the underlying host.