virtualbox.org

I know many people had problems when upgading to the current version 3.0.6 because of the fact that the VBox guest additions have been moved to another place. This is my problem, too. However I'm not able to use the workaround because I can't remove the guest additions form my virtual machines. Whenever I try to release the guest additions I get an error message "The machine is not mutable (state is 2)".

Any suggestions?

Thanks in advance

murcalumis

In the meantime I found a workaround for my problem. I downgraded back to version 3.0.4, started my virtual machines and shut them down instead of saving the state of the virtual machine. Then I removed the guest additions image from my virtual machines. After that I reinstalled version 3.0.6 and was able to start my virtual machines again. There's still an invalid entry in the virtual disk manager under cd/dvd image pointing to a wrong path. I can't delete that invalid entry.
Has anyone an idea on how I can get rid of that invalid entry?

Thanks

murcalumis

You can remove the entry if you release the file from every VM you have, then select it and hit the remove button. That will simply unregister the ISO. If it really doesn't work, close all instances of VB and open the VirtualBox.xml file. Look up the GA ISO in that file and either remove the entry, or modify the line to the proper location.

Removal of the invalid entry doesn't work (option is greyed out). If I edit the VirtualBox.xml file in order to get rid of the wrong guest addition entry one of my virtual machine no longer works (see screenshot).

murcalumis

You can't remove the faulty GA entry, because it's still attached to the now inaccessible VM. You have to fix that VM or remove it before you can remove the GA entry.

Ok. How can I fix it? If i copy back the original VirtualBox.xml then I can start that otherweise inaccessable VM but still get a warning concerning the faulty guest addition. If I edit the XML then I don't get the error message but my VM is inaccessable.

What have you changed exactly? It seems that you messed around way to much with the main xml file, a VM doesn't suddenly become inaccessible unless you screw it up badly.

I'm seeing the same problem after upgrading from 2.2.4 to 3.0.8. I was careful to only remove the one xml entry for the now missing GA iso. I even tried copying the path of the new GA iso, but then it complains about not being able to register the iso twice.

How do I remove the stale entry?

If you have it mounted to any VM, you have to modify that XML file too, otherwise you can just remove the single line that mentions the GA ISO. Looks like this: Of course, this is on Linux Host, but Windows has a similar entry, only the path looks different (of course).