[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [libvirt] [PATCH] interface: Check for interface (in-)activity on some operations
- From: Matthias Bolte <matthias bolte googlemail com>
- To: Eric Blake <eblake redhat com>
- Cc: libvir-list redhat com
- Subject: Re: [libvirt] [PATCH] interface: Check for interface (in-)activity on some operations
- Date: Fri, 15 Jul 2011 17:02:25 +0200
2011/7/15 Eric Blake <eblake redhat com>:
> On 07/15/2011 08:48 AM, Michal Privoznik wrote:
>> On 15.07.2011 16:45, Eric Blake wrote:
>>> On 07/15/2011 08:36 AM, Michal Privoznik wrote:
>>>>> On the other hand, if we don't support transient interfaces, then the
>>>>> above analysis which works for domains would have to be adjusted for
>>>>> interfaces, so you may have something to patch after all.
>>>>>
>>>> Well, although we have function interfaceCreate, it is actually (from
>>>> semantic POV) interfaceStart, because it just start inactive but defined
>>>> interface. So we do not support transient interfaces. Therefore
>>>> transitions for interfaces are slightly different from transitions for
>>>> domains. That's why I think we do need this patch.
>>>
>>> Let's nail down the transitions that we plan to support, then, just as I
>>> did earlier for domains.
>>>
>>> It would be even cooler to have a life cycle diagram with the API used
>>> to transition between states documented somewhere. I seem to recall
>>> seeing one for domains once, but couldn't find it in 5 minutes of
>>> searching right now.
>>>
>> You mean
>> http://wiki.libvirt.org/page/VM_lifecycle#States_that_a_guest_domain_can_be_in
>
> You found a different one than me, but that one also has the problem of
> no mention of a transient domain.
That one actually covers transient domain partly. Look at the
create/shutdown transition between undefined and running states.
--
Matthias Bolte
http://photron.blogspot.com
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]