Problems with bridged or host-attach networking
Posted: 12. Jun 2009, 23:42
A lot of people are having issues with this - I think there is a problem in the install somwhere.
Host is WinXP.
Guest is ubuntu 8.10.
Process is upgrade 2.1.x to 2.2.4
Running from an admin account.
1. Complete install repeatedly hung just before completing.
2. Install succeeded when host-adapter was marked as install-on-demand
After this, neither bridged nor host-attach can be used as no host adapter/bridged adapter is ever offered, nor is there any
way to create them as you could in earlier releases.
Even after manually bridging at the windows network control panel nothing can be achieved.
Repair does nothing as it is impossible to change the install config options to attempt to force the network adapter to install.
At this point I successfully performed a complete (clean) install on my backup pc. So, I rebooted the primary, removed virtualbox,
rebooted again (I am paranoid) and performed a clean install with no other process running. This time it succeeded.
I really hate windows.
Now host-attach and bridged modes both offer the expected adapter and all is (almost) hunky-dory. I still get a warning every time I
start VB that my VDI is inaccessible, although it always starts ok. I put this down to a non-standard vdi location - apparently the
early check just assumes a default and doesn't look in the xml, which is sloppy.
Meaningless warnings aside, there are two bugs here:
1. Hang on complete install. I don't know if this was associated with something running in the background or the fact I was upgrading.
2. Install on demand doesn't.
Also, possibly,
3. Repair does not give the option to change config (ie change install-on-demand to install-unconditionally).
So, anyone else having issues I suggest uninstall and reinstall on a newly rebooted system with nothing else running.
It worked for me.
Host is WinXP.
Guest is ubuntu 8.10.
Process is upgrade 2.1.x to 2.2.4
Running from an admin account.
1. Complete install repeatedly hung just before completing.
2. Install succeeded when host-adapter was marked as install-on-demand
After this, neither bridged nor host-attach can be used as no host adapter/bridged adapter is ever offered, nor is there any
way to create them as you could in earlier releases.
Even after manually bridging at the windows network control panel nothing can be achieved.
Repair does nothing as it is impossible to change the install config options to attempt to force the network adapter to install.
At this point I successfully performed a complete (clean) install on my backup pc. So, I rebooted the primary, removed virtualbox,
rebooted again (I am paranoid) and performed a clean install with no other process running. This time it succeeded.
I really hate windows.
Now host-attach and bridged modes both offer the expected adapter and all is (almost) hunky-dory. I still get a warning every time I
start VB that my VDI is inaccessible, although it always starts ok. I put this down to a non-standard vdi location - apparently the
early check just assumes a default and doesn't look in the xml, which is sloppy.
Meaningless warnings aside, there are two bugs here:
1. Hang on complete install. I don't know if this was associated with something running in the background or the fact I was upgrading.
2. Install on demand doesn't.
Also, possibly,
3. Repair does not give the option to change config (ie change install-on-demand to install-unconditionally).
So, anyone else having issues I suggest uninstall and reinstall on a newly rebooted system with nothing else running.
It worked for me.