Quoting Daniel Molina (dmol...@opennebula.org): > Could you try removing the m1.small|large|... empty fields or setting them > to 0?
That helps :). I was able to reproduce the issue with a "KEYPAIR" with a "white space", i.e. "key space" in a EC2 VM template: Mon Mar 31 21:46:59 2014 [VMM][E]: Error parsing monitoring information: USEDMEMORY=0 USEDCPU=0 NETTX=0 NETRX=0 STATE=a AWS_DNS_NAME=ec2-54-72-149-220.eu-west-1.compute.amazonaws.com AWS_PRIVATE_DNS_NAME=ip-172-31-21-87.eu-west-1.compute.internal AWS_KEY_NAME=key space AWS_AVAILABILITY_ZONE=eu-west-1c AWS_VPC_ID=vpc-7ef7b615 AWS_PRIVATE_IP_ADDRESS=172.31.21.87 AWS_IP_ADDRESS=54.72.149.220 AWS_SUBNET_ID=subnet-7cf7b617 AWS_SECURITY_GROUPS=sg-1a5bb275 AWS_INSTANCE_TYPE=t1.micro If I use a KEYPAIR without space(s) it it able to monitor correctly: [VMM][D]: VM $ONE_ID successfully monitored: I created issues #2820 and #2821. Gr. Stefan -- | BIT BV http://www.bit.nl/ Kamer van Koophandel 09090351 | GPG: 0xD14839C6 +31 318 648 688 / i...@bit.nl _______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org