"Invalid Settings Detected" and won't go away

[bhuga]

VBox 4.0.2, OS X. Ubuntu 10.10 guest image.

Nothing fancy. One bridged ethernet adapter is the only thing i changed from the defaults.

I spent about 4 hours messing with the image, making it what I want.

Now, I want to add a host-only network adapter. I cannot.

My error message is "Invalid settings detected", which appears as soon as I load the settings page for the VM and does not go away no matter what I do, near as I can tell. I cannot find anything that tells me what is invalid, nor why it is invalid when I load the saved ones (these settings work fine when i boot the VM).

So i go to the command line:
VBoxManage modifyvm myvm --nic2 hostonly
VBoxManage startvm myvm


VBoxManage: error: Failed to open/create the internal network 'HostInterfaceNetworking-en0: Ethernet' (VERR_INTNET_FLT_IF_NOT_FOUND).
VBoxManage: error: Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND).
VBoxManage: error: Unknown error creating VM (VERR_INTNET_FLT_IF_NOT_FOUND)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component Console, interface IConsole, callee

modifyvm again to remove the nic lets it boot again.

Any help appreciated.

[Perryg]

Update to version 4.0.4 or look in the preferences -> network and make sure that the host-only adapter is installed and configured.

[bhuga]

The problem persists after upgrading to 4.0.4.

The nic is not installed or configured in the preferences. if I add it via the CLI, it appears there, and when i remove it again, it goes away. I'd be fine if the VM started, but i have to remove the VM to start it.

[Perryg]

The NIC is not what I am talking about. It is the missing service. See screen shot below.

Pref-Net.png (56.95 KiB) Viewed 45880 times

[bhuga]

Ah, sorry, I misunderstood.

Yes, i have the vboxnet0 adapter, and it shows up in ifconfig as well.

[Sasquatch]

Then use the proper VBoxManage syntax. You're missing a few definitions in your command. You tell it to use hostonly, but you fail to tell it which hostonly interface to use (you can have multiple). So, change the following:

Code: Select all

VBoxManage modifyvm myvm --nic2 hostonly
to
VBoxManage modifyvm myvm --nic2 hostonly --hostonlyadapter1 vboxnet0

[bhuga]

Ah! Thanks for showing me where to look. The hostonly adapter was set to my local ethernet interface, indeed an invalid configuration.

vbm modifyvm dydra --hostonlyadapter2 vboxnet0

That allows it to start. This is probably reproduceable if one were to spend time on it--at one point I had the second adapter as a bridge on en0, but I then disabled the adapter and switched the first NIC to be bridged.

I still can't edit any settings in the GUI. But im up and running.

[anshprat]

hi,

I faced the exact same problem and this post guided me towards the correct answer. For others:

I had a vm on host fedora 14. Today I updated to fedora 15 and my my vm failed to start. Also vboxnet0 wasnt showing in my host ifconfig.

After seeing this post, I did the following.

File -> Preferences -> Network

1) Deleted the original vboxnet0 (original host only n/w device). It warned about deleting the same. I chose yes.
2) Recreated the device by clicking on + on the right hand side.

And voila, my vm worked beautifully as before

Hope this helps anyone else in similar situation.

cheers
Anshu Prateek