Re: [one-users] Incomplete information from hosts polling (VMWare ESXi 4.1 an OpenNebula 2.0.1)

[Luigi Fortunati]

On Fri, Feb 4, 2011 at 10:35 AM, Luigi Fortunati
wrote:

> To Siva:
> As far as I know you can connect to the ESXi Server in three ways:
>
> libvirt and virsh (the way of OpenNebula-VMWare Driver):
> The VMWare Driver of OpenNebula uses virsh commands (which relies on
> libvirt) to access some hypervisor functionalities. You can use directly
> virsh commands to test what libvirt is capable of by using this command:
> virsh -c esx://[@]/?no_verify=1
> Then you'll get a password prompt.
> you can use "root" as user. no_verify=1 disables check on certificates.
> You can find other useful infos here: http://libvirt.org/drvesx.html
>
> If OpenNebula can't connect you'll probably notice some error messages on
> the logs.
> Take a look in var/oned.log and var//vm.log and post the errors,
> otherwise check the installation steps in the VMWare Driver section of the
> documentation.
> I remember that you have to configure a username and password in a file in
> order to let OpenNebula connect to hypervisors through virsh.
>
> VMWare API (vSphere Client):
> ESXi hosts come with a public API developed by VMWare for accessing
> hypervisor functionalities:
> http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/
> I think that libvirt actually uses ver. 2.5 of those APIs.
> vSphere Client most probably connects to the hypervisor using those API
> (probably the latest version of the latter).
>
> Shell:
> You have to enable access to the shell through VSphere Client.
> As far as I know it is only possible to make ssh access with the root
> credentials, even if you created other users and modified /etc/passwd file
> to set a shell for the user.
>
> On Fri, Feb 4, 2011 at 7:33 AM, Siva Prasad wrote:
>
>> Hi
>>
>> Can you please let me know how are you able to connect to ESXI Server.I
>> tried the same but got the error "connection refused".
>>
>> Please let me know the detail steps.
>>
>> Thanks,
>> Siva
>>
>> On Thu, Feb 3, 2011 at 9:40 PM, Luigi Fortunati <
>> luigi.fortun...@gmail.com> wrote:
>>
>>> Hi,
>>> I noticed a serious problem about the usage of VMWare ESXi 4.1 and
>>> OpenNebula 2.0.1.
>>> I'm actually using the VMWare driver addon which can be found on the
>>> opennebula website (ver. 1.0) and libvirt (ver. 0.8.7).
>>> It happens that OpenNebula can't get information about the usage of
>>> resources on the cluster nodes.
>>> By running 2 VM (each one requires 2 VCPU and 1 GB of memory) and
>>> executing some commands I get this output.
>>>
>>>  oneadmin@custom2:~/src$ onehost list
>>>   ID NAME  CLUSTER  RVM   TCPU   FCPU   ACPUTMEMFMEM
>>> STAT
>>>2 custom7.sns.itdefault0200200200  2G  0K
>>>  off
>>>1 custom6.sns.itdefault2200200200  2G  0K
>>>   on
>>> oneadmin@custom2:~/src$ onehost show 1
>>> HOST 1 INFORMATION
>>>
>>> ID: 1
>>> NAME  : custom6.sns.it
>>> CLUSTER   : default
>>> STATE : MONITORED
>>> IM_MAD: im_vmware
>>> VM_MAD: vmm_vmware
>>> TM_MAD: tm_vmware
>>>
>>> HOST SHARES
>>>
>>> MAX MEM   : 2096460
>>> USED MEM (REAL)   : 0
>>> USED MEM (ALLOCATED)  : 0
>>> MAX CPU   : 200
>>> USED CPU (REAL)   : 0
>>> USED CPU (ALLOCATED)  : 0
>>> RUNNING VMS   : 2
>>>
>>> MONITORING INFORMATION
>>>
>>> CPUSPEED=1992
>>> HYPERVISOR=vmware
>>> TOTALCPU=200
>>> TOTALMEMORY=2096460
>>>
>>> As you can see OpenNebula is unable to get correct information about the
>>> usage of resources on the cluster nodes.
>>> As these informations are used by the VM scheduler, OpenNebula is unable
>>> to schedule the VM correctly.
>>> I tried to create several VM and all of them were placed on the same host
>>> even if the latter was unable to satisfy the resource requirements of all
>>> the VMs.
>>> I think that this problem is strongly related to libvirt as OpenNebula
>>> use it to recover information about hosts and vm.
>>>
>>> Do you get the same behavior? Do you know if there is a way to solve this
>>> big issue?
>>>
>>> --
>>> Luigi Fortunati
>>>
>>> ___
>>> Users mailing list
>>> Users@lists.opennebula.org
>>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>>
>>>
>>
>
>
> --
> Luigi Fortunati
>



-- 
Luigi Fortunati
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] Incomplete information from hosts polling (VMWare ESXi 4.1 an OpenNebula 2.0.1)

[Luigi Fortunati]

I can post the VM template content on monday. However, as far as I remember,
the vm template was really simple:
NAME="Debian"
VCPU= 2
MEMORY=1024
DISK=[IMAGE="Debian5-i386"]
OS=[ARCH=i686]

The VMs can boot and run, I can log on console through vSphere Client on the
newly created VMs.

I noticed that if you don't declare the number on VCPU the VM doesn't get
scheduled on a cluster node. This option seems mandatory but I didn't find
any mention about it on the documentation.
Another thing that seems mandatory is declaring the cpu architecture as
i686, otherwise OpenNebula will return error when writing the deployment.0
file.


On Thu, Feb 3, 2011 at 5:42 PM, Ruben S. Montero wrote:

> Hi,
>
> I am not sure this is related to the VMware monitoring... Can you send the
> VM Templates?
>
> Thanks
>
> Ruben
>
> On Thu, Feb 3, 2011 at 5:10 PM, Luigi Fortunati  > wrote:
>
>> Hi,
>> I noticed a serious problem about the usage of VMWare ESXi 4.1 and
>> OpenNebula 2.0.1.
>> I'm actually using the VMWare driver addon which can be found on the
>> opennebula website (ver. 1.0) and libvirt (ver. 0.8.7).
>> It happens that OpenNebula can't get information about the usage of
>> resources on the cluster nodes.
>> By running 2 VM (each one requires 2 VCPU and 1 GB of memory) and
>> executing some commands I get this output.
>>
>> oneadmin@custom2:~/src$ onehost list
>>   ID NAME  CLUSTER  RVM   TCPU   FCPU   ACPUTMEMFMEM
>> STAT
>>2 custom7.sns.itdefault0200200200  2G  0K
>>  off
>>1 custom6.sns.itdefault2200200200  2G  0K
>>   on
>> oneadmin@custom2:~/src$ onehost show 1
>> HOST 1 INFORMATION
>>
>> ID: 1
>> NAME  : custom6.sns.it
>> CLUSTER   : default
>> STATE : MONITORED
>> IM_MAD: im_vmware
>> VM_MAD: vmm_vmware
>> TM_MAD: tm_vmware
>>
>> HOST SHARES
>>
>> MAX MEM   : 2096460
>> USED MEM (REAL)   : 0
>> USED MEM (ALLOCATED)  : 0
>> MAX CPU   : 200
>> USED CPU (REAL)   : 0
>> USED CPU (ALLOCATED)  : 0
>> RUNNING VMS   : 2
>>
>> MONITORING INFORMATION
>>
>> CPUSPEED=1992
>> HYPERVISOR=vmware
>> TOTALCPU=200
>> TOTALMEMORY=2096460
>>
>> As you can see OpenNebula is unable to get correct information about the
>> usage of resources on the cluster nodes.
>> As these informations are used by the VM scheduler, OpenNebula is unable
>> to schedule the VM correctly.
>> I tried to create several VM and all of them were placed on the same host
>> even if the latter was unable to satisfy the resource requirements of all
>> the VMs.
>> I think that this problem is strongly related to libvirt as OpenNebula use
>> it to recover information about hosts and vm.
>>
>> Do you get the same behavior? Do you know if there is a way to solve this
>> big issue?
>>
>> --
>> Luigi Fortunati
>>
>> ___
>> Users mailing list
>> Users@lists.opennebula.org
>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>
>>
>
>
> --
> Dr. Ruben Santiago Montero
> Associate Professor (Profesor Titular), Complutense University of Madrid
>
> URL: http://dsa-research.org/doku.php?id=people:ruben
> Weblog: http://blog.dsa-research.org/?author=7
>



-- 
Luigi Fortunati
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] Connection refused error while adding the host through onehost create

[Tino Vazquez]

Hi Siva,

It doesn't look like a problem with the hypervisor, but rather a connection one.

Could you check that you can ping and telnet (443) "myremotehost" from
the OpenNebula front-end?

Regards,

-Tino

--
Constantino Vázquez Blanco | dsa-research.org/tinova
Virtualization Technology Engineer / Researcher
OpenNebula Toolkit | opennebula.org



