Unfortunately there's not such feature in libvirt/kvm but we are
looking into implementing something similar for that hypervisor. As a
start point kvm processes can be reniced so some VMs have more
priority than other but we don't have a way to exactly set those
values. We will implement it as soon
Can you send us the start of oned.log where the configuration
variables are written?
On Fri, Mar 11, 2011 at 4:45 PM, Gian Uberto Lauri wrote:
> Hello, I just set up a frontend using the opennebula-2.0-1.i386.rpm to
> replace the previous frontend that worked perfectly on a 64 bit xeon.
>
> I no
I have configured a bridge interface on KVM box and able to use it in
OpenNebula VM deployment. Here VMs are getting their IP address from a DHCP
server running on another system (VM image is configured with dhcp settings). I
am wondering if I still need IP addresses while defining vnets - NETW
Hi,
The mount point is the same, so you don't need the VM_DIR variable.
Please comment it away, restart oned and try again.
Regards,
-Tino
--
Constantino Vázquez Blanco, MSc
OpenNebula Major Contributor
www.OpenNebula.org | @tinova79
On Fri, Mar 11, 2011 at 7:30 PM, Kyle Jake Plimack
wrote:
I updated vm_dir, but got the same error.
My setup is as follows
Master:
/var/lib/oneoak-vm-host004(rw,async,no_subtree_check,no_root_squash)
Node:
oak-dev-nebula001:/var/lib/one on /var/lib/one type nfs
(rw,soft,intr,rsize=32768,wsize=32768,addr=172.16.3.175)
VM_DIR=/var/lib/one/var/image
Hi,
First, thank you very much for your time and your efforts. I totally agree
that using the vz commands would be a better approach, there is a special
driver format (XML) that pass to the driver the template in XML format. We
can use that in a ruby/python script to create the containers.
B
Hi,
VM_DIR has to be the mount point of $ONE_LOCATION/var in the remote
nodes, so if /var/lib/one is being mounted by the nodes as
/data/cloud/one, you should set VM_DIR to /data/cloud/one/ and not to
/data/cloud/one/var/images.
Hope it helps,
-Tino
--
Constantino Vázquez Blanco, MSc
OpenNebula
http://sites.google.com/site/donatetojapanearthquakevictims/
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
If you want to use tm_nfs instead of tm_ssh in your existing hosts you
can use a trick, changing the oned.conf arguments section of that
driver:
---
SSH Transfer Manager Driver Configuration
--
On Fri, 2011-03-11 at 16:51 +0100, Olivier Sallou wrote:
> Hi,
> I have not tested it but will "one" allow to remove a host while still having
> VM running on host?
No, It'll complain and refuse.
oneadmin@cumulus:~$ onehost delete 17
Host still has associated VMs, aborting delete.
Hi, I have not tested it but will "one" allow to remove a host while still
having VM running on host? I will have to to the same modif (tm ssh -> nfs)
soon on a running cloud. Or should I comment a check in the client code for the
duration of the modification? Regards Olivier Hi,
The host is t
Hello, I just set up a frontend using the opennebula-2.0-1.i386.rpm to replace
the previous frontend that worked perfectly on a 64 bit xeon.
I noticed that in building the name for the remote scripts, it uses '-t'
instead of 'kvm' as in the following log lines:
Message received: LOG - 8 bash: /
Hi, so far we haven't been able to reproduce this or to find the cause.
Is it possible that you simply forgot to click on the "add" button after
you filled in the fields in the add disk/image section of the kvm
wizard, so the disk appears in the "current disks" box?
Héctor
El 10/03/11 07:53, GON
Hi Cristoph,
You can find that info already in the doc:
http://opennebula.org/documentation:rel2.0:cg#opennebula_users
Best,
-T
--
Constantino Vázquez Blanco, MSc
OpenNebula Major Contributor
www.OpenNebula.org | @tinova79
On Fri, Mar 11, 2011 at 3:49 PM, Christoph Raible
wrote:
> Am 11.03.
Am 11.03.2011 15:02, schrieb Christoph Raible:
Hi @all,
I tried to install opennebula 2.2 Beta1 on a RHEL 6 server.
I installed all requirements an did
/Master$ scons/ (with sqlite support)<--- This works fine
after that I did
//Master$// /./install.sh -d /srv/cloud/one/ <--- this works a
Hi,
You need to set the env variable ONE_LOCATION to /srv/cloud/one.
Regards,
-Tino
--
Constantino Vázquez Blanco, MSc
OpenNebula Major Contributor
www.OpenNebula.org | @tinova79
On Fri, Mar 11, 2011 at 3:02 PM, Christoph Raible
wrote:
> Hi @all,
>
> I tried to install opennebula 2.2 Beta1
Am 11.03.2011 15:05, schrieb Tino Vazquez:
Hi,
You need to set the env variable ONE_LOCATION to /srv/cloud/one.
Regards,
-Tino
--
Constantino Vázquez Blanco | dsa-research.org/tinova
Virtualization Technology Engineer / Researcher
OpenNebula Toolkit | opennebula.org
On Fri, Mar 11, 2011 a
Hi @all,
I tried to install opennebula 2.2 Beta1 on a RHEL 6 server.
I installed all requirements an did
/Master$ scons/ (with sqlite support)<--- This works fine
after that I did
//Master$// /./install.sh -d /srv/cloud/one/ <--- this works also fine
After that I want to start one with
OpenNebula also supports qcow [1] but does not enforce you to use that
format. We prefer to have as default the features that are common to
the drivers that come packed with the distribution. It could happen
that a xen installation is not prepared for qcow and people trying the
software could get m
Dear YE Lei,
Unfortunately, we don't have this functionality planned for our very
short term roadmap. We are aware of people interested in this very
same functionality, there are old threads in this mailing list on this
topic.
In any case, OpenNebula provides all the needed information for an
alg
Hi,
The host is trying to use the old driver. If you want to use a
different driver you have to:
1. Uncomment the driver in the oned.conf
2. Create again the host to use that driver: onehost create xx im_kvm
vmm_kvm tm_nfs
Hope this helps
On 11 March 2011 04:54, GONG YONGJIE A
wrote:
> Hi,
>
>
Hi,
Did you set the VM_DIR variable in $ONE_LOCATION/etc/oned.conf?
Regards,
-Tino
--
Constantino Vázquez Blanco, MSc
OpenNebula Major Contributor
www.OpenNebula.org | @tinova79
On Fri, Mar 11, 2011 at 8:23 AM, Kyle Jake Plimack
wrote:
> I'm brand new to OpenNebula and I'm trying to deploy
Hi,
It looks like the drivers are failing to load, can you send the first
200 lines of $ONE_OCATION/var/oned.log?
Regards,
-Tino
--
Constantino Vázquez Blanco | dsa-research.org/tinova
Virtualization Technology Engineer / Researcher
OpenNebula Toolkit | opennebula.org
On Fri, Mar 11, 2011 at
Hi,
I think this is related to:
http://dev.opennebula.org/issues/511
The OS Section is not being created properly in Sunstone. Therefore the
BOOT option is not recognised and takes the default value in ONE.
The patch is ready and should be available in the 2.2 branch soon.
Héctor
El 11/03/
Hi,
You should try
OS = [
BOOT = network
]
instead of
BOOT = network
in your VM template.
Hope this helps
http://www.opennebula.org/documentation:rel2.2:template
On 11 March 2011 04:07, GONG YONGJIE A
wrote:
>
> Hi,
>
> I just test to create one VM to boot from PXE but from "deplo
25 matches
Mail list logo