Hi Jim,
I don't know what could be wrong with your setup. I don't know what version
of the packages you have installed, but, could you try uninstalling all the
opennebula-* packages you have and try with the ones provided by this repo?
https://nazar.karan.org/results/opennebula/_opennebula.repo
Hi,
Thanks for the feedback. This will be included in 4.0.
Regards,
-Tino
--
Constantino Vázquez Blanco, PhD, MSc
Project Engineer
OpenNebula - The Open-Source Solution for Data Center Virtualization
www.OpenNebula.org | @tinova79 | @OpenNebula
On Tue, Apr 30, 2013 at 6:53 PM, wrote:
> Tino
This is probably because of
http://dev.opennebula.org/issues/1605
You may try to use onedb fsck
Cheers
Ruben
On Mon, Apr 29, 2013 at 12:16 PM, rajesh kannan wrote:
> *13* oneadmin oneadmin one-13 *clea* 13 2G onehost
> 21d 06h33
> *14* oneadmin oneadmin one-14
Hi Guilherme
There is *no* difference from the OpenMPI point of view between physical
MPI and virtual MPI cluster. Just do the same steps but always *in* the
VMs. I suggest you:
1.- Prepare one VM image as front-end. With the LRMS of your choice
(SGE...), NFS MPI libraries and the like
2.- Confi
Now your error may be other:
"Mon Apr 29 12:43:14 2013 [VMM][I]: error: internal error process exited
while connecting to monitor: Could not access KVM kernel module: Permission
denied"
Sometimes is needed for oneadmin to be part of the kvm group to access
/dev/kvm...
Cheers
Ruben
On Mon, Apr
Hi Tim,
I don't know why the source tarball doesn't have the proper size... I
rebuilt 3.9.90 and packed the whole building dir just in case:
http://dev.opennebula.org/packages/.scratch/debian6-opennebula-3.9.90.tar.gz
cheers,
Jaime
On Mon, Apr 29, 2013 at 12:50 PM, Tim Stoop wrote:
> Hi all,
On 05/01/2013 12:25 PM, Jaime Melis wrote:
I don't know why the source tarball doesn't have the proper size... I
rebuilt 3.9.90 and packed the whole building dir just in case:
Thanks for that! However, when I try to create a new dsc from your
source directory, I get the following errors thrown
do scons -c first inside the opennebula-3.9.90 directory, or manually
remove those files
cheers,
Jaime
On Wed, May 1, 2013 at 12:52 PM, Tim Stoop wrote:
> On 05/01/2013 12:25 PM, Jaime Melis wrote:
>
>> I don't know why the source tarball doesn't have the proper size... I
>> rebuilt 3.9.90 and
Thanks.
Added oneadmin to KVM group.
Solves the problem.
Thank you again
Regards
Fazli
On Wed, May 1, 2013 at 5:43 PM, Ruben S. Montero
wrote:
> Now your error may be other:
>
> "Mon Apr 29 12:43:14 2013 [VMM][I]: error: internal error process exited
> while connecting to monitor: Could not a
On 05/01/2013 01:13 PM, Jaime Melis wrote:
do scons -c first inside the opennebula-3.9.90 directory, or manually
remove those files
Thanks Jaime, that helped.
For those interested, I've created packages for Wheezy. They're in our
wheezy repository which you can find here: https://debian.kumin
sunstone template update does not appear to deal gracefully with XML in
template variables.
I have a RAW section that I have in most of my VM templates. It the value in
DATA looks like this:
However, when I "update" a VM template in sunstone, it turns into this:
Hi,
If you're interessested in OpenNebula packaging for Debian, please join
team :
http://wiki.debian.org/Teams/pkg-opennebula
There is an experimental branch in our git repository :
http://anonscm.debian.org/gitweb/?p=pkg-opennebula/opennebula.git;a=shortlog;h=refs/heads/experimental
I'm lacking
Hi,
Let me describe an error situation that I experienced.
We are using ONe3.2.
I launch a VM off a persistent image but it fails at an very early stage (for
example tm_ln.sh)
so I end up having a VM in "failed" state.
Next, when I try to delete it via "onevm delete", I have error messages tha
Hi,
Yes this should be fixed now
http://dev.opennebula.org/issues/1717
Cheers
Ruben
On Wed, May 1, 2013 at 6:23 PM, Thomas Higdon wrote:
> sunstone template update does not appear to deal gracefully with XML in
> template variables.
>
> I have a RAW section that I have in most of my VM temp
Hi Hyunwoo
Yes totally right, this is in fact a bug that has been solved in recent
versions of OpenNebula... In this situation, the delete operation will
leave the persistent images in the error state so the consistency of the
image can be checked. OpenNebula will not try to move the image back to
Hi Ruben,
Thanks very much for the response.
Fortunately, this does not seem to happen frequently in our cluster
and even if it happens, it does not cause any big trouble,
we just have to manually do "oneimage enable" the persistent image
which went to "err" because of "onevm delete" .
Thanks fo
dear all,
for preparation to install opennebula, login to a remote root server to set
up a bridge. after run "apt-get install bridge-utils", add below two lines
in the /etc/network/interfaces file after "iface eth0 inet manual"
auto br0
iface br0 inet static
however when run "/etc/init.d/network
Hello q.s.,
Can you send us your interfaces file?
Thanks,
Jon A
On May 1, 2013 10:55 PM, "Qiubo Su (David Su)" wrote:
> dear all,
>
> for preparation to install opennebula, login to a remote root server to
> set up a bridge. after run "apt-get install bridge-utils", add below two
> lines in the
On 05/02/2013 06:54 AM, Qiubo Su (David Su) wrote:
> dear all,
>
> for preparation to install opennebula, login to a remote root server
> to set up a bridge. after run "apt-get install bridge-utils", add
> below two lines in the /etc/network/interfaces file after "iface eth0
> inet manual"
>
> aut
19 matches
Mail list logo