On Thu, Feb 3, 2011 at 3:58 PM, Siva Prasad  wrote:
> I get Connection refused error when adding  host using onehost command.
>
> The following are the detailed steps I have done.This is little in detail .
>
> I have installed opennebula2.0.1
>
> The Hypervisor I am trying to connect is ESXI4.1.0.
>
> I am able to connect to the ESXI successyfully with the oneadmin
> (password=test123)
>
> I have generated the keys using openssl and signed them using certtool.
>
> I have generated following keys using openssl.I have generated all the below
> keys using the same pass (test123)
>
>    1)   cakey.pem
>     2)  myremotehostkey.pem ( the machine where ESXI4.10 is installed ), I
> could connect to this from my desktop using the oneadmin.
>     3)  clientkey.pem(The machine where openNebula is installed)
>
> I have self signed the cakey.pem using the certtool
>   (certtool --generate-self-signed --load-privkey cakey.pem
> --template ca.info --outfile cacert.pem)
> Now I have generated the cert for myremotehost using the command
>  "certtool --generate-certificate --load-privkey
> myremotehostkey.pem   --load-ca-certificate cacert.pem --load-ca-privkey
> cakey.pem   --template server.info --outfile myremotehostcert.pem"  ( In the
> server.info file I have given CN as myremotehost)
> I have generated the clientcert using the following command
>   "certtool --generate-certificate --load-privkey clientkey.pem
> --load-ca-certificate cacert.pem --load-ca-privkey cakey.pem  --template
> client.info --outfile clientcert.pem"
>
> Now I have placed the certificates and keys  in the following locations
>
> cacert.pem  in   /etc/pki/CA ( in the machine where opennebula is
> installed).
> myremotehostkey.pem in  /etc/pki/libvirt/private
> myremotehostcert.pem in /etc/pki/libvirt
>
>  restarted the oned and now added the host using onehost create myremotehost
> im_vmware vmm_vmware tm_vmware
>
> I get the following error in the oned.log
>
>
>  ERROR =
>
>
> Thu Feb  3 20:01:48 2011 [InM][E]: Error monitoring host 7 : MONITOR FAILURE
> 7 Could not monitor host myremotehost.
> Thu Feb  3 20:11:03 2011 [VMM][I]: --Mark--
> Thu Feb  3 20:11:03 2011 [InM][I]: --Mark--
> Thu Feb  3 20:11:48 2011 [InM][I]: Monitoring host myremotehost (7)
> Thu Feb  3 20:11:48 2011 [InM][I]: Command execution fail:
> /root/one2/lib/remotes/im/run_probes vmware myremotehost
> Thu Feb  3 20:11:48 2011 [InM][I]: STDERR follows.
> Thu Feb  3 20:11:48 2011 [InM][I]: [VMWARE] cmd failed
> [/root/one2/bin/tty_expect -u oneadmin -p test123 virsh -c
> esx://myremotehost?no_verify=1 --readonly nodeinfo]. Stderr:  Connection
> refused
> Thu Feb  3 20:11:48 2011 [InM][I]: error: failed to connect to the
> hypervisor
> Thu Feb  3 20:11:48 2011 [InM][I]: error: no valid connection
> Thu Feb  3 20:11:48 2011 [InM][I]: oneadmin
> Thu Feb  3 20:11:48 2011 [InM][I]: test123
> Thu Feb  3 20:11:48 2011 [InM][I]:
> Thu Feb  3 20:11:48 2011 [InM][I]: . Stdout: ExitCode: 1
> Thu Feb  3 20:11:48 2011 [InM][I]: ./vmware.rb:47: private method `split'
> called for 1:Fixnum (NoMethodError)
>
> =
>
> I get the same above error if I try to connect to virsh prompt from command
> line.(root/one2/lib/remotes/im/run_probes vmware myremotehost
> )
>
> Now my queries are the the locations of myremotehostcert.pem and
> myremotehostkey.pem are correct?
> Where should I place clientcert and clientkey pem files.?
> Is the way I am generating the certificates right? ( I hope they are right
> because it did not give any error while signing)
>
> Please let me know if I have to do anythign else  OR  If I am doing anything
> wrong.
>
>
> Appreciate your help in solving the problem.
>
> thanks,
> Siva
>
> ___
> Users mailing list
> Users@lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] serial console on KVM domains

[Tino Vazquez]

Hi Steven,

You can achieve that using the RAW attribute. Please see the last bit of [1].

Regards,

-Tino

[1] http://www.opennebula.org/documentation:rel2.0:kvmg

--
Constantino Vázquez Blanco | dsa-research.org/tinova
Virtualization Technology Engineer / Researcher
OpenNebula Toolkit | opennebula.org



On Thu, Feb 3, 2011 at 7:31 PM, Steven Timm  wrote:
>
> Is there any template option that can be added to
> the opennebula  VM template for a KVM domain such that it
> will be able to attach to the serial console via virsh console?
> For Xen this already works and there is nothing that has
> to be specified.
>
> In static KVM (non-cloud) installations we have this in
> our libvirt XML
>
>    
>      
>    
>
> What's the OpenNebula equivalent to make this happen?
>
> Steve timm
>
>
> --
> --
> Steven C. Timm, Ph.D  (630) 840-8525
> t...@fnal.gov  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
> Users@lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

[one-users] ONE with Xen and LVM

[anoop Lekshmanan]

Hi All,

I have setup ONE 2.0.1 with Xen node, everything is working fine except
loading an image to LVM on node. Have you ever tried that?

It would be great if you can share an example VM template/ intial steps to
do the VM Instance launch with Xen/KVM with TM_LVM.


Thanks,
Anoop
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

[one-users] passwordless ssh between onehosts

[Steffen Neumann]

Hi, 

how is the passwordless ssh supposed to work ?

I can ssh from head -> any node just fine,
but "onevm migrate" requires passwordless ssh from node01 -> node02
so oneadmin@node01's id_rsa_pub needs to be in oneadmin@node02's
authorized keys.

This will explode with the number of hosts involved. 

Or did I miss something simpler ? Is that already handled ?
Is the id_rsa_pub (supposed to be) the same on all hosts ?

Yours,
Steffen


-- 
IPB HalleAG Massenspektrometrie & Bioinformatik
Dr. Steffen Neumann  http://www.IPB-Halle.DE
Weinberg 3   http://msbi.bic-gh.de
06120 Halle  Tel. +49 (0) 345 5582 - 1470
  +49 (0) 345 5582 - 0
sneumann(at)IPB-Halle.DE Fax. +49 (0) 345 5582 - 1409

___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] Writing one template that allows for persistent VM:

[Carlos Martín Sánchez]

Hi Steven,

On 4 February 2011 05:22, Steven Timm  wrote:

> hOn Thu, 3 Feb 2011, Steven Timm wrote:
>
>
>> I am trying to come up with a prescription for users that allows the
>> following sequence:
>>
>> 1) Launch a VM based on a standard VM repository template
>>
>> 2) Save the contents of the VM back to the VM repositor\
>>
>> 3) Relaunch the VM without modifying the template.
>>
>> I've tried the following thus far:
>>
>> 1) Launch the VM initially from a VM OS file outside the VM repository
>> with save=yes.  this does save the VM OS but just to
>> /var/lib/one//disk.0, not back to the original file.
>> User must copy that file somewhere and/or change their template.
>>
>> 1a) Launch the VM and then execute a onevm saveas command.
>>   this gets a copy of the image back to the image repository
>>   but again user must modify the template to relaunch the VM.
>>
>> 2) Make a public VM image in the repository, launch from that.
>> Problems--even if image is public, other users (even oneadmin) can't read
>> it and sometimes I myself can't read it, without going into
>> the image repo and chmod'ing the file by hand.  And again
>> you are forced to save back to something other than the original file.
>>
>> 3) Make a persistent non-public image in the repository.
>> Again there are permission problems launching, and it can only
>> be used once by one user.  Even so I can't get it to save back to the
>> repository.
>>
>>  If the user makes and saves the persistent non-public image
> in the repository, it is then necessary to go in and
> change the permissions on the file in the repository, otherwise
> the oneadmin user can't read it.  But once this is done,
> it is possible to start the VM from the repository and save it
> back to the same place in the repository when it is done.
>
>
When OpenNebula is installed, the images directory is set up with the sticky
bit. From install.sh:
chmod 3770 $DESTDIR$IMAGES_LOCATION

In [1], it says


"The IMAGE_REPOSITORY_PATH can be changed to another administrator defined
folder. This folder will need to be created with special permissions to
ensure its consistency. It will need full permissions for writting new files
for any user, and:

* the sticky bit, so other users are allowed to read other user files, but
aren't allowed to erase them
* the setgid, so all the files copied to the image repository end up with
oneadmin group

This can be achieved with “chmod 3770 /path/to/image/repository/”."


If you changed the images path, or if for some reason you deleted the var
directory, you'll need to recreate the sticky bit configuration.
In order to let other users register images, you have to either let anyone
write in the images path, or add all your OpenNebula regular users to
oneadmin's group.

Could you please check your configuration? If you continue having troubles,
please send us your installation directory permissions.


> Next step--to make a public non-persistent generic image
> in the repo, and then have a "clone" function such that
> a user can make a non-public persistent image from it and
> fork off their VM and save it from there on.  Anyone else interested?
>
>
What's your goal? to control it somehow in the VM template, or rather create
a new command such as:
oneimage clone "Original_public_image" "My_private_copy" ?



> Steve Timm
>
>
>
>
Best regards,
Carlos.

[1] http://opennebula.org/documentation:rel2.0:oned_conf#image_repository

Carlos Martín, Cloud Technology Engineer/Researcher
DSA Research Group: web http://dsa-research.org and blog
http://blog.dsa-research.org
OpenNebula Open Source Toolkit for Cloud Computing:
http://www.OpenNebula.org 



>
>
>  Everything that we need to do is doable, but it takes hacking around
>> with the template every time to be able to launch where we
>> left off.  We need a way to make things more seamless.
>>
>> Steve Timm
>>
>>
>>
>>
>>
> --
> --
> Steven C. Timm, Ph.D  (630) 840-8525
> t...@fnal.gov  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
> Users@lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] Writing one template that allows for persistent VM:

[Steven Timm]

When OpenNebula is installed, the images directory is set up with the sticky
bit. From install.sh:
chmod 3770 $DESTDIR$IMAGES_LOCATION

In [1], it says


"The IMAGE_REPOSITORY_PATH can be changed to another administrator defined
folder. This folder will need to be created with special permissions to
ensure its consistency. It will need full permissions for writting new files
for any user, and:

* the sticky bit, so other users are allowed to read other user files, but
aren't allowed to erase them
* the setgid, so all the files copied to the image repository end up with
oneadmin group

This can be achieved with ?chmod 3770 /path/to/image/repository/?."


If you changed the images path, or if for some reason you deleted the var
directory, you'll need to recreate the sticky bit configuration.
In order to let other users register images, you have to either let anyone
write in the images path, or add all your OpenNebula regular users to
oneadmin's group.

Could you please check your configuration? If you continue having troubles,
please send us your installation directory permissions.



We did change the images path. I added the 3770 permissions to this path
and now oneadmin can launch my private persistent image and different 
users can launch public images.




Next step--to make a public non-persistent generic image
in the repo, and then have a "clone" function such that
a user can make a non-public persistent image from it and
fork off their VM and save it from there on.  Anyone else interested?



What's your goal? to control it somehow in the VM template, or rather create
a new command such as:
oneimage clone "Original_public_image" "My_private_copy" ?



It would be nice to have a "oneimage clone" feature.  that way
the user is not forced to make one template for the first time
to read from the public copy and save to his private copy.

Steve Timm






Steve Timm





Best regards,
Carlos.

[1] http://opennebula.org/documentation:rel2.0:oned_conf#image_repository

Carlos Martín, Cloud Technology Engineer/Researcher
DSA Research Group: web http://dsa-research.org and blog
http://blog.dsa-research.org
OpenNebula Open Source Toolkit for Cloud Computing:
http://www.OpenNebula.org 






 Everything that we need to do is doable, but it takes hacking around

with the template every time to be able to launch where we
left off.  We need a way to make things more seamless.

Steve Timm






--
--
Steven C. Timm, Ph.D  (630) 840-8525
t...@fnal.gov  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
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org





--
--
Steven C. Timm, Ph.D  (630) 840-8525
t...@fnal.gov  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
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] passwordless ssh between onehosts

[Olivier Sallou]

if your oneadmin homedir is mounted, all you need is to put each host 
key on authorized keys, no exponential combination.


Indeed, this is quite hard to manage if you use a local homedir for each 
host.


Olivier

Le 2/4/11 3:22 PM, Steffen Neumann a écrit :

Hi,

how is the passwordless ssh supposed to work ?

I can ssh from head ->  any node just fine,
but "onevm migrate" requires passwordless ssh from node01 ->  node02
so oneadmin@node01's id_rsa_pub needs to be in oneadmin@node02's
authorized keys.

This will explode with the number of hosts involved.

Or did I miss something simpler ? Is that already handled ?
Is the id_rsa_pub (supposed to be) the same on all hosts ?

Yours,
Steffen




--
gpg key id: 4096R/326D8438  (pgp.mit.edu)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438


___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] onevnet range network handing without range

[Ruben S. Montero]

Hi

A Ranged Network is a contiguous range of IPs (any number of IPs) class
networks can be defined for convenience, though.  however you can specify
any size. eg.
...
NETWORK = 10.20.0.10
SIZE = 240
...

This will produce the range you are looking for...


Cheers


On Fri, Feb 4, 2011 at 12:13 AM, Steffen Neumann wrote:

> Hi,
>
> from my old days I know about class A,B and C networks.
> That definition is also used in the TYPE = RANGED
> network definition. I see two problems there:
>
> 1) People might have different networks,
>   e.g. e.g. a 192.168.0.0/23 with addresses
>   from approx. 192.168.0.1 to 192.168.1.254
>
>   the onevnet definition should be as flexible.
>
> 2) In my 10.20.0.0/16 network, I want to have the
>   physical hosts on 10.20.0.x and virtual machines
>   on 10.20.1.y, essentially sharing the same subnet.
>
>   onevnet is defined as class B 10.20.0.0,
>   but it will happily provide a lease colliding
>   with my (dhcp-assigned) physical hosts.
>
>   The onevnet RANGE definition should allow a real range,
>   similar to dnsmask's dhcp-range=10.20.0.10,10.20.0.250,1h
>
> Or did I miss anything ?
>
> Yours,
> Steffen
>
>
> --
> IPB HalleAG Massenspektrometrie & Bioinformatik
> Dr. Steffen Neumann  http://www.IPB-Halle.DE
> Weinberg 3   http://msbi.bic-gh.de
> 06120 Halle  Tel. +49 (0) 345 5582 - 1470
>  +49 (0) 345 5582 - 0
> sneumann(at)IPB-Halle.DE Fax. +49 (0) 345 5582 - 1409
>
> ___
> Users mailing list
> Users@lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>



-- 
Dr. Ruben Santiago Montero
Associate Professor (Profesor Titular), Complutense University of Madrid

URL: http://dsa-research.org/doku.php?id=people:ruben
Weblog: http://blog.dsa-research.org/?author=7
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] onevnet range network handing without range

[Ruben S. Montero]

Just forgot to mention that sizes and starting address must conform a CIDR
notation... (if not OPenNebula will round them)

On Fri, Feb 4, 2011 at 5:14 PM, Ruben S. Montero wrote:

> Hi
>
> A Ranged Network is a contiguous range of IPs (any number of IPs) class
> networks can be defined for convenience, though.  however you can specify
> any size. eg.
> ...
> NETWORK = 10.20.0.10
> SIZE = 240
> ...
>
> This will produce the range you are looking for...
>
>
> Cheers
>
>
> On Fri, Feb 4, 2011 at 12:13 AM, Steffen Neumann wrote:
>
>> Hi,
>>
>> from my old days I know about class A,B and C networks.
>> That definition is also used in the TYPE = RANGED
>> network definition. I see two problems there:
>>
>> 1) People might have different networks,
>>   e.g. e.g. a 192.168.0.0/23 with addresses
>>   from approx. 192.168.0.1 to 192.168.1.254
>>
>>   the onevnet definition should be as flexible.
>>
>> 2) In my 10.20.0.0/16 network, I want to have the
>>   physical hosts on 10.20.0.x and virtual machines
>>   on 10.20.1.y, essentially sharing the same subnet.
>>
>>   onevnet is defined as class B 10.20.0.0,
>>   but it will happily provide a lease colliding
>>   with my (dhcp-assigned) physical hosts.
>>
>>   The onevnet RANGE definition should allow a real range,
>>   similar to dnsmask's dhcp-range=10.20.0.10,10.20.0.250,1h
>>
>> Or did I miss anything ?
>>
>> Yours,
>> Steffen
>>
>>
>> --
>> IPB HalleAG Massenspektrometrie & Bioinformatik
>> Dr. Steffen Neumann  http://www.IPB-Halle.DE
>> Weinberg 3   http://msbi.bic-gh.de
>> 06120 Halle  Tel. +49 (0) 345 5582 - 1470
>>  +49 (0) 345 5582 - 0
>> sneumann(at)IPB-Halle.DE Fax. +49 (0) 345 5582 - 1409
>>
>> ___
>> Users mailing list
>> Users@lists.opennebula.org
>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>
>
>
>
> --
> Dr. Ruben Santiago Montero
> Associate Professor (Profesor Titular), Complutense University of Madrid
>
> URL: http://dsa-research.org/doku.php?id=people:ruben
> Weblog: http://blog.dsa-research.org/?author=7
>



-- 
Dr. Ruben Santiago Montero
Associate Professor (Profesor Titular), Complutense University of Madrid

URL: http://dsa-research.org/doku.php?id=people:ruben
Weblog: http://blog.dsa-research.org/?author=7
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] Create an Image and registering

[Krishna R. Kantam]

Great Thanks,

So I changed the paths and checked the permissions. The srv/cloud/var/images/ 
folder always shows conetents 1 item with 2GB (which is ubuntu.img) and free 
space available is 0 bytes.

registerubuntu.one file:

NAME  = "Ubuntu Web Development"
PATH  = /srv/cloud/one/var/images/ubuntu.img
PUBLIC= YES
DESCRIPTION   = "Ubuntu 10.04 desktop"

oned.config

IMAGE_REPOSITORY_PATH = /srv/cloud/var/images
DEFAULT_IMAGE_TYPE= "OS"
DEFAULT_DEVICE_PREFIX = "hd"


MANAGER_TIMER=30

HOST_MONITORING_INTERVAL = 600

VM_POLLING_INTERVAL  = 600

VM_DIR=/srv/cloud/one/var/images

SCRIPTS_REMOTE_DIR=/var/tmp/one

PORT=2633

DB = [ backend = "sqlite" ]


Now I get this error message:

[root@localhost bin]# oneimage register /srv/cloud/one/var/registerubuntu.one
Error: [ImageAllocate] Error trying to CREATE IMAGE Error inserting Image in DB.

-Krishna.


On Feb 3, 2011, at 4:33 PM, Ruben S. Montero wrote:

> Hi
> 
> This error is because a failure copying 
> 
> /srv/cloud/one/var/images/ubuntu.img
> to
> 
> /srv/cloud/var/images/83bfdec6884733dfc1030be8505f0717e3e21122
> 
> Maybe you have a misconfigured repository path in oned.conf? Check paths, 
> permissions, free space
> 
> Cheers
> 
> Ruben
> 
> 
> On Thu, Feb 3, 2011 at 9:02 PM, Krishna R. Kantam  wrote:
> Hello everyone,
> 
> I have OpenNebula 2.0.1 and i am trying to create and register an image. 
> Please see the log below and I keep getting the error message. What file 
> extension do I need for the template? or how can I create a template please 
> help
> 
> -Krishna
> 
> [root@localhost bin]# dd if=/dev/zero of=/srv/cloud/one/var/images/ubuntu.img 
> bs=1M count=2000
> 2000+0 records in
> 2000+0 records out
> 2097152000 bytes (2.1 GB) copied, 9.26583 seconds, 226 MB/s
> [root@localhost bin]# mkfs.ext3 /srv/cloud/one/var/images/ubuntu.imgmke2fs 
> 1.39 (29-May-2006)
> /srv/cloud/one/var/images/ubuntu.img is not a block special device.
> Proceed anyway? (y,n) y
> Filesystem label=
> OS type: Linux
> Block size=4096 (log=2)
> Fragment size=4096 (log=2)
> 256000 inodes, 512000 blocks
> 25600 blocks (5.00%) reserved for the super user
> First data block=0
> Maximum filesystem blocks=524288000
> 16 block groups
> 32768 blocks per group, 32768 fragments per group
> 16000 inodes per group
> Superblock backups stored on blocks: 
> 32768, 98304, 163840, 229376, 294912
> 
> Writing inode tables: done
> Creating journal (8192 blocks): done
> Writing superblocks and filesystem accounting information: done
> 
> This filesystem will be automatically checked every 31 mounts or
> 180 days, whichever comes first.  Use tune2fs -c or -i to override.
> 
> [root@localhost bin]# cat /srv/cloud/one/var/registerubuntu.one
> NAME  = "Ubuntu Web Development"
> PATH  = /srv/cloud/one/var/images/ubuntu.img
> PUBLIC= YES
> DESCRIPTION   = "Ubuntu 10.04 desktop"
> 
> [root@localhost bin]# oneimage register /srv/cloud/one/var/registerubuntu.one
> Error: No such file or directory - 
> /srv/cloud/var/images/83bfdec6884733dfc1030be8505f0717e3e21122
> 
> ___
> Users mailing list
> Users@lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
> 
> 
> 
> 
> -- 
> Dr. Ruben Santiago Montero
> Associate Professor (Profesor Titular), Complutense University of Madrid
> 
> URL: http://dsa-research.org/doku.php?id=people:ruben
> Weblog: http://blog.dsa-research.org/?author=7

___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] Create an Image and registering

[Krishna R. Kantam]

Though I was getting the error below it seems an image was registered. Does it 
mean is there a problem in registering the image?

[root@localhost bin]# oneimage list
  ID USER NAME TYPE  REGTIME PUB PER STAT  #VMS
   0 oneadmin   Ubuntu Desktop   OS   Jan 23, 2011 20:03 Yes  No disa 0
  15 oneadmin Ubuntu Web Developme   OS   Jan 24, 2011 00:35 Yes  No disa 0

-Krishna.


On Feb 4, 2011, at 12:35 PM, Krishna R. Kantam wrote:

> Great Thanks,
> 
> So I changed the paths and checked the permissions. The srv/cloud/var/images/ 
> folder always shows conetents 1 item with 2GB (which is ubuntu.img) and free 
> space available is 0 bytes.
> 
> registerubuntu.one file:
> 
> NAME  = "Ubuntu Web Development"
> PATH  = /srv/cloud/one/var/images/ubuntu.img
> PUBLIC= YES
> DESCRIPTION   = "Ubuntu 10.04 desktop"
> 
> oned.config
> 
> IMAGE_REPOSITORY_PATH = /srv/cloud/var/images
> DEFAULT_IMAGE_TYPE= "OS"
> DEFAULT_DEVICE_PREFIX = "hd"
> 
> 
> MANAGER_TIMER=30
> 
> HOST_MONITORING_INTERVAL = 600
> 
> VM_POLLING_INTERVAL  = 600
> 
> VM_DIR=/srv/cloud/one/var/images
> 
> SCRIPTS_REMOTE_DIR=/var/tmp/one
> 
> PORT=2633
> 
> DB = [ backend = "sqlite" ]
> 
> 
> Now I get this error message:
> 
> [root@localhost bin]# oneimage register /srv/cloud/one/var/registerubuntu.one
> Error: [ImageAllocate] Error trying to CREATE IMAGE Error inserting Image in 
> DB.
> 
> -Krishna.
> 
> 
> On Feb 3, 2011, at 4:33 PM, Ruben S. Montero wrote:
> 
>> Hi
>> 
>> This error is because a failure copying 
>> 
>> /srv/cloud/one/var/images/ubuntu.img
>> to
>> 
>> /srv/cloud/var/images/83bfdec6884733dfc1030be8505f0717e3e21122
>> 
>> Maybe you have a misconfigured repository path in oned.conf? Check paths, 
>> permissions, free space
>> 
>> Cheers
>> 
>> Ruben
>> 
>> 
>> On Thu, Feb 3, 2011 at 9:02 PM, Krishna R. Kantam  wrote:
>> Hello everyone,
>> 
>> I have OpenNebula 2.0.1 and i am trying to create and register an image. 
>> Please see the log below and I keep getting the error message. What file 
>> extension do I need for the template? or how can I create a template please 
>> help
>> 
>> -Krishna
>> 
>> [root@localhost bin]# dd if=/dev/zero 
>> of=/srv/cloud/one/var/images/ubuntu.img bs=1M count=2000
>> 2000+0 records in
>> 2000+0 records out
>> 2097152000 bytes (2.1 GB) copied, 9.26583 seconds, 226 MB/s
>> [root@localhost bin]# mkfs.ext3 /srv/cloud/one/var/images/ubuntu.imgmke2fs 
>> 1.39 (29-May-2006)
>> /srv/cloud/one/var/images/ubuntu.img is not a block special device.
>> Proceed anyway? (y,n) y
>> Filesystem label=
>> OS type: Linux
>> Block size=4096 (log=2)
>> Fragment size=4096 (log=2)
>> 256000 inodes, 512000 blocks
>> 25600 blocks (5.00%) reserved for the super user
>> First data block=0
>> Maximum filesystem blocks=524288000
>> 16 block groups
>> 32768 blocks per group, 32768 fragments per group
>> 16000 inodes per group
>> Superblock backups stored on blocks: 
>> 32768, 98304, 163840, 229376, 294912
>> 
>> Writing inode tables: done
>> Creating journal (8192 blocks): done
>> Writing superblocks and filesystem accounting information: done
>> 
>> This filesystem will be automatically checked every 31 mounts or
>> 180 days, whichever comes first.  Use tune2fs -c or -i to override.
>> 
>> [root@localhost bin]# cat /srv/cloud/one/var/registerubuntu.one
>> NAME  = "Ubuntu Web Development"
>> PATH  = /srv/cloud/one/var/images/ubuntu.img
>> PUBLIC= YES
>> DESCRIPTION   = "Ubuntu 10.04 desktop"
>> 
>> [root@localhost bin]# oneimage register /srv/cloud/one/var/registerubuntu.one
>> Error: No such file or directory - 
>> /srv/cloud/var/images/83bfdec6884733dfc1030be8505f0717e3e21122
>> 
>> ___
>> Users mailing list
>> Users@lists.opennebula.org
>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>> 
>> 
>> 
>> 
>> -- 
>> Dr. Ruben Santiago Montero
>> Associate Professor (Profesor Titular), Complutense University of Madrid
>> 
>> URL: http://dsa-research.org/doku.php?id=people:ruben
>> Weblog: http://blog.dsa-research.org/?author=7
> 
> ___
> Users mailing list
> Users@lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] OCA API / deleting user

[Daniel Molina Aranda]

Hi,

The current implementation require that the applications, built upon
the OCA API, check that kind of things.
This functionality will be added to the OpenNebula Core in upcoming
releases, this way the application wont have to take into account this
kind of stuff.

Regards.


On 4 February 2011 00:06, Piotr Kandziora  wrote:
> Hi,
>
>
> I have been performing tests with OpenNebula and noticed that using command
> line I am not able to delete user while it has some VMs running (it is ok).
> But, using OCA API this operation is possible and causes some strange
> behaviour. Details below:
>
> a) using command line (deleting user test11 is not possible, because it has
> running one-4014 vm instance):
>
> oneadmin@main:~$ oneuser list
>   ID USER    PASSWORD
>    0 oneadmin    4ff88aaddbd209d8026924c2cc2836b408698823
>    3 test11  4ff88aaddbd209d8026924c2cc2836b408698823
>
> oneadmin@main:~$ onevm list
>    ID USER NAME STAT CPU MEM    HOSTNAME    TIME
>  4014   test11 one-4014 runn   0  0K  root24 00 00:00:32
>
> oneadmin@main:~$ oneuser delete 3
> The user 3 still has VMs defined, aborting user delete.
>
> b) using OCA API (in my case Python OCA API):
>
> So, I am deleting user 'test11' using following code:
>
> #!/usr/bin/python
> import oca
>
> c = oca.Client('oneadmin:free','http://localhost:2633/RPC2')
>
> usr = oca.user.UserPool(c)
> usr.info(oca.ALL)
>
> for i in usr:
>     if i.name == 'test11':
>     i.delete()
>
> After it command 'onevm list' returns output:
>
> oneadmin@main:~$ onevm list
>    ID USER NAME STAT CPU MEM    HOSTNAME    TIME
> /usr/lib/one/ruby/client_utilities.rb:143:in `Float': invalid value for
> Float(): "" (ArgumentError)
>     from /usr/lib/one/ruby/client_utilities.rb:143:in `data_str'
>     from /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `collect'
>     from /usr/lib/one/ruby/client_utilities.rb:139:in `each'
>     from /usr/lib/one/ruby/client_utilities.rb:139:in `collect'
>     from /usr/lib/one/ruby/client_utilities.rb:139:in `data_str'
>     from /usr/lib/one/ruby/client_utilities.rb:138:in `collect'
>     from /usr/lib/one/ruby/client_utilities.rb:138:in `data_str'
>     from /usr/bin/onevm:208:in `list_short'
>     from /usr/bin/onevm:682
>
> At this moment I am not able to perform any action using onevm command.
>
> In this situation I had to fix it by manual modifcation in vm_pool table in
> opennebula database (I removed records that belonged to deleted user).
>
> Question is following: Do I have to ensure before deleting user that it does
> not have any running VM instances? Or this is unplanned behaviour and should
> be fixed?
>
> I am using OpenNebula version 2.0.1.
>
> Best regards
> Piotr Kandziora
>
>
>
>
> ___
> Users mailing list
> Users@lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>



-- 
Daniel Molina, Cloud Technology Engineer/Researcher
DSA Research Group: web http://dsa-research.org and blog
http://blog.dsa-research.org
OpenNebula Open Source Toolkit for Cloud Computing: http://www.OpenNebula.org
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

[one-users] Kernel panic - not syncing: Attempted to kill init!

[anoop Lekshmanan]

I get this error on loading ttylinux or any other image in to Xen Node and
LVM, I have tried native kernel as well, but that did not work.

device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised:
dm-de...@redhat.com
device-mapper: dm-raid45: initialized v0.2594l
Kernel panic - not syncing: Attempted to kill init!

My VM template:

NAME   = test
CPU= 1
MEMORY = 256
OS = [
   KERNEL = /boot/vmlinuz-2.6.18-194.32.1.el5xen,
   INITRD = /boot/initrd-2.6.18-194.32.1.el5xen.img,
   ROOT   = /dev/vg00/lv-one--0
   #BOOTLOADER  = /usr/bin/pygrub,
   #KERNEL_CMD = "ro"
 ]

DISK   = [
  IMAGE= "ttylin",
  #source   = "/dev/vg00/xenvm01",
  target   = "hdb",
  readonly = "no" ]

NIC= [ NETWORK = "Small network" ]

FEATURES=[ acpi="no" ]

GRAPHICS=[
   AUTOPORT=yes,
   KEYMAP=en-us,
   LISTEN=127.0.0.1,
   PORT=5901,
   TYPE=vnc ]

#CONTEXT = [
#hostname= "$NAME",
# ip_public   = "192.168.0.16",
#files  = "/opt/cloud/one/images/init.sh
/opt/cloud/one/.ssh/id_rsa.pub",
#target  = "hdc",
#root_pubkey = "id_rsa.pub",
#username= "oneadmin",
#user_pubkey = "id_rsa.pub"

VM deployment file generated:

name = 'one-65'
#O CPU_CREDITS = 256
memory  = '256'
kernel = '/boot/vmlinuz-2.6.18-194.32.1.el5xen'
ramdisk = '/boot/initrd-2.6.18-194.32.1.el5xen.img'
root = '/dev//dev/vg00/lv-one--0'
disk = [
'tap:aio:/opt/cloud/one/var//65/images/disk.0,hdb,w',
]
vif = [
' mac=02:00:c0:a8:1e:06,ip=192.168.30.6,bridge=xenbr0',
]
vfb = ['type=vnc,vnclisten=127.0.0.1,vncdisplay=1,keymap=en-us']



I am trying to load this in to LVM and ONE creates the LV successfully and
VM state ins "RUNN"

Any help would be appreciated.

Thanks,
Anoop
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] Kernel panic - not syncing: Attempted to kill init!

