This is still a concern, and not easily reproducible. I would rather keep it open, unless you have reason to consider the OOPS resolved on current 2.6.32-21. I am stress-testing (by extension) kvm, and hopefully either I can state it has not happened on the last (few) thousands tries, and recornfirm it.
This is still a concern, and not easily reproducible. I would rather keep it open, unless you have reason to consider the OOPS resolved on current 2.6.32-21. I am stress-testing (by extension) kvm, and hopefully either I can state it has not happened on the last (few) thousands tries, and recornfirm it.