[one-users] Problems using allocateFromTemplate(Client client, int templateId) java OCA

[Sajith Kalathingal]

The problem is that xmlrpc call with TEMPLATE_ID = is not working properly.


________________________________
 From: Sajith Kalathingal <sajith.kalathingal at yahoo.in>
To: Opennebula <users at lists.opennebula.org> 
Sent: Thursday, 9 February 2012 5:53 PM
Subject: Problems using allocateFromTemplate(Client client, int templateId) java OCA
 

Hi,

I'm trying to allocate virtual machines using the following statement

allocateFromTemplate(Client client, int templateId). While doing this VM goes from pending->boot->fail.

There is nothing interesting on oned.log or OneResponse. 

However individual VM log shows 


Thu Feb  9 12:36:28 2012 [DiM][I]: New VM state is ACTIVE.
Thu Feb  9 12:36:28 2012 [LCM][I]: New VM state is PROLOG.
Thu Feb  9 12:36:28 2012 [VM][I]: Virtual Machine has no context
Thu Feb  9 12:36:28 2012 [LCM][I]: New VM state is BOOT
Thu Feb  9 12:36:28 2012 [VMM][I]: Generating deployment file: /var/lib/one/54/deployment.0
Thu Feb  9 12:36:28 2012 [VMM][E]: No MEMORY
 defined and no default provided.
Thu Feb  9 12:36:28 2012 [VMM][E]: deploy_action, error generating deployment file: /var/lib/one/54/deployment.0
Thu Feb  9 12:36:28 2012 [DiM][I]: New VM state is FAILED



The template which I used is 


NAME   = ttylinux
CPU    = 1
MEMORY = 450
PATH   = /var/lib/one/public/ttylinux.img

OS = [ KERNEL     = /vmlinuz,
       INITRD     = /initrd.img,
       ROOT       = sda1,
       KERNEL_CMD = "ro xencons=tty console=tty1"]

DISK   = [
  source   = "/var/lib/one/public/ttylinux.img",
  target   = "hda",
  readonly = "no" ]

NIC    = [
 NETWORK = "Small network1" ]

FEATURES=[ acpi="no" ]



I tried the same template with : onetemplate instantiate `templateid` and it is working fine. 


I am using Opennebula 3.2.1.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20120209/08b8c8da/attachment-0002.htm>