Opened 14 years ago
Closed 9 years ago
#7505 closed defect (obsolete)
ifdown eth1 required before reboot or shutdown or else subsequent boot hangs at eth1 configuration
| Reported by: | Gilbert Standen | Owned by: | |
|---|---|---|---|
| Component: | network | Version: | VirtualBox 3.2.8 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Linux |
Description (last modified by )
VirtualBox version 3.2.8 r64453 running on Ubuntu 9.10 32-bit host, problem occurs when running a CentOS 4.1 (Final) virtual guest.
If you run only one virtual network adapter, specifically a NAT'd adapter, dhcp, startup is fine. But if you try to add a second adapter, specifically, a Host-Only adapater, dhcp (or static), boot will usually hang when the OS tries to configure eth1 (the Host-Only adapter).
I found that the only workaround was to remember to do an "ifdown eth1" (the host-only adapter) before each reboot or shutdown of the CentOS vm. If you do a manual"ifdown eth1" then the reboot is consistently successful, and both eth0 (NAT) and eth1 (Host-Only) are successfully configured at boot and bootup is successful every time (I have tested over 10x boots so far completely successful as long as "ifdown eth1" is executed before shutdown). Thanks
Change History (2)
comment:1 by , 13 years ago
comment:2 by , 9 years ago
| Description: | modified (diff) |
|---|---|
| Resolution: | → obsolete |
| Status: | new → closed |
It looks like the guest OS tries to obtain IP address for eth1 via DHCP. It should still come up when timeout in dhcp client expires. You can configure internal DHCP server for the host-only adapter in File->Preferences->Network. Select the interface and click the 'edit' (screwdriver) button, then select 'DHCP Server' tab.