[one-users] Unknown state

[Ruben S. Montero]

Can you check the times in vm.log and oned.log (when the shutdown failure
occurs) is there any other relevant info in those logs?

Cheers

On Wed, Oct 27, 2010 at 10:15 PM, Rich Wellner <rkw at objenv.com> wrote:

> Leaving the monitor loop at 60 seconds and increasing the shutdown latency
> to 100 seconds (well more than the guest takes to shutdown) the problem
> remains.
>
>
> rw2
>
> On 10/27/10 8:33 AM, Tino Vazquez wrote:
>
>> Hi Rich,
>>
>> OpenNebula ceases its monitoring when the VM enters the shutdown
>> state. What is probably happening is that the VM takes more time to
>> shutdown than the default timeout, which is 40 seconds (20 iterations
>> over a 2 seconds sleep), so for OpenNebula is like if the shutdown
>> failed. This timeout default can be adjusted in
>> $ONE_LOCATION/bin/remotes/vmm/kvm/shutdown.
>>
>> Best regards,
>>
>> -Tino
>>
>> --
>> Constantino Vázquez Blanco | dsa-research.org/tinova
>> Virtualization Technology Engineer / Researcher
>> OpenNebula Toolkit | opennebula.org
>>
>>
>>
>> On Wed, Oct 27, 2010 at 1:08 AM, Rich Wellner<rkw at objenv.com>  wrote:
>>
>>> Hey guys,
>>>
>>> I have monitoring turned down to a minute so that I don't have much
>>> latency
>>> on my management while we're doing testing.  As a result, when I do a
>>> shutdown on a vm sometimes the shutdown isn't complete before the next
>>> monitoring update.  What ends up happening is that the state of the
>>> machine
>>> goes from running to shutdown, then a bit later to running again.
>>>  Finally,
>>> when the guest shutdown actually complete, the state goes to unknow
>>> because
>>> One doesn't know why the machine disappeared.
>>>
>>> It would be better if this race condition were handled more elegantly and
>>> One could tolerate that the machine took a while to shutdown.  As is a
>>> manual clean-up has to happen.  I have also confirmed that my one minute
>>> monitor cycle only makes the problem more likely.  If, by coincidence,
>>> someone asks One to shutdown a vm slightly before the monitor thread
>>> kicks
>>> off, this issue shows up.  So it seems any machine that is shutdown where
>>> timeToShutdown>  timeUntilMonitorRefresh will end up in an unknown state.
>>>
>>> rw2
>>>
>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opennebula.org
>>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>>
>>>
>>>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>



-- 
Dr. Ruben Santiago Montero
Associate Professor (Profesor Titular), Complutense University of Madrid

URL: http://dsa-research.org/doku.php?id=people:ruben
Weblog: http://blog.dsa-research.org/?author=7
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20101027/9b91e136/attachment-0002.htm>