On 08.04.2020 16:08, Don Koch wrote:
> On Wed, 8 Apr 2020 10:34:08 +0300
> nshirokovskiy wrote:
>
>>
>>
>> On 07.04.2020 20:31, Don Koch wrote:
>>> On Thu, 19 Dec 2019 13:50:19 +0300
>>> Nikolay Shirokovskiy wrote:
>>>
If we use fake reboot then domain goes thru running->shutdown->running
On Wed, 8 Apr 2020 10:34:08 +0300
nshirokovskiy wrote:
>
>
> On 07.04.2020 20:31, Don Koch wrote:
> > On Thu, 19 Dec 2019 13:50:19 +0300
> > Nikolay Shirokovskiy wrote:
> >
> >> If we use fake reboot then domain goes thru running->shutdown->running
> >> state changes with shutdown state only
On 07.04.2020 20:31, Don Koch wrote:
> On Thu, 19 Dec 2019 13:50:19 +0300
> Nikolay Shirokovskiy wrote:
>
>> If we use fake reboot then domain goes thru running->shutdown->running
>> state changes with shutdown state only for short period of time. At
>> least this is implementation details
On Thu, 19 Dec 2019 13:50:19 +0300
Nikolay Shirokovskiy wrote:
> If we use fake reboot then domain goes thru running->shutdown->running
> state changes with shutdown state only for short period of time. At
> least this is implementation details leaking into API. And also there is
> one real case
On 12/19/19 5:50 AM, Nikolay Shirokovskiy wrote:
> If we use fake reboot then domain goes thru running->shutdown->running
> state changes with shutdown state only for short period of time. At
> least this is implementation details leaking into API. And also there is
> one real case when this is
If we use fake reboot then domain goes thru running->shutdown->running
state changes with shutdown state only for short period of time. At
least this is implementation details leaking into API. And also there is
one real case when this is not convinient. I'm doing a backup with the
help of
