On Tue, May 03, 2016 at 09:31:13 +0200, Michal Privoznik wrote:
> On 03.05.2016 08:14, Peter Krempa wrote:
[...]
> > As long as it's guaranteed that any target qemu supported by libvirt
> > does support the interrogation you are going to do it's probably fine.
> >
> > The problem with your
On 03.05.2016 08:14, Peter Krempa wrote:
> On Mon, May 02, 2016 at 18:35:35 +0200, Michal Privoznik wrote:
>> On 02.05.2016 16:36, Peter Krempa wrote:
>>> On Fri, Apr 29, 2016 at 18:43:10 +0200, Michal Privoznik wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=1139766
>
> [...]
>
>>> Any
On Mon, May 02, 2016 at 18:35:35 +0200, Michal Privoznik wrote:
> On 02.05.2016 16:36, Peter Krempa wrote:
> > On Fri, Apr 29, 2016 at 18:43:10 +0200, Michal Privoznik wrote:
> >> https://bugzilla.redhat.com/show_bug.cgi?id=1139766
[...]
> > Any failure in qemuProcessReconnect results into
On 02.05.2016 16:36, Peter Krempa wrote:
> On Fri, Apr 29, 2016 at 18:43:10 +0200, Michal Privoznik wrote:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1139766
>>
>> Thing is, for some reasons you can have your domain's RTC to be
>> in something different than UTC. More weirdly, it's not only
On Fri, Apr 29, 2016 at 18:43:10 +0200, Michal Privoznik wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=1139766
>
> Thing is, for some reasons you can have your domain's RTC to be
> in something different than UTC. More weirdly, it's not only time
> zone what you can shift it of, but an
https://bugzilla.redhat.com/show_bug.cgi?id=1139766
Thing is, for some reasons you can have your domain's RTC to be
in something different than UTC. More weirdly, it's not only time
zone what you can shift it of, but an arbitrary value. So, if
domain is configured that way, libvirt will correctly