[Steven Timm]

The error you are getting is probably due to a malformed ramdisk
for your Xen kernel. Likely what is happening is that the ramdisk
is trying to load the real scsi device as sda1  rather than the xenblk
block device.  Try to replace the ramdisk and see if you do any better.
I had this same error a while ago and building a ramdisk on a xen
VM that was installed statically is what it took for me to make it work.

Also, just so you know, when you say  KERNEL = /boot/vmlinuz
etc, then the kernel and ramdisk have to be in that location
on your VM host, not inside the LVM you are trying to boot.
If you want to use the kernel/ramdisk inside the xen virtual machine
then you should use pygrub, which is what I use.

Steve


On Sat, 5 Feb 2011, anoop Lekshmanan wrote:


I get this error on loading ttylinux or any other image in to Xen Node and
LVM, I have tried native kernel as well, but that did not work.

device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised:
dm-de...@redhat.com
device-mapper: dm-raid45: initialized v0.2594l
Kernel panic - not syncing: Attempted to kill init!

My VM template:

NAME   = test
CPU= 1
MEMORY = 256
OS = [
  KERNEL = /boot/vmlinuz-2.6.18-194.32.1.el5xen,
  INITRD = /boot/initrd-2.6.18-194.32.1.el5xen.img,
  ROOT   = /dev/vg00/lv-one--0
  #BOOTLOADER  = /usr/bin/pygrub,
  #KERNEL_CMD = "ro"
]

