TurnKey Linux Virtual Appliance Library

'Machine not mutable' error with Fileserver VM on Virtualbox

This is my first go with virtualisation and I feel sunk already! When I attempt to import the fileserver VM into Virtualbox I get this message -

The machine is not mutable (state is PoweredOff)

I get the same result with VirtualBox on Ubuntu 10.04 and on Windows XP, and I have verified the download and redownloaded it several times. The only things that come up upon googling the error message seem to be to do with sharing folders and leaving VMs powered on.

I'm probably not doing something obvious because of my inexperience. Any help is appreciated, thanks.

Same Error with Drupal Appliance

I am using the VM image on Mac OS X with Virtual Box 3.2.2 and I get the same problem when I try and import the VM image. I too am new to these images and Virtual Box so it may be a user error. I did however follow the instructions in the documentation and have tried it several times.

Seems to be an issue with 3.2

I hit the same thing, and dropped back to 3.1.8 and was able to import my image.


Same ERROR with LAMP

Me too. Please advise.

Same here, the debug trace as

Same here, the debug trace as follows;


p, li { white-space: pre-wrap; }

Result Code:





IMachine {6d9212cb-a5c0-48b7-bbc1-3fa2ba2ee6d2}

Jeremy's picture

For what its worth I just downloaded and tested Core

I'm using VirtualBox 3.2.0-OSE in Ubuntu 10.04 (from the repos) and the Core ovf imported fine, the VM then started fine too.

Drupal, Fileserver and Core are "not mutable"

The debug traces are the same.  Using VirtualBox 3.2.2

An upgrade to VirtualBox 3.2.4 kills the mutable error

I just upgraded to the latest version of VirtualBox (released June 7) and decided to retry setting up the Drupal6 appliance, and it worked. The VM looks fine, too.

Anyone looking for a solution

Anyone looking for a solution regarding inaccessible VBox due to a corrupt saved state on Windows Host OS > Try the following ..it worked for me

open your command prompt
cd to your Virtualbox directory in your Program Files
Then type following command to discard the current state :

Program Files\Sun\VirtualBox>VBoxManage discardstate uuid

Note: replace uuid with your 'Machine uuid' found in  Machines/YourMachineName/YourMachineName.xml-prev

..this will discard the corrupt state and restore the  'power off' state ..after that you be able to start your virtual machine as normal.

VBoxManage also has a poweroff and reset option, which may be useful to some, if the above does not do the trick. You can find more info on this here:

Jeremy's picture

Good work, I'm sure that'll help some!

Also AFAIK these instructions should be OS agnostic (ie should work on other OSs too) - except the location will be different. In Linux I think you can use the commands direct from the command propt (no cd req'd).

FYI Linux users: Linux Magazine had an interesting article about using Vbox from the command line thats worth a look if you do much with VBox.

Thanks that worked!

Thanks that worked!

4 1/2 years later ... that

4 1/2 years later ... that worked!  Saved me lots of time.  Thanks

(I couldn't do a "modifyvm uuid --nic1 null" without the above, and was unable to boot my vm)

Post new comment

The content of this field is kept private and will not be shown publicly. If you have a Gravatar account, used to display your avatar.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <p> <span> <div> <h1> <h2> <h3> <h4> <h5> <h6> <img> <map> <area> <hr> <br> <br /> <ul> <ol> <li> <dl> <dt> <dd> <table> <tr> <td> <em> <b> <u> <i> <strong> <font> <del> <ins> <sub> <sup> <quote> <blockquote> <pre> <address> <code> <cite> <strike> <caption>

More information about formatting options

Leave this field empty. It's part of a security mechanism.
(Dear spammers: moderators are notified of all new posts. Spam is deleted immediately)