On Mon, Jul 13, 2020 at 14:04:25 +0200, Jiri Denemark wrote:
> On Sat, Jul 11, 2020 at 13:44:19 -0400, Mark Mielke wrote:
> > On Sat, Jul 11, 2020 at 6:04 AM Mark Mielke wrote:
> >
> > > On Fri, Jul 10, 2020 at 7:48 AM Mark Mielke wrote:
> > >
> > >> On Fri, Jul 10, 2020 at 7:14 AM Jiri
On Sat, Jul 11, 2020 at 13:44:19 -0400, Mark Mielke wrote:
> On Sat, Jul 11, 2020 at 6:04 AM Mark Mielke wrote:
>
> > On Fri, Jul 10, 2020 at 7:48 AM Mark Mielke wrote:
> >
> >> On Fri, Jul 10, 2020 at 7:14 AM Jiri Denemark
> >> wrote:
> >>
> >>> The implementation seems to be doing exactly
On Sat, Jul 11, 2020 at 6:04 AM Mark Mielke wrote:
> On Fri, Jul 10, 2020 at 7:48 AM Mark Mielke wrote:
>
>> On Fri, Jul 10, 2020 at 7:14 AM Jiri Denemark
>> wrote:
>>
>>> The implementation seems to be doing exactly what the commit message
>>>
>> says. The migratable=off default should be
On Fri, Jul 10, 2020 at 7:48 AM Mark Mielke wrote:
> On Fri, Jul 10, 2020 at 7:14 AM Jiri Denemark wrote:
>
>> > +if (qemuCaps &&
>>
> > +def->cpu->mode == VIR_CPU_MODE_HOST_PASSTHROUGH &&
>> > +!def->cpu->migratable) {
>> > +if (virQEMUCapsGet(qemuCaps,
On Fri, Jul 10, 2020 at 07:48:26 -0400, Mark Mielke wrote:
> On Fri, Jul 10, 2020 at 7:14 AM Jiri Denemark wrote:
>
> > On Sun, Jul 05, 2020 at 12:45:55 -0400, Mark Mielke wrote:
> > > With 6.4.0, live migration was working fine with Qemu 5.0. After trying
> > out
> > > 6.5.0, migration broke
On Fri, Jul 10, 2020 at 7:14 AM Jiri Denemark wrote:
> On Sun, Jul 05, 2020 at 12:45:55 -0400, Mark Mielke wrote:
> > With 6.4.0, live migration was working fine with Qemu 5.0. After trying
> out
> > 6.5.0, migration broke with the following error:
> >
> > libvirt.libvirtError: internal error:
On Fri, Jul 10, 2020 at 05:53:47 -0400, Mark Mielke wrote:
> Hi all:
>
> Any thoughts on this, or not time enough to look?
>
> I'm trying to decide what the right solution is on my end to deal with this
> breaking change, before more widely deploying it. If I know what the fix
> will be, I would
On Sun, Jul 05, 2020 at 12:45:55 -0400, Mark Mielke wrote:
> Hi all:
>
> With 6.4.0, live migration was working fine with Qemu 5.0. After trying out
> 6.5.0, migration broke with the following error:
>
> libvirt.libvirtError: internal error: unable to execute QEMU command
> 'migrate': State
Hi all:
Any thoughts on this, or not time enough to look?
I'm trying to decide what the right solution is on my end to deal with this
breaking change, before more widely deploying it. If I know what the fix
will be, I would like to align my strategy against it. Or, if we discuss
and the libvirt
Hi all:
With 6.4.0, live migration was working fine with Qemu 5.0. After trying out
6.5.0, migration broke with the following error:
libvirt.libvirtError: internal error: unable to execute QEMU command
'migrate': State blocked by non-migratable CPU device (invtsc flag)
I believe I traced the
10 matches
Mail list logo
