NAT Problem with new version 3.2.2 r62298

[Flash77]

Hi all,
I updated to above version this morning. After the update I am not able to start up WinXP in Mac OSX host any more.

00:00:01.047 VMSetError: /Users/vbox/tinderbox/mac-rel/src/VBox/Devices/Network/DrvNAT.cpp(1083) int drvNATConstruct(PDMDRVINS*, CFGMNODE*, uint32_t); rc=VERR_PDM_DRVINS_UNKNOWN_CFG_VALUES
00:00:01.047 VMSetError: Unknown NAT configuration option, only supports PassDomain, TFTPPrefix, BootFile and Network
00:00:01.047 PDM: Failed to construct 'pcnet'/0! VERR_PDM_DRVINS_UNKNOWN_CFG_VALUES (-2805) - A driver encountered an unknown configuration value. This means that the driver is potentially misconfigured and the driver construction failed because of this.
00:00:01.063 VMSetError: /Users/vbox/tinderbox/mac-rel/src/VBox/VMM/VM.cpp(316) int VMR3Create(uint32_t, void (*)(VM*, void*, int, const char*, unsigned int, const char*, const char*, char*), void*, int (*)(VM*, void*), void*, VM**); rc=VERR_PDM_DRVINS_UNKNOWN_CFG_VALUES
00:00:01.063 VMSetError: Unknown error creating VM
00:00:01.063 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={6375231a-c17c-464b-92cb-ae9e128d71c3} aComponent={Console} aText={Unknown NAT configuration option, only supports PassDomain, TFTPPrefix, BootFile and Network (VERR_PDM_DRVINS_UNKNOWN_CFG_VALUES).
00:00:01.063 Unknown error creating VM (VERR_PDM_DRVINS_UNKNOWN_CFG_VALUES)} aWarning=false, preserve=false
00:00:01.126 Power up failed (vrc=VERR_PDM_DRVINS_UNKNOWN_CFG_VALUES, rc=NS_ERROR_FAILURE (0X80004005))


If I disable the network adapter (NAT) prior to booting the client, and enable the network adapter again when the client is running, everything works!
I didn't change any settings during the last few weeks, to me this indicates a problem with the update.

Any ideas?

Regards
Patrick

[frank]

I cannot see this without having the full VBox.log file available (please attach). But it might be possible that you have NAT forwarding rules enabled. Starting with VBox 3.2.0 the handling of NAT port forwarding changed. You have to remove all related ExtraData keys and use VBoxManage modifyvm VM_NAME -natpf... (see user manual) instead.

[Flash77]

Hi Frank,
attached is the full VBox.log file.
Please note that I did not set up any NAT forwarding (at least not to my knowledge) and that I did not use VBoxManage modifyvm... in the past.

Prior to the last update everything went fine. Now I have to set the network adapter to "not connected" and once WinXP is running I can change to NAT without any problems...

Regards
Patrick

[frank]

You still have extra data set up for this VM. Do the following:

Code: Select all

VBoxManage getextradata VB_WIN_XP enumerate

This will show you some entries containing pcnet. Remove these entries with

Code: Select all

VBoxManage setextradata VB_WIN_XP /Devices/pcnet/0/LUN#0/Config/SocketRcvBuf
VBoxManage setextdadata VB_WIN_XP /Devices/pcnet/0/LUN#0/Config/SocketSndBuf
VBoxManage setextradata VB_WIN_XP /Devices/pcnet/0/LUN#0/Config/TcpRcvSpace
VBoxManage setextdadata VB_WIN_XP /Devices/pcnet/0/LUN#0/Config/TcpSndSpace

And re-apply these settings with

Code: Select all

VBoxManage modifyvm VB_WIN_XP --natsettings1 ,128,128,128,128

Then your VM should start fine.

[Flash77]

Hi Frank,
thanks for the profound knowledge & support.

VBoxManage setextradata VB_WIN_XP /Devices/pcnet/0/LUN#0/Config/SocketRcvBuf etc. did actually not remove the entries from VB_WIN_XP.xml

I had to remove these extradata entries manually from the xml file, now everything is working again like a charm.

Thanks again
Patrick

[frank]

Erm yes, you are on an Linux host, therefore the command line was cut at '#'. So you should have used " " quotes around the extradata keys.