[vbox-dev] machine.delete() strange behavior Windows 7 (Python)
klaus.espenlaub at oracle.com
Mon Aug 26 11:27:57 PDT 2013
On 26.08.2013 16:57, Thomas Belian wrote:
> I'm trying to build a program which reads an XML file and control
> VirtualBox in a way VNUML works
> My whole program works but I have one problem.
> For removing my scenario after working with it I use the following
> which works very well under Scientific Linux 6.4 and Ubuntu 12.04 LTS,
> but on Windows 7 64 Bit all settings will be deleted, but not the hard
> disk, which is a linked clone.
This is unfortunately (to me) ambiguous. Do you have the 100% identical
(structurally) setup on both Linux and Windows, i.e. that the linked
clone is there in both cases, set up in the same way?
It's expected behavior that this command does NOT delete all disk images
used by this VM. It will only delete what isn't needed for other VMs,
i.e. that part of the medium tree which is private to this VM.
Everything else will be left over.
Your command is doing the same thing as "VBoxManage unregistervm vmname
--delete", so if you think this is behaving differently on Linux and
Windows then you need to describe exactly how you create the VM config
(exact order of operations, probably it'd be helpful to provide the VM
config files which you produce). Then we should be able to reproduce.
> This line works on Linux but not on Windows, has anyone an idea why?
More information about the vbox-dev