I'm posting this here to ask if others have had similar experiences and if it'd make sense to try to take to the developer list in some way. a short time ago, I upgraded my vbox installation on my home machine, I shutdown all my VMs, ran the upgrade, rebooted the server host OS, forgot about the extension pack for the new version of virtualbox, several VMs were started by my init scripts, many failed due to settings requiring the extension pack. I installed the pack then began using the virtualbox gui interface to reset/reboot and verify the new machines. 2 in particular were very troublesome; they appeared to be down in the gui interface, attempts to start them would give machines with bad root partitions, fsck, restart, repeat.
after much frustration and more cooldown time, I discovered there were multiple instances of the VM running (specifically after shutting down the gui console instance, the gui showed the VM as down, ps auxww | egrep -i $vm_name gave processes). after killing the processes, I was able to start the VM and connect to it in my normal, expected ways. my question is: should there be more/better VM state locking to prevent this sort of thing from being able to happen? -- public gpg key id: AE60F64C ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk _______________________________________________ VBox-users-community mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vbox-users-community _______________________________________________ Unsubscribe: mailto:[email protected]?subject=unsubscribe
