Comment 3 for bug 727814

Anyone have a userland workaround (other than ec2-reboot-instances of own instance-id, which requires auth keys on the node...) for getting an ec2 node on these kernels to reboot itself successfully?

Also: note that once we have a release kernel w/ the fix, new Maverick AMIs will have to go out before the problem is really solved (or else you can't really reboot to the fixed kernel from a fresh image after update).