Removing a Guest VM from the command line

[memilanuk]

Hello,

I'm hoping this is a lot easier than it seems...

What command (or string of commands) do I need to do to completely remove, unregister, nuke, whatever a given guest VM? When looking at the manual there are all kinds of options for adding and modifying stuff, but it sure skates around the topic of getting rid of a VM once its set up...

TIA,

Monte

[Perryg]

VBoxManage unregistervm <uuid>|<name> [--delete]

[Sasquatch]

And don't forget "VBoxManage closemedium disk|dvd|floppy <uuid>|<filename> [--delete]" to remove the VDI file too.

[memilanuk]

VBoxManage unregistervm <uuid>|<name> [--delete]

Didn't work, complained about still having disk images registered/attached/mounted (don't recall the exact verbage)

Start to finish, once you decide to get rid of a VM and its associated disk image... what command sequence do you use?

[Perryg]

Snapshots?

[memilanuk]

Didn't last long enough for there to be any.

[Sasquatch]

Then it would appear you remove the disk first. Or at least unregister it from the VM.

[alpha_YbSXf]

The unregister command worked for me, when I ran it as a elevated user (adminstrator on Windows).

However, it did leave behind the Snapshots. So I manually deleted that after running the unregistervm --delete option.

Further, if I run `VboxManage.exe list vms`the old VM is still listed.

How do I remove and unlist the non-existent VM from the command line?

[socratis]

I'm sorry, but this is an 8-year old thread. It's beyond the limits of a "dead thread". I'm going to have to ask you to open a new thread, we can't be building the discussion on such old foundation.

Locking this.

PS. Do *not* change the user when doing VM operation. VirtualBox uses a per-user environment. Becoming root (or any other user) does *not* give you access or more powers to the original user's VMs. *ALWAYS* perform VM operations as the user that actually created the VMs.