Hi list friends, There are a lot of reports without a conclusion about: Sun Jan 23 11:53:52 2011 [LCM][I]: New VM state is BOOT Sun Jan 23 11:53:52 2011 [VMM][I]: Generating deployment file: /srv3/cloud/one/var/60/deployment.0 Sun Jan 23 11:53:54 2011 [LCM][I]: New VM state is RUNNING Sun Jan 23 11:54:29 2011 [VMM][I]: VM running but it was not found. Restart and delete actions available or try to recover it manually Sun Jan 23 11:54:29 2011 [LCM][I]: New VM state is UNKNOWN
and few about onevm list columns, that show 0 values, such as TMEM: ID NAME CLUSTER RVM TCPU FCPU ACPU TMEM FMEM STAT 21 mc2-frontend default 0 400 356 400 0K 1.6G on 22 mc2-node01 default 2 400 396 380 0K 1.6G on 23 mc2-node02 default 2 400 400 380 1.7G 1.5G on 24 mc2-node03 default 2 400 398 380 1.7G 1.5G on The problem with my cluster is the default system language. Two of my nodes, mc2-frontend(that is a node also) and mc2-node01 were installed in my nature language(pt_BR.UTF-8), while the others were installed in English(en_US.UTF-8). The solution was change default language to en_US.UTF-8 in all cloud nodes. On Ubuntu Server 9.10: change LANG environment variable, on /etc/default/locale file, to LANG="en_US.UTF-8" SOLVED! Maybe methods used to read machine resources, such as TMEM, should be revised? Nodes with problems to read machine resources present side effects. For example, mm_shed do not deploy submitted VMs to nodes with TMEM=0. Best regards, Erico.
_______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org