VBoxNetDHCP.exe stop working

[Henry Stolen]

Hi,

My host is windows 7 32-bits, I installed ubuntu server 12.04.3 as a guest OS, I'm using as a network interface the VirtualBox Host-Only Ethernet Adapter and the first time I ran the guest everything was working alright, I reboot the host and when I tried to load the guest system I got the Message VBoxNetDHCP.exe stop working, the boot screen stops at the message "stopping user space bootsplash" wainting for network configuration, after a while, a second message is displayed "waiting up to 60 more seconds for network configuration" and as soon as the system finish booting, I looked for the interface but it is never started for IPv4 configuration.

Any suggestions?

Tks.

[Perryg]

Post the results of the following from the host command window

Code: Select all

VBoxManage list hostonlyifs

and

Code: Select all

VBoxManage list dhcpservers

[Henry Stolen]

These are the results:

VBoxManage list hostonlyifs
Name: VirtualBox Host-Only Ethernet Adapter
GUID: 02ddd2df-febb-4d61-ba4e-380557ee5635
DHCP: Disabled
IPAddress: 192.168.56.1
NetworkMask: 255.255.255.0
IPV6Address: fe80:0000:0000:00001e6a:fcd9:d720
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 08:00:27:00:c0:72
MediumType: Ethernet
Status: Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter

VBoxManage list dhcpservers
NetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter
IP: 192.168.56.100
NetworkMask: 255.255.255.0
lowerIPAddress: 192.168.56.101
upperIPAddress: 192.168.56.254
Enabled: Yes

[Perryg]

Looks like the server side is doing its thing. Post the results of the following:

From the hosts terminal/command window type VBoxManage showvminfo <VM Name> --details and post here. Replace <VM Name> with the actual name of the VM. Use " " if the name has a space in it.

Note if the host is Windows you need to be in the directory that has VBoxManage.exe for the command to work.

[Henry Stolen]

This is the output:
Name: Hadoop Master
Groups: /
Guest OS: Ubuntu
UUID: 85ca79ba-2237-46ca-a505-2cff093da001
Config file: C:\VirtualBox VMs\Hadoop Master\Hadoop Master.vbox
Snapshot folder: C:\VirtualBox VMs\Hadoop Master\Snapshots
Log folder: C:\VirtualBox VMs\Hadoop Master\Logs
Hardware UUID: 85ca79ba-2237-46ca-a505-2cff093da001
Memory size: 1024MB
Page Fusion: off
VRAM size: 12MB
CPU exec cap: 100%
HPET: off
Chipset: piix3
Firmware: BIOS
Number of CPUs: 1
PAE: on
Long Mode: off
Synthetic CPU: off
CPUID overrides: None
Boot menu mode: message and menu
Boot Device (1): Floppy
Boot Device (2): DVD
Boot Device (3): HardDisk
Boot Device (4): Not Assigned
ACPI: on
IOAPIC: off
Time offset: 0ms
RTC: UTC
Hardw. virt.ext: on
Nested Paging: on
Large Pages: off
VT-x VPID: on
VT-x unr. exec.: on
State: running (since 2013-11-25T22:08:15.296000000)
Monitor count: 1
3D Acceleration: off
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address:
Teleporter Password:
Tracing Enabled: off
Allow Tracing to Access VM: off
Tracing Configuration:
Autostart Enabled: off
Autostart Delay: 0
Default Frontend:
Storage Controller Name (0): IDE
Storage Controller Type (0): PIIX4
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0): 2
Storage Controller Port Count (0): 2
Storage Controller Bootable (0): on
Storage Controller Name (1): SATA
Storage Controller Type (1): IntelAhci
Storage Controller Instance Number (1): 0
Storage Controller Max Port Count (1): 30
Storage Controller Port Count (1): 1
Storage Controller Bootable (1): on
IDE (1, 0): Empty
SATA (0, 0): C:\VBVM\Hadoop Master HD.vdi (UUID: 48ed6381-0ddc-4ad6-951c-e1e1117035b5)
NIC 1: MAC: 08002760CF43, Attachment: NAT, Cable connected: on, Trace: off (file: none), Type: 82545EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 1 Settings: MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64, receive: 64)
NIC 1 Rule(0): name = guestssh, protocol = tcp, host ip = , host port = 2222, guest ip = , guest port = 22
NIC 2: disabled
NIC 3: disabled
NIC 4: disabled
NIC 5: disabled
NIC 6: disabled
NIC 7: disabled
NIC 8: disabled
Pointing Device: USB Tablet
Keyboard Device: PS/2 Keyboard
UART 1: disabled
UART 2: disabled
LPT 1: disabled
LPT 2: disabled
Audio: enabled (Driver: DSOUND, Controller: AC97)
Clipboard Mode: disabled
Drag'n'drop Mode: disabled
Session type: GUI/Qt
Video mode: 720x400x0 at 0,0
VRDE: disabled
USB: enabled
EHCI: disabled

USB Device Filters:

<none>

