On Tue, Jan 05, 2016 at 10:34:16 +0100, Peter Krempa wrote:
> On Tue, Jan 05, 2016 at 10:23:59 +0100, Michal Privoznik wrote:
> > On 04.01.2016 16:28, Peter Krempa wrote:
> > > On Tue, Dec 22, 2015 at 15:41:16 +0100, Michal Privoznik wrote:
> > >>
On Tue, Jan 05, 2016 at 10:23:59 +0100, Michal Privoznik wrote:
> On 04.01.2016 16:28, Peter Krempa wrote:
> > On Tue, Dec 22, 2015 at 15:41:16 +0100, Michal Privoznik wrote:
> >> https://bugzilla.redhat.com/show_bug.cgi?id=1293351
> >>
> >> I've came across a bit of a silly scenario, but long
On 04.01.2016 16:28, Peter Krempa wrote:
> On Tue, Dec 22, 2015 at 15:41:16 +0100, Michal Privoznik wrote:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1293351
>>
>> I've came across a bit of a silly scenario, but long story short:
>> after domain was resumed, the virDomainSetTime() API hung for
On Tue, Dec 22, 2015 at 15:41:16 +0100, Michal Privoznik wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=1293351
>
> I've came across a bit of a silly scenario, but long story short:
> after domain was resumed, the virDomainSetTime() API hung for 5
> seconds after which it failed with an
https://bugzilla.redhat.com/show_bug.cgi?id=1293351
I've came across a bit of a silly scenario, but long story short:
after domain was resumed, the virDomainSetTime() API hung for 5
seconds after which it failed with an error. Problem was, that
there is no guest agent installed in the domain. But