running fsck -y resolved this for me. I'm not 100% sure if it was VirtualBox that caused the problem or the laptop not shutting down correctly at some point.

I suspect that linux booted the filesystem in read-only mode and gdm was trying to write to the filesystem on boot after the install of VirtualBox but thats a best guess.