Virualbox on my Windows/XP host does not start after defining port forwarding.

[Y.W.Lee]

The host is Windows/XP with service pack 3, guest is Solaris 10 and VirtualBox is 1.6.2. After defining port forwarding as below,

<ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/solar/GuestPort" value="631"/> <ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/solar/HostPort" value="6631"/> <ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/solar/Protocol" value="TCP"/>

Virtualbox crashed with the following message:

Configuration error: Failed to get the "MAC" value. VBox status code: -2103 (VERR_CFGM_VALUE_NOT_FOUND).

Result Code: E_FAIL (0x80004005) Component: Console Interface: IConsole {d5a1cbda-f5d7-4824-9afe-d640c94c7dcf}

[Seth Keiper]

Is your Solaris guest using the Intel network adapter? Is port 6631 in use on the host?

[Y.W.Lee]

I changed the network adapter to PCnet-FAST III(Am79c973) from Intel PRO/1000 MT Desktop (82540EM), re-installed Solaris and defined port forwarding.
Then no crash occurs.

Thanks for the comment by erstazi.

[thepacketmaster]

I followed the suggestion of changing the network adapter to PCnet-FASTII from the Intel Pro/1000 MT Desktop. Next I just went in and moved /etc/dhcp.e1000g0 to /etc/dhcp.pcn0, and /etc/hostname.e1000g0 to /etc/hostname.pcn0. After a quick reboot to confirm it boots up properly, everything is good.

[Frank Mehnert]

I will close this bug. We are aware that port forwarding should be possible without these VBoxManage setextradata hacks and this is actually on our TODO list.