[vbox-dev] IMachine::setSettingsFilePath not supported?

Klaus Espenlaub klaus.espenlaub at oracle.com
Wed Jul 2 15:26:02 GMT 2014


On 02.07.2014 09:18, Karoline Haus wrote:
> Hi Klaus,
> Yes, the way I'm doing it now is to change the default settings path
> before I import a VM, and then change it back to the system default. I
> had figured that way myself already :-) It is OK and it does work for now.
> I use VBOX 4.3.12 under Gentoo Linux, and I think that is the current
> VBOX version, isn't it?

Yes. 4.3.14 is likely to happen soon (no exact dates as usual, when it's 
ready), but there's no plan to change this bit of the API, just pushing 
out bug fixes. Quite a few have been piled up in the mean time.

We hope to find time to address this for the next major release, but 
there's always so much to do...

> Thanks for your help.
> Karoline
> Klaus Espenlaub <klaus.espenlaub at oracle.com> schrieb am 12:23 Dienstag,
> 1.Juli 2014:
> Karoline,
> On 30.06.2014 13:53, Karoline Haus wrote:
>  > I would like to be able to create a VM under a specific folder. In fact,
>  > I would like to import a VM from an OVA file, and then have that VM
>  > registered under a specific folder. However, by default VBox will store
>  > it under $HOME/.VirtualMachines and I cannot figure how I can use the
>  > API to change the settings file path on VM import? I have seen there is
>  > an IMachine::setSettingsFilePath function, but I use the Python API and
>  > it does return a "Not Implemented" error. Is there any other way to
>  > store VMs under a specific location?
> Changing of the settings file path for an existing VM is a todo, it
> needs a lot of groundwork (moving disk images in the directory and the
> like).
> What you want is setting the default machine folder before importing,
> maybe reverting this change afterwards (if you want locally created VMs
> still in the default place).
> I'm wondering why your setup uses a .VirtualMachines subdirectory, I
> don't see this anywhere in the code. Ancient VirtualBox versions default
> to ~/.VirtualBox/Machines, and newer versions default to ~/VirtualBox
> VMs, but stick to the old default if it's an upgrade. One can switch to
> the new default though, or pick a totally different directory.
> Klaus
>  >
>  > Many thanks for any pointers.

More information about the vbox-dev mailing list