Monitoring takes a bit to get information on the VM consumption form the hypervisor. It is not strange that it takes a minute or so after the VM goes to "runn" state. If after a couple of minutes the VM is still showing 0 in memory consumption can you check that there are not monitoring errors in the log files?
On Tue, Mar 29, 2011 at 4:15 PM, Madhurranjan Mohaan <[email protected]> wrote: > Hello Steven, > > That was a great point. I found the error in the libvirt log for that Vm. > The vnc host was started but on a port that was already listening so the VM > had crashed. Followed by that I recreated the vm-template file with a > different port and its up now. Virsh list shows it up but onevm shows it in > the unknown state . Memory is still 0 . > > Followed by that i deployed the ttylinux image as well that comes by > default. Again that shows 0K memory. Unable to figure out the reason. > > thanks > > Ranjan > > > > On Tue, Mar 29, 2011 at 7:17 PM, Steven Timm <[email protected]> wrote: >> >> If virsh list doesn't show anything that means that the >> VM crashed soon after boot on the VM host. Look at the libvirt >> logs on the VM host. If you have access to virt-manager >> or some other way to see a vm console, try to do a onevm restart <vmid> >> and see if you can get the console up fast enough to see where it died. >> >> Steve Timm >> >> >> On Tue, 29 Mar 2011, Madhurranjan Mohaan wrote: >> >>> Hello Steven, >>> >>> Thanks for your quick response. >>> >>> 1. The nnn.log of the VM , shows me this : It doesn't show me 0 anywhere >>> here. >>> >>> >>> Tue Mar 29 17:54:58 2011 [TM][I]: tm_clone.sh: DST: >>> /srv/cloud/one/var/58/images/disk.0 >>> Tue Mar 29 17:54:58 2011 [TM][I]: tm_clone.sh: Creating directory >>> /srv/cloud/one/var/58/images >>> Tue Mar 29 17:54:59 2011 [TM][I]: tm_clone.sh: Executed "mkdir -p >>> /srv/cloud/one/var/58/images". >>> Tue Mar 29 17:54:59 2011 [TM][I]: tm_clone.sh: Executed "chmod a+w >>> /srv/cloud/one/var/58/images". >>> Tue Mar 29 17:55:00 2011 [TM][I]: tm_clone.sh: Cloning >>> /srv/cloud/one/fr.iso >>> Tue Mar 29 17:55:00 2011 [TM][I]: tm_clone.sh: Executed "cp -r >>> /srv/cloud/one/fr.iso >>> /srv/cloud/one/var/58/images/disk.0" . >>> Tue Mar 29 17:55:00 2011 [TM][I]: tm_clone.sh: Executed "chmod a+rw >>> /srv/cloud/one/var/58/images/disk.0". >>> Tue Mar 29 17:55:03 2011 [TM][I]: tm_mkimage.sh: Executed "mkdir -p >>> /srv/cloud/one/var/58/images". >>> Tue Mar 29 17:55:03 2011 [TM][I]: tm_mkimage.sh: Executed "/bin/dd >>> if=/dev/zero of=/srv/cloud/one/var/58/images/disk.1 bs >>> =1 count=1 seek=4096M". >>> Tue Mar 29 17:55:03 2011 [TM][I]: tm_mkimage.sh: Executed "/sbin/mkfs -t >>> ext3 -F /srv/cloud/one/var/58/images/disk.1". >>> Tue Mar 29 17:55:03 2011 [TM][I]: tm_mkimage.sh: Executed "chmod a+rw >>> /srv/cloud/one/var/58/images/disk.1". >>> Tue Mar 29 17:55:03 2011 [TM][I]: tm_context.sh: Executed "mkdir -p >>> /srv/cloud/one/var/58/images/isofiles". >>> Tue Mar 29 17:55:03 2011 [TM][I]: tm_context.sh: Executed "cp -R >>> /srv/cloud/one/var/58/context.sh /srv/cloud/one/var/58/i >>> mages/isofiles". >>> Tue Mar 29 17:55:03 2011 [TM][I]: tm_context.sh: Executed "cp -R >>> /srv/cloud/one/vm-template-2/init.sh /srv/cloud/one/var/ >>> 58/images/isofiles". >>> Tue Mar 29 17:55:03 2011 [TM][I]: tm_context.sh: Executed >>> "/usr/bin/mkisofs >>> -o /srv/cloud/one/var/58/images/disk.2 -J -R >>> /srv/cloud/one/var/58/images/isofiles". >>> Tue Mar 29 17:55:03 2011 [TM][I]: tm_context.sh: Executed "rm -rf >>> /srv/cloud/one/var/58/images/isofiles". >>> Tue Mar 29 17:55:04 2011 [LCM][I]: New VM state is BOOT >>> *Tue Mar 29 17:55:04 2011 [VMM][I]: Generating deployment file: >>> /srv/cloud/one/var/58/deployment.0 >>> Tue Mar 29 17:55:35 2011 [LCM][I]: New VM state is RUNNING >>> Tue Mar 29 18:05:45 2011 [VMM][I]: VM running but it was not found. >>> Restart >>> and delete actions available or try to recove r it >>> manually >>> Tue Mar 29 18:05:45 2011 [LCM][I]: New VM state is UNKNOWN >>> Tue Mar 29 18:15:45 2011 [VMM][I]: VM running but it was not found. >>> Restart >>> and delete actions available or try to recove r it >>> manually >>> Tue Mar 29 18:15:45 2011 [LCM][I]: New VM state is UNKNOWN >>> Tue Mar 29 18:25:45 2011 [VMM][I]: VM running but it was not found. >>> Restart >>> and delete actions available or try to recove r it >>> manually >>> ** >>> 2. *Around the same time i can't see anything significant in oned.log . >>> >>> Tue Mar 29 18:05:30 2011 [InM][I]: Monitoring host server123(0) >>> Tue Mar 29 18:05:31 2011 [ReM][D]: HostPoolInfo method invoked >>> Tue Mar 29 18:05:31 2011 [ReM][D]: VirtualMachinePoolInfo method invoked >>> Tue Mar 29 18:05:33 2011 [InM][D]: Host 0 successfully monitored. >>> Tue Mar 29 18:05:34 2011 [ReM][D]: HostPoolInfo method invoked >>> Tue Mar 29 18:05:34 2011 [ReM][D]: VirtualMachinePoolInfo method invoked >>> Tue Mar 29 18:07:10 2011 [ReM][D]: HostPoolInfo method invoked >>> Tue Mar 29 18:07:10 2011 [ReM][D]: VirtualMachinePoolInfo method invoked >>> Tue Mar 29 18:05:41 2011 [ReM][D]: HostPoolInfo method invoked >>> Tue Mar 29 18:05:41 2011 [ReM][D]: HostPoolInfo method invoked >>> Tue Mar 29 18:05:41 2011 [ReM][D]: VirtualMachinePoolInfo method invoked >>> Tue Mar 29 18:05:41 2011 [ReM][D]: VirtualMachinePoolInfo method invoked >>> >>> *3. virsh list doesn't show me any VM that is running on that host. * >>> >>> Thoughts ? >>> Ranjan >>> >>> >>> On Tue, Mar 29, 2011 at 6:50 PM, Steven Timm <[email protected]> wrote: >>> >>>> Look at your oned.log and at the nnn.log which is the log of >>>> the virtual machine number in question. Probably it first shows zero >>>> and then goes to unknown because something is failing in >>>> one of the monitoring scripts so it can't monitor. The logs should say. >>>> >>>> Did you note which host the VM is running on? does virsh list on >>>> that host show that it is still running? >>>> >>>> Steve Timm >>>> >>>> >>>> >>>> On Tue, 29 Mar 2011, Madhurranjan Mohaan wrote: >>>> >>>> Hi All, >>>>> >>>>> There is enough Ram on my machine but somehow apart from the default >>>>> "ttylinux" image, any other image I create with memory value specified >>>>> in >>>>> the *vm-template.one* file results in generating the VM but the memory >>>>> column always shows 0K. After a while , the VM goes from running to >>>>> unknown >>>>> . I can't see any error message . This is on Centos 5.5 and I am using >>>>> kvm >>>>> as the hypervisor. >>>>> >>>>> onevm list >>>>> >>>>> 22 oneadmin ttylinux runn 0 64M machine.th 05 01:56:35 >>>>> 56 oneadmin vm *runn *0 *0K* machine.th 00 00:00:56 >>>>> >>>>> Any suggestions ? >>>>> >>>>> thanks >>>>> >>>>> Ranjan >>>>> >>>>> >>>> -- >>>> ------------------------------------------------------------------ >>>> Steven C. Timm, Ph.D (630) 840-8525 >>>> [email protected] http://home.fnal.gov/~timm/ >>>> Fermilab Computing Division, Scientific Computing Facilities, >>>> Grid Facilities Department, FermiGrid Services Group, Group Leader. >>>> Lead of FermiCloud project. >>>> >>> >> >> -- >> ------------------------------------------------------------------ >> Steven C. Timm, Ph.D (630) 840-8525 >> [email protected] http://home.fnal.gov/~timm/ >> Fermilab Computing Division, Scientific Computing Facilities, >> Grid Facilities Department, FermiGrid Services Group, Group Leader. >> Lead of FermiCloud project. > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > > -- Javier Fontan, Grid & Virtualization Technology Engineer/Researcher DSA Research Group: http://dsa-research.org Globus GridWay Metascheduler: http://www.GridWay.org OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org _______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
