The (annoying, but working) workaround is the following:
I imported my Vagrant-managed Ubuntu 10.04.4 LTS VM into a trial copy of Parallels Desktop 8. I then logged into the VM manually using the Parallels VM window using the default Vagrant user / password (vagrant/vagrant) and changed the password for my custom Vagrantfile dev login. Then in Parallels I switched the networking on the VM to Bridge Mode (so I can access it via IP address on my local network).
Remarkably everything in the VM worked and I'm back to coding. Would like to see a quick fix for VirtualBox so I can get back to my Vagrant awesomeness.
I imported my Vagrant-managed Ubuntu 10.04.4 LTS VM into a trial copy of Parallels Desktop 8. I then logged into the VM manually using the Parallels VM window using the default Vagrant user / password (vagrant/vagrant) and changed the password for my custom Vagrantfile dev login. Then in Parallels I switched the networking on the VM to Bridge Mode (so I can access it via IP address on my local network).
Remarkably everything in the VM worked and I'm back to coding. Would like to see a quick fix for VirtualBox so I can get back to my Vagrant awesomeness.