VirtualBox seems to have forgotten (Or I did...)

Unable to get VirtualBox-hosted machines onto the net yesterday. Seems the NAT network inside VB just gave up trying to route information out. Kinda killed my plans for trying to build the kernel inside a snapshot of 542 (instead of spending days getting Fedora installed). I don't recall having to do anything other than reboot to get the network to work before.

Should probably just go back to VMWare for now. I much prefer the Open Source approach, but if it can't reach the network it's unusable for our purposes. Or maybe just find a VirtualBox person who wants to work on supporting it and "owning" the emulation environment for the project.


Comments are closed.


Pingbacks are closed.