On 2013-01-24 05:52, cmcc.dylan wrote:
what's more, libvirt cann't see the CPU parameter! sou i think CPU is
only used for overcommiting in opennebula level.
In Xen/KVM it is passed to Xen credit scheduler or KVM cgroup
configuration for minimal CPU share. So if you put CPU=0.25,VCPU=1, then
what's more, libvirt cann't see the CPU parameter! sou i think CPU is only used
for overcommiting in opennebula level.
At 2013-01-24 11:42:31,"cmcc.dylan" wrote:
if VCPU=4, i think the host will fork 4 process on behalf of this vm, because i
see it is so implemented in the qemu code.
I
if VCPU=4, i think the host will fork 4 process on behalf of this vm, because i
see it is so implemented in the qemu code.
I am very confused about this part of opennebula!
At 2013-01-24 11:31:34,"Steven C Timm" wrote:
VCPU is the parameter that controls how many cores appear internally in t
VCPU is the parameter that controls how many cores appear internally in the
virtual machine. I. e. if you have VCPU=4
Your VM will have 4 cores, but there will still only be one kvm process as seen
in the hypervisor that corresponds to it.
In a typical KVM setup it is possible to allocate more V
Hi, everyone!
I have a doubt what's the accurately means of CPU in the vm's template.
For a example, if we define a vm which has CPU=1 and VCPU = 4. In this
condition , what's result in the host os?
Does the host os fork 4 process on behalf of this vm and does the 4
process get 4
still the same problem,
if an error occurs because the installation steps OpenNebula mistake,
friends can provide a step by step OpenNebula installation from start to
finish (sunstone)?
because I do not understand the steps in opennebula.org and there are
several configurations that can not be inst
On 2013-01-23 14:55, Ruben S. Montero wrote:
Hi,
You can set cache if you are using the CLI, just create a disk
attachment file
with
DISK = [ IMAGE_ID = #{image_id}, TARGET = #{target}, CACHE=default ]
or
DISK = [ IMAGE_ID = #{image_id}, DEV_PREFIX = #{bus}, CACHE=default ]
OK, it works. B
Hi,
You can set cache if you are using the CLI, just create a disk attachment
file
with
DISK = [ IMAGE_ID = #{image_id}, TARGET = #{target}, CACHE=default ]
or
DISK = [ IMAGE_ID = #{image_id}, DEV_PREFIX = #{bus}, CACHE=default ]
and then use it for onevm attachdisk. I agree, that it should p
Hi,
I'm testing disks hotplug for kvm VMs and I found that there are no way
to setup cache mode for such disks. I tried to put CACHE="none" to image
template, but it is not used in attach_disk (tested with "rm -f
"$ATTACH_FILE"" commented out).
We have CACHE="none" default in vmm_exec_kvm.co
Hi,
I just tested with changed configuration. I put
DATASTORE_LOCATION=/real_path_to_datastores and I don't see any problems
with images (references counting and in memory name cache) for the moment.
Do symlinks in virtualisation hosts to datastores location could lead to
that ? I saw that i
Hi,
On 23 January 2013 07:47, Dimas Alif wrote:
> hay,
> config -->
> dimas@dimas:~S cat /var/log/one/sunstone.log
> --
>
> Server configuration
> --
> {:vnc_proxy_support_wss=>false,
> :one_xmlrpc=>"http://localho
Hi
On 22 January 2013 15:15, Emanuel Marzini wrote:
> Thanks a lot for your quickly reply. I hope that ganglia will resolve my
> problem. Therefore there isn't a mode in OpenNebula - OCCI to resolve this
> issue?
That information is included in the VM XML and you can retrieve it
using the OCA AP
To: Jaime Melis
Cc: Miloš Kozák , users
Hi!
Sure thing! I will find some time in the near future and contribute a
blog post on this setup!
Cheers
Mihály
On 22 January 2013 12:10, Jaime Melis wrote:
> Hi,
>
> thank you both for such a high quality and educational thread. I wasn't
> aware of
13 matches
Mail list logo