DISK   = [
 IMAGE= "ttylin",
 #source   = "/dev/vg00/xenvm01",
 target   = "hdb",
 readonly = "no" ]

NIC= [ NETWORK = "Small network" ]

FEATURES=[ acpi="no" ]

GRAPHICS=[
  AUTOPORT=yes,
  KEYMAP=en-us,
  LISTEN=127.0.0.1,
  PORT=5901,
  TYPE=vnc ]

#CONTEXT = [
#hostname= "$NAME",
# ip_public   = "192.168.0.16",
#files  = "/opt/cloud/one/images/init.sh
/opt/cloud/one/.ssh/id_rsa.pub",
#target  = "hdc",
#root_pubkey = "id_rsa.pub",
#username= "oneadmin",
#user_pubkey = "id_rsa.pub"

VM deployment file generated:

name = 'one-65'
#O CPU_CREDITS = 256
memory  = '256'
kernel = '/boot/vmlinuz-2.6.18-194.32.1.el5xen'
ramdisk = '/boot/initrd-2.6.18-194.32.1.el5xen.img'
root = '/dev//dev/vg00/lv-one--0'
disk = [
   'tap:aio:/opt/cloud/one/var//65/images/disk.0,hdb,w',
]
vif = [
   ' mac=02:00:c0:a8:1e:06,ip=192.168.30.6,bridge=xenbr0',
]
vfb = ['type=vnc,vnclisten=127.0.0.1,vncdisplay=1,keymap=en-us']



