Hi,
I got:
Wed May 23 14:22:28 2012 [VMM][I]: ExitCode: 0
Wed May 23 14:22:28 2012 [VMM][W]: Adding custom monitoring attribute:
NAME one-588
Wed May 23 14:22:28 2012 [VMM][D]: Monitor Information:
CPU : 0
Memory: 3584000
Net_TX: 12001
Net_RX: 452
Wed May 23 1
Hello Francesco,
sorry for the late response. The problem then is that the block device is
not referenced in the qemu-kvm process? Can you send us the deployment
file? /var/lib/one/datastores/0//deployment.0
cheers,
Jaime
On Sun, Apr 15, 2012 at 1:35 PM, Francesco Camisa <
francesco.cam...@polic
Hi,
This is fixed in OpenNebula 3.4+, see [1]. I think you should be able to
apply these changes [2] in 3.2 without any problems.
Regarding your question, you can't force a VM in the suspended state to be
monitored and restored to the running state, unless you change in the DB
the vm_pool columns
On Mon, 21 May 2012 23:21:31 +0200, "Ruben S. Montero"
wrote:
> >
> > Hmmm... so, the intent is to have a same template which could be
> > deployed on hosts using different hypervisors on the same cloud ? I'm
> > not sure I understand the rationale. Could you elaborate a bit more ?
> >
>
> You m
Hi.
On Wed, 23 May 2012 16:26:00 +0200, Jaime Melis wrote:
> Once the vm starts we basically have no control as to where the operating
> systems puts the drives. The use of LABEL= and UUID= in the guest vms helps
> a lot, as you have already noticed.
>
Using LABELs is indeed probably the most s
Thanks for the info.
but i have tried installing a couple of time alreay..
both time using Debian 6 x64
i will try again over the weekend and post queries to the list.
the idea is to setup a small virtualized environment - mainly for learning.
with regards,
Nicolas
On 24/05/12 07:50, davo
