Apologies if I'm responding to this bug in an inappropriate way....
I, too, was bit by this bug last week, and seeing that a bug had been filed, waited to see if a fix was soon forthcoming.
Any idea when the fix for this might hit Sid? Or be otherwise available to me? Or perhaps there's a work-around I could implement in the meanwhile, so that I can get VirtualBox working again?