On Friday 03 September 2010 00:28:23 Székelyi Szabolcs wrote:
> We're using iSCSI targets directly (one target per vm), automatically
> created and initialized (cloned) from images on vm deploy. Althogh
> the target is based on IET behind gigabit links, it works quite
> well: we haven't done perfor
hello together,
I work with ONE 2.0beta based on ubuntu 10.04 with a NFS shared mount. I
try to livemigrate the supported ttylinux image and get the following
log output. The VM stays on the origin cluster node.
Thu Sep 2 23:38:36 2010 [VMM][I]: Command execution fail: virsh
--connect qemu
hello javier,
one more time,
I'm now working with OpenNebula 2.0beta with the KVM Hypervisor (head
node and cluster nodes are based on 10.04). I tried to play with the
supported ttylinux image form the ONE website. Starting the machine and
login via ssh is no problem. After Stop -> Resume the
On Thursday 02 September 2010 14:03:32 Michael Brown wrote:
> I've found that NFS is unacceptably slow too. With both the front end and
> the nodes mounting NFS, copies have to go through the front end, then back
> out again, which is a bit wasteful.
>
> We use a NetApp storage system, which can
Hello list,
I am new to OpenNebula and in the process of evaluating and testing it
for use at our main site. We are currently overhauling our
old infrastructure and got some new network hardware and servers. I am
looking for suggestions and input on if and how well our hardware will
suite a p
Hello,
Even if NFS with default configuration is not the most performant
shared filesystem we thought it was the most common shared filesystem
people could use for virtualization. Maybe you can make it faster
adding some parameters when mounting the shared filesystem. "async"
will make your VM's r
Can you also paste the output of 'vgs' ?
On Thu, Sep 2, 2010 at 6:23 PM, Jaime Melis wrote:
> Hi Italo,
>
> that is weird. Can you paste the output of 'lvs' ?
>
> regards,
> Jaime
>
> On Thu, Sep 2, 2010 at 6:16 PM, Italo Madalozo
> wrote:
>> Hi Jaime,
>> thanks for the reply. /images is not a
Hi Italo,
that is weird. Can you paste the output of 'lvs' ?
regards,
Jaime
On Thu, Sep 2, 2010 at 6:16 PM, Italo Madalozo wrote:
> Hi Jaime,
> thanks for the reply. /images is not a path it is the name of the VG, first
> I tried /dev/images and it did not work, when I change to /images it work
Hi Jaime,
thanks for the reply. /images is not a path it is the name of the VG, first
I tried /dev/images and it did not work, when I change to /images it works.
But it can not delete the snapshots afterwards.
Cheers
Italo
On 2 September 2010 15:59, Jaime Melis wrote:
> Hi Italo,
>
> it looks
Hi Tino,
I think I am getting a little farther in that I was trying to use the onevm
create instead of registering (which worked but not sure it helps).
However it fails to create the vm and I find this message in the
vmm_vmware.log:
[02.09.2010 11:57:44] Failed deploying VM 1 into
12core.x
Hi Italo,
it looks like $VG_NAME contains "/images", but it shouldn't be a path,
it should be the name of the volume group that LVM uses to create LVs.
Try changing that to "images", by editing tm_lvmrc.
cheers,
Jaime
On Wed, Sep 1, 2010 at 5:30 PM, Italo Madalozo wrote:
> Hi,
> I have been tr
Hi Tino,
Thanks for the quick reply.
How do you specify a VM PATH though as my VM has 5-6 associated files?
Here is the example given:
NAME = "Ubuntu Web Development"
PATH = /home/one_user/images/ubuntu_desktop.img
PUBLIC= YES
DESCRIPTION = "Ubuntu 10.04 desktop for
Hello,
It looks like the problem is the NFS configuration. KVM runs as root
and needs read/write acces to the disk image. It this disk image has
been exported by NFS with the root_squash option (by default) the
local root user of the worker node won't have the permissions it
needs. You might wan't
Hi Jonathan,
The way to use the image catalog is to upload individual images, each
of them requiring an image template [1].
One registered, a VM can use an image by just referencing the image's
name (same as the VirtualNetwork from your template, using just the
name "VMWareNET").
Regards,
-Tino
Hello,
I am trying to register my VM to use with OpenNebula and ESX 4.1.
I copied the VM folder to the shared nfs storage and then have tried to
create a template for this vm but I am not sure I have it right:
r...@:/srv/cloud/one# cat /export/vg0-lv0/WinXP.template
NAME=VMwareVM
MEMORY=256
I've found that NFS is unacceptably slow too. With both the front end and
the nodes mounting NFS, copies have to go through the front end, then back
out again, which is a bit wasteful.
We use a NetApp storage system, which can do flexclones. We can't take
advantage of that with OpenNebula becaus
16 matches
Mail list logo
