All,
Just sharing this information to save someone else the time and trouble
that I just went through to run down a problem.
If you have a virtual machine that you start in headless mode, you might see
something like this when attempting to start it:
\\=======
Oracle VM VirtualBox Headless Interface 4.0.6
(C) 2008-2011 Oracle Corporation
All rights reserved.
Invalid machine name or UUID!
//=======
Worse, it could happen that you get that message most of the time, but then
sometimes find that the machine was started (really!), You need to go poking
around
in the MachineName.vbox XML file to see if something is out of whack.
In particular, a mismatch between the HardDisk entries near the top of
the file and the StorageController and AttachedDisk entries at the bottom
will cause this error to occur.
How did this come to be? Beats me. A new disk was added a few days
ago, using only the VirtualBox GUI. I started and restarted the system
many times (adding a new disk for a Windows virtual machine required
that), and it worked just fine.
The .vbox-prev file provided no insight, because the file was identical to
the .vbox file and timestamped as of the latest attempt to start the VM.
Anyway, it's resolved now through hand-editing the file and adding a
missing HardDisk entry corresponding to the hard disk I added through
the GUI at the beginning of the week (and that I used for a couple of
days).
Hope this is useful for someone!
Eric
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
VBox-users-community mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
