I can actually reproduce this in quantal. However (at least in my case) kvm is not actually hanging. The default boot prompt is sending output to 'console=ttyS0', and cloud-init waits a long time for an ec2 server to be available.
When I catch the grub prompt, type 'e' to edit the boot command, and delete the 'console=ttyS0', then output appears on my vnc session. Does that work for you in lucid as well?
Thanks for taking the time to report this bug.
I can actually reproduce this in quantal. However (at least in my case) kvm is not actually hanging. The default boot prompt is sending output to 'console=ttyS0', and cloud-init waits a long time for an ec2 server to be available.
When I catch the grub prompt, type 'e' to edit the boot command, and delete the 'console=ttyS0', then output appears on my vnc session. Does that work for you in lucid as well?