Changes between Version 70 and Version 71 of User_FAQ

Timestamp:

Feb 13, 2008 3:34:35 PM (17 years ago)

Author:

umoeller

Comment:

+ shared folder problem

User_FAQ

@@ -11 +11 @@
 == General ==
 
- * Sometimes VirtualBox fails to start with a message on the lines of 
+ * Sometimes !VirtualBox fails to start with a message on the lines of 
 {{{
 Failed to create VirtualBox COM object
@@ -18 +18 @@
  This usually means that the !VirtualBox COM server was unable to start up, and is often a sign of problems in your installation of !VirtualBox.  In many cases this problem can be solved simply by reinstalling !VirtualBox.  Reinstalling will simply set up the !VirtualBox program files again, and will not affect any virtual machines which you have created.
 
- If this does not help, and you wish to investigate the problem further yourself, try starting the !VirtualBox COM server (the program VBoxSVC in the VirtualBox program folder) from a command prompt or a DOS box.  You may be able to see what is going wrong from error messages when the server starts.
+ If this does not help, and you wish to investigate the problem further yourself, try starting the !VirtualBox COM server (the program VBoxSVC in the !VirtualBox program folder) from a command prompt or a DOS box.  You may be able to see what is going wrong from error messages when the server starts.
 
  Please do not open bug reports when you get this error before you have tried the other available support channels ([http://forums.virtualbox.org/ forums], [wiki:"Mailing_lists" mailing lists] and [wiki:"IRC" IRC]).
@@ -25 +25 @@
 
  Because the guest sees a __virtual__ graphics card, not the host graphics card. The virtual graphics card provides the necessary VESA and VGA features to make the guest operative systems work OK. Additional features, like higher resolutions, is provided by the graphics driver included with the guest additions. More details on how to install guest additions and features of the virtual graphics card can be found in the manual.
+
+ *  I use !VirtualBox 1.5.0 and I one of my VMs has become inaccessible. I get the following  error message: "Hard disk X is already attached to a machine Y." But I'm sure I didn't attach this hard disk to any other VM or anything like that.
+
+ Most likely, you have defined one or more shared folders for this VM but later deleted these folders on the host (or made them inaccessible in some other way). This was a known issue of version 1.5.0, but it's been '''fixed with !VirtualBox 1.5.4.''' If you can't upgrade, you can try to re-create the inaccessible shared folders. You may find these shared folders in the .xml file mentioned in the error message -- open it in any text editor, search for the text `<SharedFolder` and then look at the path that immediately follows the text  `hostPath=`. Alternatively, open this .xml in any text editor and delete all such !SharedFolder elements.
 
 == Linux hosts ==