3.2.10 VirtualBox Forgets Which VMs are Running

[kihjin]

VirtualBox 3.2.10 OSE
Host: Ubuntu Server 10.04.1

I run a server with multiple headless VirtualBox instances running. I've had this problem with older versions of VirtualBox, where, some event would cause VBoxManage to "forget" which VMs were actually running. The VMs would continue to function normally, but any attempt to communicate to them through VBoxManage would fail. No savestate, acpipowerbutton, not even poweroff. VBoxManage list runningvms would not display all of the actually running systems

It seems like the event that causes this issue is when one of the instances is restarted, probably the first one, not really sure.

I've experienced this issue in older releases, so I am surprised to continue to see it now. It's frustrating because once the states are lost, you can't reclaim the running VMs.

I propose a VBoxManage resyncvms command that would somehow (if you pass in PIDs) enable you to reclaim these "zombie" instances. If we can't make it impossible for the states to be forgotten, then there should be a way to reclaim them.

[Perryg]

How are you starting the headless VM's? One at a time or with some script?