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). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/727814 Title: [Maverick] Reboot of linux-virtual hangs on EC2 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
