(sorry for the wrong list, I was unsure and I choose the wrong one :\)
On 03/16/2017 03:42 PM, Daniel P. Berrange wrote:
> On Thu, Mar 16, 2017 at 01:46:38PM +0100, Peter Krempa wrote:
>> For techincal discussions on design it's better to post to the
>> development list.
>>
>> On Mon, Feb 27, 201
"Daniel P. Berrange" writes:
> On Fri, Mar 17, 2017 at 02:07:11PM +0100, Milan Zamazal wrote:
>> "Daniel P. Berrange" writes:
>>
>> > On Fri, Mar 17, 2017 at 11:55:13AM +0100, Milan Zamazal wrote:
>> >> Hi, we experienced a strange, non-reproducible error after a successful
>> >> migration to a
On Fri, Mar 17, 2017 at 02:07:11PM +0100, Milan Zamazal wrote:
> "Daniel P. Berrange" writes:
>
> > On Fri, Mar 17, 2017 at 11:55:13AM +0100, Milan Zamazal wrote:
> >> Hi, we experienced a strange, non-reproducible error after a successful
> >> migration to another host. When we called virDomain
"Daniel P. Berrange" writes:
> On Fri, Mar 17, 2017 at 11:55:13AM +0100, Milan Zamazal wrote:
>> Hi, we experienced a strange, non-reproducible error after a successful
>> migration to another host. When we called virDomainDestroyFlags with
>> VIR_DOMAIN_DESTROY_GRACEFUL flag after the migration
On Fri, Mar 17, 2017 at 11:55:13AM +0100, Milan Zamazal wrote:
> Hi, we experienced a strange, non-reproducible error after a successful
> migration to another host. When we called virDomainDestroyFlags with
> VIR_DOMAIN_DESTROY_GRACEFUL flag after the migration on the source host,
> we got VIR_ER
Hi, we experienced a strange, non-reproducible error after a successful
migration to another host. When we called virDomainDestroyFlags with
VIR_DOMAIN_DESTROY_GRACEFUL flag after the migration on the source host,
we got VIR_ERR_OPERATION_INVALID (code 55) error. The same with
repeated virDomainD
