I had the following odd behaviour yesterday on my OpenNebula installation (2.0.1):
* A user sent a "suspend" command to a VM. The VM got stuck in state SAVE-SUSPEND. No error in oned.log, vm.log, or /var/log messages and syslog * From that moment on until a restart of oned any newly created VM would get stuck in state BOOT and not proceed beyond that. * After restarting oned I could send the VMs stuck in BOOT a "restart" command and they are now running. * The VM stuck in SAVE-SUSPEND is still in that STATE (more than 12h later). In case it helps this is the images directors of the stuck VM: oneadmin@nebnode01:~/var/214/images$ ls -al total 2590848 drwxrwxrwx 2 oneadmin cloud 2048 2011-06-21 17:46 . drwxrwxrwx 3 oneadmin cloud 2048 2011-06-21 17:44 .. -rw-rw-rw- 1 root root 1756 2011-06-21 17:46 checkpoint -rw-r--r-- 1 oneadmin cloud 962 2011-06-21 17:44 deployment.0 -rw-rw-rw- 1 oneadmin cloud 505151488 2011-06-21 17:45 disk.0 -rw-rw-rw- 1 oneadmin cloud 2147483649 2011-06-21 17:44 disk.1 -rw-r--r-- 1 oneadmin cloud 372736 2011-06-21 17:44 disk.2 Carsten [cid:[email protected]]<http://www.csiro.au/> Carsten Friedrich Research Team leader ICT Centre, GPO Box 664,Canberra, ACT 2601 Phone: +61 2 6216 7019 Email: [email protected]<mailto:[email protected]> Web: http://www.csiro.au/org/ICT.html
<<inline: image001.gif>>
_______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
