I think I remember seeing a similar bug that we fixed but I cannot find it. Does this also happen on "real" hardware or is it just in virtual box?