First, we haven't confirmed this is an issue with 10.8.2 or something else; though it does sound like it is. Second, this is a forum for Mac OSX users of VirtualBox. It seems quite appropriate to bring the question up in this forum, though also bringing the question up in Apple forums is also a good idea now that it is highly likely 10.8.2. It does not seem to affect VMWare Fusion, so it could be specific to VirtualBox. We have several laptops we were able to test with.
Do you have any constructive feedback on how we might go about diagnosing the issue?
Can anyone else also confirm it's 10.8.2? Thanks! Perhaps we can submit an early bug report then so when 10.8.2 is released the end of this month it has possibly already been looked at, and a fix could be in the works?