Hi,
Yes, its possible and pretty easy. Find out the location of the image (oneimage
show id) and using OS's standard copy command (cp), copy the SOURCE_PATH to
another place and upload on your new cloud.
--
Regards,
Anandharaj
-Original Message-
From: Users
Hi,
How do we set / enable the bootmenu? Below is my current setup in vmm_kvm.conf
OS = [ boot = hd, arch = x86_64 ]
--
Regards,
Anandharaj
-Original Message-
From: Users [mailto:users-boun...@lists.opennebula.org] On Behalf Of Stefan
Kooman
Sent: Thursday, October 23, 2014
im giving up on opennebula for now, theres too many twist and turne tha i have to learn.
Sent using CloudMagic
On Wed, Oct 29, 2014 at 3:07 PM, Anandharaj Subramaniam anandharaj.man...@mimos.my wrote:Hi,
How do we set / enable the bootmenu? Below is my current setup in vmm_kvm.conf
OS = [
Quoting Anandharaj Subramaniam (anandharaj.man...@mimos.my):
Hi,
How do we set / enable the bootmenu? Below is my current setup in vmm_kvm.conf
OS = [ boot = hd, arch = x86_64 ]
That's a RAW (KVM) attribute:
RAW = osbootmenu enable='yes'//os
By including it in vmm_kvm.conf it's
Hi,
I'm running against this same issue as described here.
Regardless of how I try to look at it, non-persistent (and thus, volatile
images) are kinda annoying.
I understand how to create a template, install an OS using that template
(CDROM and persistent OS images linked) and then after
Hi
I have configured OpenNebula 4.8 and working good.
I have one Swift storage cluster in place. I want to store datastore on
that Swift storage.
I tried to create new datastore but in that there is no option for
Swift.
How can I add Swift storage for datastore?
Regards
Neelesh Gurjar
Hi Anandharaj,
Thank you for help me!
I'll do this.
Cheers,
Giovanni
Em 29.10.2014 07:57, Anandharaj Subramaniam escreveu:
Hi,
Yes, its possible and pretty easy. Find out the location of the image
(oneimage show id) and using OS's standard copy command (cp), copy
the SOURCE_PATH to another
Under OpenNebula 3 we have been using RANK=FREEMEMORY
to launch the next virtual machine on the hypervisor which
has the most memory available at the time. I am using the
same in OpenNebula 4.8 but it does not appear to be working,
even though FREEMEMORY is still a documented selection variable