VirtualBox

Ticket #9204 (closed defect: duplicate)

Opened 3 years ago

Last modified 18 months ago

Invalid settings detected

Reported by: srondeau Owned by:
Priority: minor Component: other
Version: VirtualBox 4.0.10 Keywords:
Cc: Guest type: Windows
Host type: Linux

Description

"Invalid settings detected" is the only message you receive at the bottom of the VirtualBox GUI's Settings page if there is a problem with settings. The lack of specifics makes it difficult to determine which settings are invalid. In our case, we had checked the "External Display" setting but did not provide any other information.

Is it possible to provide the name of the tab or something else that would allow us to focus on the setting in error?

Attachments

virtualbox.log Download (9.4 KB) - added by rayden 18 months ago.
Console log

Change History

comment:1 follow-up: ↓ 2 Changed 3 years ago by frank

Are you really on a Linux host? In that case, which Linux distribution is that and do you use GNOME or KDE and which style do you have installed? Because actually there _is_ such information but it is probably hidden for you.

comment:2 in reply to: ↑ 1 Changed 3 years ago by srondeau

Replying to frank:

Are you really on a Linux host? In that case, which Linux distribution is that and do you use GNOME or KDE and which style do you have installed? Because actually there _is_ such information but it is probably hidden for you.

Fedora 15 (installed to hard disk from a Live CD). Gnome 3 is used. I don't use the GUI much, so I don't know what you mean by "style" or how to find out what style is installed.

My point is that the information can be made clearer in the existing message, vs. having to hunt for it, though I would like to know how to hunt for it and get a clear answer. I tried:

VBoxManage showvminfo myvm

But it did not indicate the error clearly. After finding out what it was, I reviewed the information it provided, and it indicated "Ports ," in the VRDE settings, which to a trained eye should have shown the problem. I inherited this problem from an intern working for me, so even though I might be able to find the problem, she was confused by the vague message... and it prevented her from doing anything else until it was resolved.

comment:3 follow-up: ↓ 4 Changed 3 years ago by frank

  • Status changed from new to closed
  • Resolution set to duplicate

Well, then this is a completely different problem. The port value was lost by some bug and IIRC there is already another ticket open for this problem. When you remove the value form the VRDE port, then the 'invalid settings detected' message appears but in this context the message is quite clear (because the value was just removed).

For other problems (e.g. network card attached to hostif but hostif not available), there is an error message which points to the real problem.

Because the missing VRDE value is described in another ticket I will close this one.l

comment:4 in reply to: ↑ 3 Changed 3 years ago by srondeau

  • Status changed from closed to reopened
  • Resolution duplicate deleted

Replying to frank:

Well, then this is a completely different problem.

My problem is with the lack of information in the error message, not with the actual error that occurred. The error message indicated in the ticket subject is too vague to figure out where to look. I could not find the error easily, nor could my intern. That's the problem.

comment:5 Changed 3 years ago by frank

  • Status changed from reopened to closed
  • Resolution set to duplicate

I explained where this lack comes from. The value was cleared by accident, that's the actual bug, not the missing information -- the case you saw should never happen.

Changed 18 months ago by rayden

Console log

comment:6 Changed 18 months ago by rayden

Upgraded from VirtualBox 4.2.1 to 4.2.2(r81494) and got this error "Invalid settings detected" on the Settings page.

Already reinstalled VirtualBox from the uninstall tool provided, but the error appears again.

I don't know what to do.

Check the attachment provided!

comment:7 Changed 18 months ago by rayden

Deleted the VirtualBox.xml and VirtualBox.xml-prev in ~/Library/VirtualBox just to see if the new one would coutain no errors. But it's the same. The errors still appears even with an automatic created one.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use