I am trying to load this in to LVM and ONE creates the LV successfully and
VM state ins "RUNN"

Any help would be appreciated.

Thanks,
Anoop



--
--
Steven C. Timm, Ph.D  (630) 840-8525
t...@fnal.gov  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
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] Kernel panic - not syncing: Attempted to kill init!

[anoop Lekshmanan]

Thanks Steve.

I tried to boot using pyGrub and that did not work for me. I have prepared a
CentOS.img created using virt-install and registered with oneimage.

Could you please share how can I use guest's kernel.

Thanks again.

Anoop





On Sat, Feb 5, 2011 at 1:00 AM, Steven Timm  wrote:

>
> The error you are getting is probably due to a malformed ramdisk
> for your Xen kernel. Likely what is happening is that the ramdisk
> is trying to load the real scsi device as sda1  rather than the xenblk
> block device.  Try to replace the ramdisk and see if you do any better.
> I had this same error a while ago and building a ramdisk on a xen
> VM that was installed statically is what it took for me to make it work.
>
> Also, just so you know, when you say  KERNEL = /boot/vmlinuz
> etc, then the kernel and ramdisk have to be in that location
> on your VM host, not inside the LVM you are trying to boot.
> If you want to use the kernel/ramdisk inside the xen virtual machine
> then you should use pygrub, which is what I use.
>
> Steve
>
>
>
> On Sat, 5 Feb 2011, anoop Lekshmanan wrote:
>
>  I get this error on loading ttylinux or any other image in to Xen Node and
>> LVM, I have tried native kernel as well, but that did not work.
>>
>> device-mapper: uevent: version 1.0.3
>> device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised:
>> dm-de...@redhat.com
>> device-mapper: dm-raid45: initialized v0.2594l
>> Kernel panic - not syncing: Attempted to kill init!
>>
>> My VM template:
>>
>> NAME   = test
>> CPU= 1
>> MEMORY = 256
>> OS = [
>>  KERNEL = /boot/vmlinuz-2.6.18-194.32.1.el5xen,
>>  INITRD = /boot/initrd-2.6.18-194.32.1.el5xen.img,
>>  ROOT   = /dev/vg00/lv-one--0
>>  #BOOTLOADER  = /usr/bin/pygrub,
>>  #KERNEL_CMD = "ro"
>>]
>>
>> DISK   = [
>>  IMAGE= "ttylin",
>>  #source   = "/dev/vg00/xenvm01",
>>  target   = "hdb",
>>  readonly = "no" ]
>>
>> NIC= [ NETWORK = "Small network" ]
>>
>> FEATURES=[ acpi="no" ]
>>
>> GRAPHICS=[
>>  AUTOPORT=yes,
>>  KEYMAP=en-us,
>>  LISTEN=127.0.0.1,
>>  PORT=5901,
>>  TYPE=vnc ]
>>
>> #CONTEXT = [
>> #hostname= "$NAME",
>> # ip_public   = "192.168.0.16",
>> #files  = "/opt/cloud/one/images/init.sh
>> /opt/cloud/one/.ssh/id_rsa.pub",
>> #target  = "hdc",
>> #root_pubkey = "id_rsa.pub",
>> #username= "oneadmin",
>> #user_pubkey = "id_rsa.pub"
>>
>> VM deployment file generated:
>>
>> name = 'one-65'
>> #O CPU_CREDITS = 256
>> memory  = '256'
>> kernel = '/boot/vmlinuz-2.6.18-194.32.1.el5xen'
>> ramdisk = '/boot/initrd-2.6.18-194.32.1.el5xen.img'
>> root = '/dev//dev/vg00/lv-one--0'
>> disk = [
>>   'tap:aio:/opt/cloud/one/var//65/images/disk.0,hdb,w',
>> ]
>> vif = [
>>   ' mac=02:00:c0:a8:1e:06,ip=192.168.30.6,bridge=xenbr0',
>> ]
>> vfb = ['type=vnc,vnclisten=127.0.0.1,vncdisplay=1,keymap=en-us']
>>
>>
>>
>> I am trying to load this in to LVM and ONE creates the LV successfully and
>> VM state ins "RUNN"
>>
>> Any help would be appreciated.
>>
>> Thanks,
>> Anoop
>>
>>
> --
> --
> Steven C. Timm, Ph.D  (630) 840-8525
> t...@fnal.gov  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
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] Kernel panic - not syncing: Attempted to kill init!