Available remote USB devices:

<none>

Currently Attached USB Devices:

<none>

Bandwidth groups: <none>

Shared folders: <none>

VRDE Connection: not active
Clients so far: 0

Video capturing: not active
Capture screens: 0
Capture file: C:\VirtualBox VMs\Hadoop Master\Hadoop Master.webm
Capture dimensions: 1024x768
Capture rate: 512 kbps
Capture FPS: 25

Guest:

Configured memory balloon size: 0 MB
OS type: Ubuntu
Additions run level: 0

Guest Facilities:

No active facilities.

**********
As additional data, I change th configuration to a NAT iface and did a port fwd so this way I get connected to the guest, after that, change the conf to the host only adpt and it worked, but just for a while, 'cause I reboot the host and tried to exec the VM with the host only iface and happens exactly the same, get the crash message.

[Perryg]

NIC 1: MAC: 08002760CF43, Attachment: NAT, Cable connected: on, Trace: off (file: none), Type: 82545EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 1 Settings: MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64, receive: 64)
NIC 1 Rule(0): name = guestssh, protocol = tcp, host ip = , host port = 2222, guest ip = , guest port = 22
NIC 2: disabled
NIC 3: disabled
NIC 4: disabled
NIC 5: disabled
NIC 6: disabled
NIC 7: disabled
NIC 8: disabled

I see that the only NIC has NAT. Add another adapter (guest must be shut down) set to host only and see if it pulls up the host-only interface and gets an IP.

[Henry Stolen]

Done. This is the output:
NIC 1: MAC: 08002760CF43, Attachment: NAT, Cable connected: on, Trace: off (file: none), Type: 82545EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 1 Settings: MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64, receive: 64)
NIC 1 Rule(0): name = guestssh, protocol = tcp, host ip = , host port = 2222, guest ip = , guest port = 22
NIC 2: MAC: 0800273A7CB7, Attachment: Host-only Interface 'VirtualBox Host-Only Ethernet Adapter', Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 3: disabled
NIC 4: disabled
NIC 5: disabled
NIC 6: disabled
NIC 7: disabled
NIC 8: disabled

I bring up the VM with both ifaces and had no error, except that when run the ifconfig command I realize that I had only one iface eth0, I edit the /etc/network/interfaces file and add it manually, after that exec the ifup command and it worked!!! But the I rebbot the host and the crash come again.

[Henry Stolen]

After doing all that, I delete de iface from the interfaces file, shutdown the guest, remove the second adapter and started the vm as NAT, then I shut it down again and added the second iface as host only and after the guest boot without a problem, I edit the /etc/network/intefaces and add the eth1 again, after that I run the command sudo ifup eth1 and the crash notice splash up again.

[Perryg]

Then you have an issue in the guest. Usually you don't need to edit the interfaces file these days. Maybe your mistake is there. Also you may need to edit the /etc/udev/rules.d/70-persistent-net.rules or you can delete the rules and Linux will configure it on the next boot.

[Henry Stolen]

Well it's weird you know,

The first time I created the guest it all works just fine, no need to do any configuration, but as long as I reboot the host this behavior it's on and on.

I really don't know what kind of issue it can be on the guest as it is installed out of the .iso

I really appreciate your help.

[Henry Stolen]

I created a new host on ubuntu 10.04.4 and the behavior is the same so I wonder how can this be a guest issue?

I'm gonna try downgrading the vbox version so maybe I can figure out something else.

Is there any thing you can help me with? anyone?

[Henry Stolen]

Well,

I'm pretty sure that there's a bug on dhcp server as I have configured the dhcp server for two vm's and every one get a diff ip4 network: the first one 192.168.56.105 and the other 192.168.0.101. The last one is the correct setting but I really don't know why this is happening. This DHCP is configure for a Host-Only adpt.

When I run vboxmanage to display dhcp status it says that is disables even when it is not.

I've tried with diff guest and the behavior it's the same, really weird stuff it's going on here.

I wonder if anybody else have this problem.

Regards.

[Perryg]

The default host-only IP is 192.168.56.* with .1 being the IP of the host, .100 the dhcp server and .101 => the assignable addresses.

It works for me and most other just fine. It usually is best to leave the address scheme alone and use the defaults. If you change the settings all bets are off, and requires the user to know what to do.

[Henry Stolen]

Yeah my friend,

I know this but changing the scheme it's the only workaround I could use to make the VBoxNetDHCP.exe not to crash.

I know too that if there's and option it is valid for us to use it so I guess i'll wait for the next version to see if this bug has a fix.

Anyway thanks for your help.

Best Regards.

[Perryg]

Is you hosts IP address in the 192.168.56.0 scheme ( your home network )? That's the only thing I can think of that would cause a conflict. If that is the case then yes you need to change the host-only scheme, but then it should work as it is supposed to if you get all of the settings set right.. There have been very few issue with the host-only dhcp server. Most of the issues with host-only is because Windows firewall is messing with it because it puts the host-only network as unknown.