[one-users] 答复: re: Failed to create VM.(KVM)

[Sam Song]

Hi vishnu,

 

I’m not sure how did you create it, but some parameters are not correct.

Please recreate a vm template according to [1] and have a try again.

This is an example template I created using sunstone, for your reference,but you could not use it directly(NETWORK and IMAGE which it used may not exist in your environment.

 

NAME=”ttylinux”

NIC=[NETWORK_ID="0"]

CPU="1"

CONTEXT=[SSH_PUBLIC_KEY="$USER[SSH_PUBLIC_KEY]",NETWORK="YES"]

DISK=[IMAGE_ID="0"]

GRAPHICS=[LISTEN="0.0.0.0",TYPE="VNC"]

MEMORY="512"

 

Good luck.

 

[1] http://opennebula.org/documentation:rel4.2:vm_guide

 

Sam

 

发件人: vishnu e divakaran [mailto:vishnued at gmail.com] 
发送时间: 2013年11月20日 23:09
收件人: Sam Song
主题: Re: re: [one-users] Failed to create VM.(KVM)

 

VM Template file
-----------------------------------------------------------------------------------
NAME   = ttylinux
PATH   = /var/tmp/ttylinux.img
CPU    = 0.1
MEMORY = 256
TYPE="OS"
DISK   = [
  source   = "/var/tmp/ttylinux.img",
  target   = "hda",
  type     = "swap",
  readonly = "no" ]

NIC    = [ NETWORK = "Small network" ]

FEATURES=[ acpi="no" ]

CONTEXT = [
    hostname    = "onevmhost",
    ip_public   = "192.168.1.15",
    files      = "/var/lib/one/vis/init.sh ~/.ssh/id_rsa.pub",
    target      = "hdc",
    root_pubkey = "id_rsa.pub",
    username    = "oneadmin",
    user_pubkey = "id_rsa.pub"
]

 

On 18 November 2013 06:24, Sam Song <samsong8610 at gmail.com> wrote:

Hi vishnu,

Which ds_mad and tm_mad do you use for the system datastore and image datastore separately?
Could you provide your vm template?

Regards

Sam

-----邮件原件-----
发件人: vishnu e divakaran [mailto:vishnued at gmail.com]
发送时间: 2013年11月17日 0:58
收件人: Sam Song
主题: Re: 答复: [one-users] Failed to create VM.(KVM)


Yes disk.0 is not exist there,but disk.1 is there.

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20131121/5ef88689/attachment-0002.htm>