I can confirm this bug also affects 2.1.4-dfsg-1 and I believe also 3.0.4-dfsg-1. I think this bug is the same as the one listed here http://www.virtualbox.org/ticket/2149 and applying the diffs it suggests (http://www.virtualbox.org/changeset/22152) fixed the problem for me with version 2.1.4-dfsg-1.