dhcp-server problem

[morgon]

Hi,

I am running VirtualBox 3.2.4 on Ubuntu Lucid.
I've installed it via virtualbox-3.2_3.2.4-62467~Ubuntu~lucid_i386.deb.

Everything (so far) works fine, apart from one thing: I cannot start a dhcp-server for internal networking.

Here the problem:

Code: Select all

VBoxManage dhcpserver add --netname intnet -ip 192.168.10.1 --netmask 255.255.255.0 --lowerip 192.168.10.50 --upperip 192.168.10.10 --enable
Oracle VM VirtualBox Command Line Management Interface Version 3.2.4
(C) 2005-2010 Oracle Corporation
All rights reserved.

ERROR: code NS_ERROR_INVALID_ARG (0x80070057) - Invalid argument value (extended info not available)
Context: "CreateDHCPServer(NetName.mutableRaw(), svr.asOutParam())" at line 248 of file VBoxManageDHCPServer.cpp
error: failed to create server

I have tried different ip-ranges bit to no avail...

Anyone with an idea about what this could be?

Many thanks!

[Perryg]

From the host terminal 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.

[morgon]

Ok, here the output for one of my VMs (another one looks the same):

Code: Select all

VBoxManage showvminfo vm1 --details
Oracle VM VirtualBox Command Line Management Interface Version 3.2.4
(C) 2005-2010 Oracle Corporation
All rights reserved.

Name:            vm1
Guest OS:        Ubuntu
UUID:            ff66cb62-f92d-447e-8238-2f76c58bc7bf
Config file:     /home/mh/.VirtualBox/Machines/vm1/vm1.xml
Hardware UUID:   ff66cb62-f92d-447e-8238-2f76c58bc7bf
Memory size:     128MB
Page Fusion:     off
VRAM size:       8MB
HPET:            off
Number of CPUs:  1
Synthetic Cpu:   off
CPUID overrides: None
Boot menu mode:  message and menu
Boot Device (1): HardDisk
Boot Device (2): Not Assigned
Boot Device (3): Not Assigned
Boot Device (4): Not Assigned
ACPI:            on
IOAPIC:          off
PAE:             off
Time offset:     0 ms
RTC:             local time
Hardw. virt.ext: on
Hardw. virt.ext exclusive: on
Nested Paging:   on
Large Pages:     off
VT-x VPID:       on
State:           powered off (since 2010-06-19T18:08:09.000000000)
Monitor count:   1
3D Acceleration: off
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address: 
Teleporter Password: 
Storage Controller Name (0):            IDE Controller
Storage Controller Type (0):            PIIX4
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0):  2
Storage Controller Port Count (0):      2
IDE Controller (0, 0): /home/mh/.VirtualBox/HardDisks/hd1.vdi (UUID: b17bf66e-e768-4ebe-b6ca-28c20c96a741)
IDE Controller (0, 1): /home/mh/.VirtualBox/Machines/vm1/Snapshots/{f568b14c-5126-49f8-b6fc-a4cea139b23a}.vdi (UUID: f568b14c-5126-49f8-b6fc-a4cea139b23a)
IDE Controller (1, 0): /win/d/dsl-4.4.10.iso (UUID: ea0a8af8-33b5-45cc-a896-614915673220)
NIC 1:           MAC: 080027F8A346, Attachment: Internal Network 'intnet', Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0
NIC 2:           disabled
NIC 3:           disabled
NIC 4:           disabled
NIC 5:           disabled
NIC 6:           disabled
NIC 7:           disabled
NIC 8:           disabled
Pointing Device: PS/2 Mouse
Keyboard Device: PS/2 Keyboard
UART 1:          disabled
UART 2:          disabled
Audio:           disabled
Clipboard Mode:  Bidirectional
VRDP:            disabled
USB:             disabled

USB Device Filters:

<none>

Shared folders:  <none>

Guest:

Configured memory balloon size:      0 MB

Just to understand this: Why is the configuration of a VM relevant here? Should the dhcp-server not be independent of any VM?

cheers

[Perryg]

I just wanted to be sure of the network name. Whether it was intnat or intnat1

VBoxManage dhcpserver add --netname intnet -ip 192.168.10.1 --netmask 255.255.255.0 --lowerip 192.168.10.50 --upperip 192.168.10.10 --enable

Be sure that you use --ip and not -ip like you have here and also look at the upper and lower addresses the upper can not be less then the lower.

[morgon]

The network name does not matter really (as far as I understand it).
It just has to match whatever is configured for the VM, but even if there is no VM that uses the network name you start the dhcp-server for, the command should be successful (the server simply would never be used).

At least that is my understanding - and if that is wrong you would expect a proper error message when you use an illegal network name.

And indeed I used "--ip" - but the problem remains the same - actually I think both -ip and --ip work the same (if you don't use any of these it tells you that you need to supply --ip, but if you use -ip it does not complain about a missing --ip).

I've also used several different ip-ranges, but to no avail...

The strange thing is that seem to be the only one with this problem (at least Google finds nothing) and there are no log-files or anything - how can I investigate this further?

[Perryg]

Well I just tried to create this and it fails for me as well. I had to actually downgrade from my beta version before I tried as I would not have been able to report this. I will report this later tonight or in the morning and see what the devs have to say. I will post the bugtracker ticket number here when I have it posted.

[Perryg]

Ticket created and you can add your name to it or simply monitor http://www.virtualbox.org/ticket/7031#

[Perryg]

* changed from Can not create a DHCP server for internal network. to Can not create a DHCP server for internal network => Fixed in SVN.

This bug will be fixed in the upcoming maintenance release (not in the 3.2.6 Beta 1 yet).


Edit: Problem is still not fixed. Work is still going on.

[morgon]

Ok - great!

For the time being this issue is not really problematic for me, but it is nice to know that it is a bug and not a problem with my system.

Thanks for the support.