Comment 76 for bug 634487

Matt, I suspect you are correct that this is the same issue hit another way.
I also suspect that if we had a tiny C test case that illustrated the issue (which I've never gone after) we'd have a much better likelyhood of finding a guest or host level work around. However, I think most parties involved have just accepted that the hypervisor level fix is what is necessary, and that due to it only (largely) affecting java on t1.micro (which is not a terribly useful scenario for cpu anda memory issues).

There is no public amazon issue that I am aware of.