just to add to my previous comment; this error does not occur when booting up jaunty beta within virtualbox 2.1.4
just to add to my previous comment; this error does not occur when booting up jaunty beta within virtualbox 2.1.4