Setting nictrace causes VERR_PDM_MISSING_INTERFACE_ABOVE => Fixed in 1.6.4

[Brian J. Murrell]

When I try to enable NIC tracing on a VM, it fails to find the configuration. If I then disable tracing, it works. Something definitely looks wrong with enabling tracing:

$ VBoxManage modifyvm 7f10ffca-6262-4de7-ebb3-d90a55c4fc2e -nictrace1 on
VirtualBox Command Line Management Interface Version 1.6.2
(C) 2005-2008 Sun Microsystems, Inc.
All rights reserved.

brian@brian-laptop:/home/brian-old-laptop/lustre/b1_6$ VBoxManage modifyvm 7f10ffca-6262-4de7-ebb3-d90a55c4fc2e -nictracefile1 ~/lustre/vbox-nic1.log
VirtualBox Command Line Management Interface Version 1.6.2
(C) 2005-2008 Sun Microsystems, Inc.
All rights reserved.

but when I try to actually start the VM I get an error dialog which pretty much mirrors what's written to the VBox.log:

00:00:06.310 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={d5a1cbda-f5d7-4824-9afe-d640c94c7dcf} aComponent={Console} aText={Configuration error: the above device/driver didn't export the network config interface.
00:00:06.310 VBox status code: -2802 (VERR_PDM_MISSING_INTERFACE_ABOVE)} aWarning=false, preserve=false
00:00:06.320 Power up failed (vrc=VERR_PDM_MISSING_INTERFACE_ABOVE, hrc=NS_ERROR_FAILURE (0X80004005))

[Frank Mehnert]

Brian, thanks for your report and sorry that I didn't try what I suggested you. This is indeed a bug which is now fixed in SVN (see r10009). The next version of VirtualBox will contain this fix.

[Brian J. Murrell]

:-(

If it weren't for the missing "closed source" bits/features, I'd just grab that SVN rev. and build a new OSE version to get this fix rather than having to wait.

Is there any progress/movement on getting VBox fully FOSS now that you are under the Sun moniker and their mantra is FOSS now?

[Brian J. Murrell]

My apologies. I sounded ungrateful. Let me thank you specifically for the bug fix. Thanx much!