Ticket #3595 (closed defect: fixed)
xVM and VBoxManage report virtual machine as aborted when it is running correctly
|Reported by:||glynn_bird||Owned by:|
OK. The host is a Centos 5.2 machine. We have several Centos 5.2 (text-only) guest machines cloned from one original. All works fine unless you change the settings (in this case, the network configuration) of one of the switched off guests (keira). The xVM GUI then crashes. When it runs again, it reports one of the running machines as "aborted", even though it is running correctly (see "reese").
The offline guest whose configuration was being edited ("keira") is reported as "Powered Off", but the "settings" button is now no longer available.
A reboot of the host usually solves the problem, but this means downtime for all of the guests.
Another headache is that the guest that is marked as "aborted" can be started by clicking on the green arrow, even though it is already running! This isn't good.