So the 3.13.2 kernel does not seem to exhibit this bug? Is that only in virtual-box? Can you test to see if it also resolves the bug on bare-metal as well?
So the 3.13.2 kernel does not seem to exhibit this bug? Is that only in virtual-box? Can you test to see if it also resolves the bug on bare-metal as well?