[Steven Timm]

This is my template for running a Xen VM out of the image repository.
[timm@fcl002 ~/OpenNebula]$ cat cloudlvs_xen.one
NAME   = cloudlvs.fnal.gov
CPU= 2
VCPU   = 2
MEMORY = 2048

#OS = [
#  kernel = /vmlinuz,
#  initrd = /initrd.img,
#  root   = sda1,
#  kernel_cmd = "ro xencons=tty console=tty1"]

OS  =   [ bootloader = "/usr/bin/pygrub" ]

DISK  = [  image = "cloudlvs-persist-xen.img" ]

DISK   = [
  type = swap,
  size = 5120,
  target   = sdb ]

DISK   = [
  type = fs,
  size = 4096,
  format   = ext3,
  save = yes,
  target   = sdc,
  bus  = scsi ]

#NIC= [ NETWORK = "FermiCloud" ]
NIC = [ BRIDGE = "xenbr0", MAC = "00:16:3E:02:03:05" ]

FEATURES=[ acpi="no" ]

GRAPHICS = [
  type= "vnc",
  listen  = "127.0.0.1",
  port= "5916" ]

CONTEXT = [
hostname= "$NAME",
ip_public   = "131.225.154.207",
netmask = "255.255.254.0",
gateway = "131.225.154.1",
ns  = "131.225.8.120",
files  = "/cloud/images/OpenNebula/templates/init.sh 
/home/timm/OpenNebula/k5login",

target  = "hdc",
root_pubkey = "id_dsa.pub",
username= "opennebula",
user_pubkey = "id_dsa.pub"
]

REQUIREMENTS = "HYPERVISOR=\"xen\""

--

and here is the declaration of my image in the image repo.

[timm@fcl002 ~/OpenNebula]$ oneimage show 56
IMAGE  INFORMATION
ID : 56
NAME   : cloudlvs-persist-xen.img
TYPE   : OS
REGISTER TIME  : 02/03 17:02:52
PUBLIC : No
PERSISTENT : Yes
SOURCE : 
/var/lib/one/image-repo/d75ce946cc408f9db71bdf14ba6eecd5d20750a5

STATE  : used
RUNNING_VMS: 1

IMAGE TEMPLATE
BUS=scsi
DESCRIPTION=cloudlvs xen
DEV_PREFIX=sd
NAME=cloudlvs-persist-xen.img
PATH=/cloud/images/OpenNebula/images/cloudlvs-persist-xen.img
TYPE=OS


For Xen you are best to try to mount / as sda and that's what
this os template will do.

Steve



On Fri, 4 Feb 2011, Steven Timm wrote:



The error you are getting is probably due to a malformed ramdisk
for your Xen kernel. Likely what is happening is that the ramdisk
is trying to load the real scsi device as sda1  rather than the xenblk
block device.  Try to replace the ramdisk and see if you do any better.
I had this same error a while ago and building a ramdisk on a xen
VM that was installed statically is what it took for me to make it work.

Also, just so you know, when you say  KERNEL = /boot/vmlinuz
etc, then the kernel and ramdisk have to be in that location
on your VM host, not inside the LVM you are trying to boot.
If you want to use the kernel/ramdisk inside the xen virtual machine
then you should use pygrub, which is what I use.

Steve


On Sat, 5 Feb 2011, anoop Lekshmanan wrote:


I get this error on loading ttylinux or any other image in to Xen Node and
LVM, I have tried native kernel as well, but that did not work.

device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised:
dm-de...@redhat.com
device-mapper: dm-raid45: initialized v0.2594l
Kernel panic - not syncing: Attempted to kill init!

My VM template:

NAME   = test
CPU= 1
MEMORY = 256
OS = [
  KERNEL = /boot/vmlinuz-2.6.18-194.32.1.el5xen,
  INITRD = /boot/initrd-2.6.18-194.32.1.el5xen.img,
  ROOT   = /dev/vg00/lv-one--0
  #BOOTLOADER  = /usr/bin/pygrub,
  #KERNEL_CMD = "ro"
]

DISK   = [
 IMAGE= "ttylin",
 #source   = "/dev/vg00/xenvm01",
 target   = "hdb",
 readonly = "no" ]

NIC= [ NETWORK = "Small network" ]

FEATURES=[ acpi="no" ]

GRAPHICS=[
  AUTOPORT=yes,
  KEYMAP=en-us,
  LISTEN=127.0.0.1,
  PORT=5901,
  TYPE=vnc ]

#CONTEXT = [
#hostname= "$NAME",
# ip_public   = "192.168.0.16",
#files  = "/opt/cloud/one/images/init.sh
/opt/cloud/one/.ssh/id_rsa.pub",
#target  = "hdc",
#root_pubkey = "id_rsa.pub",
#username= "oneadmin",
#user_pubkey = "id_rsa.pub"

VM deployment file generated:

name = 'one-65'
#O CPU_CREDITS = 256
memory  = '256'
kernel = '/boot/vmlinuz-2.6.18-194.32.1.el5xen'
ramdisk = '/boot/initrd-2.6.18-194.32.1.el5xen.img'
root = '/dev//dev/vg00/lv-one--0'
disk = [
   'tap:aio:/opt/cloud/one/var//65/images/disk.0,hdb,w',
]
vif = [
   ' mac=02:00:c0:a8:1e:06,ip=192.168.30.6,bridge=xenbr0',
]
vfb = ['type=vnc,vnclisten=127.0.0.1,vncdisplay=1,keymap=en-us']



I am trying to load this in to LVM and ONE creates the LV successfully and
VM state ins "RUNN"

Any help would be appreciated.

Thanks,
Anoop






--
--
Steven C. Timm, Ph.D  (630) 840-8525
t...@fnal.gov  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
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] Kernel panic - not syncing: Attempted to kill init!

[anoop Lekshmanan]

Steve, Thank you so much!

I was really stuck here and you saved me.

:)

Thanks,
Anoop

On Sat, Feb 5, 2011 at 1:38 AM, Steven Timm  wrote:

