adding Simon to CC, our primary c-machines developer.
Peter Boy [2022-04-13 14:53 +0200]:
> Am 13.04.2022 um 12:40 schrieb Martin Pitt
> Peter Boy [2022-04-13 12:32 +0200]:
>> Thanks for all the effort. The modified new machine creation process and the
>> option to delay startup and fine-tune the configuration comes in very handy.
> Note that this already existed before, by unchecking [x] Immediately start VM
> but now it's more obvious and symmetric indeed.
I just made a short test with f35 and tried to install a CentOS 9-stream cloud image.
Unfortunately, you still can’t delay the startup with a cloud image. The button is greyed
out and not active.
As I said, this was just a UI change, not a functional one. I faintly remember
that there was some reason why delayed startup doesn't work for cloud images.
This is possibly a limitation, as it can't control the install
process any more wrt. the temporary cloud-init iso? Simon?
Additionally I missed the option to use cloud-init to set an initial
password for root. So I have a nice cloud image running, but can’t log in. Is there now
another way to get access to a VM generated by cloud image?
I tested this on F35 with
Indeed the "create and edit" is disabled (see above):
But the "Automation" tab has the user/password stuff:
(Note, I had to re-do this with a bigger 8GB disk, as grub freaks out with just 2 GB; but
this is unrelated)
But indeed I can't log in as root nor martin. On the serial console I see the
boot messages (not on the VNC console, as it's quiet there). No cloud-init in
sight anywhere 🤔 (i.e. not even the basic stuff without user-data).
But "missed the option" sounds like you were perhaps not aware of the
"Automation" tab at all?
And I couldn’t normally shutdown that machine, but had to use forced
The host or the guest? (That both sounds unrelated, though?)