It turned out as an Layer8 problem. There a 2 kind of Images on https://cloud-images.ubuntu.com/jammy/current/ jammy-server-cloudimg-amd64-disk-kvm.img jammy-server-cloudimg-amd64.img without any context to it.
My thoughts on this where like ... im using kvm , than disk-kvm should be the right one. But this one has no Console. jammy-server-cloudimg-amd64.img is the one with functioning VNC. Closing() Kind regards Sven Barczyk -----Ursprüngliche Nachricht----- Von: Nux <n...@li.nux.ro> Gesendet: Dienstag, 31. Januar 2023 13:32 An: users@cloudstack.apache.org Cc: Sven Barczyk <s.barc...@bringe.com.invalid> Betreff: Re: VNC Console Problems with Ubuntu 22.04 I believe I know why. That image is really made more for Openstack/EC2, if you check the kernel parameters (cat /proc/cmdline) you will probably notice they redirect the output to the serial console. Something like "console=ttyS0,115200n8", if you remove that you should get all output to your regulat tty console. HTH On 2023-01-31 09:47, Sven Barczyk wrote: > Hi there, > > has anybody encountered this phenomenon, with the official Cloud-Images > from Ubuntu 22.04? > > After booting, the VNC Console from ConsoleProxy is frozen with bios > post information. > The instance from this Ubuntu 22.04 cloud-image, when configured with > proper network, is bootable and is accessible via SSH. > > K,R > Sven Barczyk