>
> This is my template for running a Xen VM out of the image repository.
> [timm@fcl002 ~/OpenNebula]$ cat cloudlvs_xen.one
> NAME   = cloudlvs.fnal.gov
> CPU= 2
> VCPU   = 2
> MEMORY = 2048
>
> #OS = [
> #  kernel = /vmlinuz,
> #  initrd = /initrd.img,
> #  root   = sda1,
> #  kernel_cmd = "ro xencons=tty console=tty1"]
>
> OS  =   [ bootloader = "/usr/bin/pygrub" ]
>
> DISK  = [  image = "cloudlvs-persist-xen.img" ]
>
> DISK   = [
>  type = swap,
>  size = 5120,
>  target   = sdb ]
>
> DISK   = [
>  type = fs,
>  size = 4096,
>  format   = ext3,
>  save = yes,
>  target   = sdc,
>  bus  = scsi ]
>
> #NIC= [ NETWORK = "FermiCloud" ]
> NIC = [ BRIDGE = "xenbr0", MAC = "00:16:3E:02:03:05" ]
>
> FEATURES=[ acpi="no" ]
>
> GRAPHICS = [
>  type= "vnc",
>  listen  = "127.0.0.1",
>  port= "5916" ]
>
> CONTEXT = [
>hostname= "$NAME",
>ip_public   = "131.225.154.207",
>netmask = "255.255.254.0",
>gateway = "131.225.154.1",
>ns  = "131.225.8.120",
>files  = "/cloud/images/OpenNebula/templates/init.sh
> /home/timm/OpenNebula/k5login",
>target  = "hdc",
>root_pubkey = "id_dsa.pub",
>username= "opennebula",
>user_pubkey = "id_dsa.pub"
> ]
>
> REQUIREMENTS = "HYPERVISOR=\"xen\""
>
> --
>
> and here is the declaration of my image in the image repo.
>
> [timm@fcl002 ~/OpenNebula]$ oneimage show 56
> IMAGE  INFORMATION
> ID : 56
> NAME   : cloudlvs-persist-xen.img
> TYPE   : OS
> REGISTER TIME  : 02/03 17:02:52
> PUBLIC : No
> PERSISTENT : Yes
> SOURCE :
> /var/lib/one/image-repo/d75ce946cc408f9db71bdf14ba6eecd5d20750a5
> STATE  : used
> RUNNING_VMS: 1
>
> IMAGE TEMPLATE
> BUS=scsi
> DESCRIPTION=cloudlvs xen
> DEV_PREFIX=sd
> NAME=cloudlvs-persist-xen.img
> PATH=/cloud/images/OpenNebula/images/cloudlvs-persist-xen.img
> TYPE=OS
>
>
> For Xen you are best to try to mount / as sda and that's what
> this os template will do.
>
> Steve
>
>
>
>
> On Fri, 4 Feb 2011, Steven Timm wrote:
>
>
>> The error you are getting is probably due to a malformed ramdisk
>> for your Xen kernel. Likely what is happening is that the ramdisk
>> is trying to load the real scsi device as sda1  rather than the xenblk
>> block device.  Try to replace the ramdisk and see if you do any better.
>> I had this same error a while ago and building a ramdisk on a xen
>> VM that was installed statically is what it took for me to make it work.
>>
>> Also, just so you know, when you say  KERNEL = /boot/vmlinuz
>> etc, then the kernel and ramdisk have to be in that location
>> on your VM host, not inside the LVM you are trying to boot.
>> If you want to use the kernel/ramdisk inside the xen virtual machine
>> then you should use pygrub, which is what I use.
>>
>> Steve
>>
>>
>> On Sat, 5 Feb 2011, anoop Lekshmanan wrote:
>>
>>  I get this error on loading ttylinux or any other image in to Xen Node
>>> and
>>> LVM, I have tried native kernel as well, but that did not work.
>>>
>>> device-mapper: uevent: version 1.0.3
>>> device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised:
>>> dm-de...@redhat.com
>>> device-mapper: dm-raid45: initialized v0.2594l
>>> Kernel panic - not syncing: Attempted to kill init!
>>>
>>> My VM template:
>>>
>>> NAME   = test
>>> CPU= 1
>>> MEMORY = 256
>>> OS = [
>>>  KERNEL = /boot/vmlinuz-2.6.18-194.32.1.el5xen,
>>>  INITRD = /boot/initrd-2.6.18-194.32.1.el5xen.img,
>>>  ROOT   = /dev/vg00/lv-one--0
>>>  #BOOTLOADER  = /usr/bin/pygrub,
>>>  #KERNEL_CMD = "ro"
>>>]
>>>
>>> DISK   = [
>>>  IMAGE= "ttylin",
>>>  #source   = "/dev/vg00/xenvm01",
>>>  target   = "hdb",
>>>  readonly = "no" ]
>>>
>>> NIC= [ NETWORK = "Small network" ]
>>>
>>> FEATURES=[ acpi="no" ]
>>>
>>> GRAPHICS=[
>>>  AUTOPORT=yes,
>>>  KEYMAP=en-us,
>>>  LISTEN=127.0.0.1,
>>>  PORT=5901,
>>>  TYPE=vnc ]
>>>
>>> #CONTEXT = [
>>> #hostname= "$NAME",
>>> # ip_public   = "192.168.0.16",
>>> #files  = "/opt/cloud/one/images/init.sh
>>> /opt/cloud/one/.ssh/id_rsa.pub",
>>> #target  = "hdc",
>>> #root_pubkey = "id_rsa.pub",
>>> #username= "oneadmin",
>>> #user_pubkey = "id_rsa.pub"
>>>
>>> VM deployment file generated:
>>>
>>> name = 'one-65'
>>> #O CPU_CREDITS = 256
>>> memory  = '256'
>>> kernel = '/boot/vmlinuz-2.6.18-194.32.1.el5xen'
>>> ramdisk = '/boot/initrd-2.6.18-194.32.1.el5xen.img'
>>> root = '/dev//dev/vg00/lv-one--0'
>>> disk = [
>>>   'tap:aio:/opt/cloud/one/var//65/images/disk.0,hdb,w',
>>> ]
>>> vif = [
>>>   ' mac=02:00:c0:a8:1e:06,ip=192.168.30.6,bridge=xenbr0',
>>> ]
>>> vfb = ['type=vnc,vnclisten=127.0.0.1,vncdisplay=1,keymap=en-us']
>>>
>>>
>>>
>>> I am trying to load this in to LVM and ONE creates the LV successfull

[one-users] Create a VM using onevm create

[Krishna R. Kantam]

Hi all,

I created an image and network but When i try to create VM using onevm create i 
was getting this error. I have the image created in 
/srv/cloud/var/images/ubuntu.img and have all the permissions, Please help.

Error: [VirtualMachineAllocate] Error trying to CREATE VM Could not get disk 
image for VM.

firstVM:

CPU= 1
MEMORY = 2056

DISK=[image="/srv/cloud/var/images/ubuntu.img"]

DISK = [ type   = swap,
 size   = 1024 ]
NIC=[NETWORK="Red LAN", IP=192.168.0.3]

[root@localhost bin]# onevnet list
  ID USER NAME  TYPE BRIDGE P #LEASES
   0 oneadmin Public   Fixed   vbr1 N   0
   1 oneadmin Red LAN Ranged   vbr0 N   0

[root@localhost bin]# onevnet show 1
VIRTUAL NETWORK 1 INFORMATION   
ID:   : 1   
UID:  : 0   
PUBLIC: N   

VIRTUAL NETWORK TEMPLATE
BRIDGE=vbr0
NAME=Red LAN
NETWORK_ADDRESS=192.168.0.0
NETWORK_SIZE=C
TYPE=RANGED

[root@localhost bin]# onevm create /srv/cloud/one/templates/firstVM.template
Error: [VirtualMachineAllocate] Error trying to CREATE VM Could not get disk 
image for VM.

-Krishna.

On Feb 4, 2011, at 12:42 PM, Krishna R. Kantam wrote:

