Get the process id of the VirtualBox processes associated with that VM and kill it. Assume the name of your locked / bad vm is My-Locked-VM.
If the issue still persists, you can also kill the VBoxHeadless & VirtualBoxVM processes associated with the VM.Į.g. the machine directory, if it is empty after having deleted all the above.saved state files that the machine created, if any (one if the machine was in "saved" state and one for each online snapshot).all hard disk image files, including differencing files, which are used by the machine and not shared with other machines.
This can also be done from command line with the following command: VBoxManage unregistervm -delete ""īy doing so the following files will be deleted: The latter will completely remove the virtual machine with all files from our drive. unregister it) or if we want to also "Delete all files". We will then be asked whether we wish to only remove the machine (i.e. In the graphical frontend for Virtual Box we can easily remove a virtual machine by selecting the machine to remove and go to the menu entry "Machine -> Remove" or choose "Remove" from the right-click context menu. It makes no sense to keep a particular Virtual Machine and change the OS inside - so remove the VM and create a new one: Virtual Box Manager
0 kommentar(er)
