Stefan, your workaround would almost be acceptable if this were the only bug in play. However, for those of us booting Maverick AMIs for PV-grub, and then using cloud-init to auto-downgrade the kernel to Karmic's or auto-upgrade to Natty's (because let's face it, so far Lucid and Maverick have yet to have a production-capable kernel for EC2 use), lack of a reboot method that works from a shellscript inside the instance itself without sensitive keys is a no-go for even initially booting from Maverick AMIs with this bug in them. Luckily the older Maverick AMIs from before this bug was introduced are still available...
Stefan, your workaround would almost be acceptable if this were the only bug in play. However, for those of us booting Maverick AMIs for PV-grub, and then using cloud-init to auto-downgrade the kernel to Karmic's or auto-upgrade to Natty's (because let's face it, so far Lucid and Maverick have yet to have a production-capable kernel for EC2 use), lack of a reboot method that works from a shellscript inside the instance itself without sensitive keys is a no-go for even initially booting from Maverick AMIs with this bug in them. Luckily the older Maverick AMIs from before this bug was introduced are still available...