> Though I was getting the error below it seems an image was registered. Does 
> it mean is there a problem in registering the image?
> 
> [root@localhost bin]# oneimage list
>   ID USER NAME TYPE  REGTIME PUB PER STAT  
> #VMS
>0 oneadmin   Ubuntu Desktop   OS   Jan 23, 2011 20:03 Yes  No disa > 0
>   15 oneadmin Ubuntu Web Developme   OS   Jan 24, 2011 00:35 Yes  No disa > 0
> 
> -Krishna.
> 
> 
> On Feb 4, 2011, at 12:35 PM, Krishna R. Kantam wrote:
> 
>> Great Thanks,
>> 
>> So I changed the paths and checked the permissions. The 
>> srv/cloud/var/images/ folder always shows conetents 1 item with 2GB (which 
>> is ubuntu.img) and free space available is 0 bytes.
>> 
>> registerubuntu.one file:
>> 
>> NAME  = "Ubuntu Web Development"
>> PATH  = /srv/cloud/one/var/images/ubuntu.img
>> PUBLIC= YES
>> DESCRIPTION   = "Ubuntu 10.04 desktop"
>> 
>> oned.config
>> 
>> IMAGE_REPOSITORY_PATH = /srv/cloud/var/images
>> DEFAULT_IMAGE_TYPE= "OS"
>> DEFAULT_DEVICE_PREFIX = "hd"
>> 
>> 
>> MANAGER_TIMER=30
>> 
>> HOST_MONITORING_INTERVAL = 600
>> 
>> VM_POLLING_INTERVAL  = 600
>> 
>> VM_DIR=/srv/cloud/one/var/images
>> 
>> SCRIPTS_REMOTE_DIR=/var/tmp/one
>> 
>> PORT=2633
>> 
>> DB = [ backend = "sqlite" ]
>> 
>> 
>> Now I get this error message:
>> 
>> [root@localhost bin]# oneimage register /srv/cloud/one/var/registerubuntu.one
>> Error: [ImageAllocate] Error trying to CREATE IMAGE Error inserting Image in 
>> DB.
>> 
>> -Krishna.
>> 
>> 
>> On Feb 3, 2011, at 4:33 PM, Ruben S. Montero wrote:
>> 
>>> Hi
>>> 
>>> This error is because a failure copying 
>>> 
>>> /srv/cloud/one/var/images/ubuntu.img
>>> to
>>> 
>>> /srv/cloud/var/images/83bfdec6884733dfc1030be8505f0717e3e21122
>>> 
>>> Maybe you have a misconfigured repository path in oned.conf? Check paths, 
>>> permissions, free space
>>> 
>>> Cheers
>>> 
>>> Ruben
>>> 
>>> 
>>> On Thu, Feb 3, 2011 at 9:02 PM, Krishna R. Kantam  
>>> wrote:
>>> Hello everyone,
>>> 
>>> I have OpenNebula 2.0.1 and i am trying to create and register an image. 
>>> Please see the log below and I keep getting the error message. What file 
>>> extension do I need for the template? or how can I create a template please 
>>> help
>>> 
>>> -Krishna
>>> 
>>> [root@localhost bin]# dd if=/dev/zero 
>>> of=/srv/cloud/one/var/images/ubuntu.img bs=1M count=2000
>>> 2000+0 records in
>>> 2000+0 records out
>>> 2097152000 bytes (2.1 GB) copied, 9.26583 seconds, 226 MB/s
>>> [root@localhost bin]# mkfs.ext3 /srv/cloud/one/var/images/ubuntu.imgmke2fs 
>>> 1.39 (29-May-2006)
>>> /srv/cloud/one/var/images/ubuntu.img is not a block special device.
>>> Proceed anyway? (y,n) y
>>> Filesystem label=
>>> OS type: Linux
>>> Block size=4096 (log=2)
>>> Fragment size=4096 (log=2)
>>> 256000 inodes, 512000 blocks
>>> 25600 blocks (5.00%) reserved for the super user
>>> First data block=0
>>> Maximum filesystem blocks=524288000
>>> 16 block groups
>>> 32768 blocks per group, 32768 fragments per group
>>> 16000 inodes per group
>>> Superblock backups stored on blocks: 
>>> 32768, 98304, 163840, 229376, 294912
>>> 
>>> Writing inode tables: done
>>> Creating journal (8192 blocks): done
>>> Writing superblocks and filesystem accounting information: done
>>> 
>>> This filesystem will be automatically checked every 31 mounts or
>>> 180 days, whichever comes first.  Use tune2fs -c or -i to override.
>>> 
>>> [root@localhost bin]# cat /srv/cloud/one/var/registerubuntu.one
>>> NAME  = "Ubuntu Web Development"
>>> PATH  = /srv/cloud/one/var/images/ubuntu.img
>>> PUBLIC= YES
>>> DESCRIPTION   = "Ubuntu 1

Re: [one-users] Incomplete information from hosts polling (VMWare ESXi 4.1 an OpenNebula 2.0.1)

[Ruben S. Montero]

Hi,

You have to add also de CPU capacity for the VM (apart from the number of
virtual cpus CPUs). The CPU value is used at the allocation phase. However
you are specifying MEMORY and should be included in the allocated memeory
(USED MEMORY in onehost show) So I guess there should be other problem with
your template.

Cheers

Ruben

On Fri, Feb 4, 2011 at 10:50 AM, Luigi Fortunati
wrote:

> I can post the VM template content on monday. However, as far as I
> remember, the vm template was really simple:
> NAME="Debian"
> VCPU= 2
> MEMORY=1024
> DISK=[IMAGE="Debian5-i386"]
> OS=[ARCH=i686]
>
> The VMs can boot and run, I can log on console through vSphere Client on
> the newly created VMs.
>
> I noticed that if you don't declare the number on VCPU the VM doesn't get
> scheduled on a cluster node. This option seems mandatory but I didn't find
> any mention about it on the documentation.
> Another thing that seems mandatory is declaring the cpu architecture as
> i686, otherwise OpenNebula will return error when writing the deployment.0
> file.
>
>
> On Thu, Feb 3, 2011 at 5:42 PM, Ruben S. Montero wrote:
>
>> Hi,
>>
>> I am not sure this is related to the VMware monitoring... Can you send the
>> VM Templates?
>>
>> Thanks
>>
>> Ruben
>>
>> On Thu, Feb 3, 2011 at 5:10 PM, Luigi Fortunati <
>> luigi.fortun...@gmail.com> wrote:
>>
>>> Hi,
>>> I noticed a serious problem about the usage of VMWare ESXi 4.1 and
>>> OpenNebula 2.0.1.
>>> I'm actually using the VMWare driver addon which can be found on the
>>> opennebula website (ver. 1.0) and libvirt (ver. 0.8.7).
>>> It happens that OpenNebula can't get information about the usage of
>>> resources on the cluster nodes.
>>> By running 2 VM (each one requires 2 VCPU and 1 GB of memory) and
>>> executing some commands I get this output.
>>>
>>> oneadmin@custom2:~/src$ onehost list
>>>   ID NAME  CLUSTER  RVM   TCPU   FCPU   ACPUTMEMFMEM
>>> STAT
>>>2 custom7.sns.itdefault0200200200  2G  0K
>>>  off
>>>1 custom6.sns.itdefault2200200200  2G  0K
>>>   on
>>> oneadmin@custom2:~/src$ onehost show 1
>>> HOST 1 INFORMATION
>>>
>>> ID: 1
>>> NAME  : custom6.sns.it
>>> CLUSTER   : default
>>> STATE : MONITORED
>>> IM_MAD: im_vmware
>>> VM_MAD: vmm_vmware
>>> TM_MAD: tm_vmware
>>>
>>> HOST SHARES
>>>
>>> MAX MEM   : 2096460
>>> USED MEM (REAL)   : 0
>>> USED MEM (ALLOCATED)  : 0
>>> MAX CPU   : 200
>>> USED CPU (REAL)   : 0
>>> USED CPU (ALLOCATED)  : 0
>>> RUNNING VMS   : 2
>>>
>>> MONITORING INFORMATION
>>>
>>> CPUSPEED=1992
>>> HYPERVISOR=vmware
>>> TOTALCPU=200
>>> TOTALMEMORY=2096460
>>>
>>> As you can see OpenNebula is unable to get correct information about the
>>> usage of resources on the cluster nodes.
>>> As these informations are used by the VM scheduler, OpenNebula is unable
>>> to schedule the VM correctly.
>>> I tried to create several VM and all of them were placed on the same host
>>> even if the latter was unable to satisfy the resource requirements of all
>>> the VMs.
>>> I think that this problem is strongly related to libvirt as OpenNebula
>>> use it to recover information about hosts and vm.
>>>
>>> Do you get the same behavior? Do you know if there is a way to solve this
>>> big issue?
>>>
>>> --
>>> Luigi Fortunati
>>>
>>> ___
>>> Users mailing list
>>> Users@lists.opennebula.org
>>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>>
>>>
>>
>>
>> --
>> Dr. Ruben Santiago Montero
>> Associate Professor (Profesor Titular), Complutense University of Madrid
>>
>> URL: http://dsa-research.org/doku.php?id=people:ruben
>> Weblog: http://blog.dsa-research.org/?author=7
>>
>
>
>
> --
> Luigi Fortunati
>



-- 
Dr. Ruben Santiago Montero
Associate Professor (Profesor Titular), Complutense University of Madrid

URL: http://dsa-research.org/doku.php?id=people:ruben
Weblog: http://blog.dsa-research.org/?author=7
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

[one-users] Load balancing hosts

[Steffen Neumann]

Hi,

I have a question about the scheduling in ONE:

1) Is there a way to migrate VMs off a host 
   to another free host ? I know I can manually 
   onevm migrate 56 13, but I had somehow expected 
   that onehost 12 disable would clean out that host.

2) Is there a way to migrate VMs between hosts 
   when load gets to high ? The VMs could become busy
   and saturate their host, or a few new hosts became available.
   Is live-migration a requirement for this ?

I am fine with pointers into the fine manual,
if the information is there it evaded me.

Yours,
Steffen

-- 
IPB HalleAG Massenspektrometrie & Bioinformatik
Dr. Steffen Neumann  http://www.IPB-Halle.DE
Weinberg 3   http://msbi.bic-gh.de
06120 Halle  Tel. +49 (0) 345 5582 - 1470
  +49 (0) 345 5582 - 0
sneumann(at)IPB-Halle.DE Fax. +49 (0) 345 5582 - 1409

___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org