On Fri, Jan 18, 2019 at 10:25 AM Paolo Bonzini wrote:
> On 18/01/19 14:41, Mark Mielke wrote:
> > It is useful to understand the risk. However, this is the same risk we
> > have been successfully living with for several years now, and it seems
> > abrupt to declare 3.1 and 3.2 as the Qemu version
On 2019/1/18 14:18, Christian Ehrhardt wrote:
On Fri, Jan 18, 2019 at 7:33 AM Mark Mielke wrote:
Thank you for the work on nested virtualization. Having had live migrations
fail in the past when nested virtualization has been active, it is great to
see that clever people have been working on t
* Paolo Bonzini (pbonz...@redhat.com) wrote:
> On 18/01/19 14:41, Mark Mielke wrote:
> > It is useful to understand the risk. However, this is the same risk we
> > have been successfully living with for several years now, and it seems
> > abrupt to declare 3.1 and 3.2 as the Qemu version beyond whi
On 18/01/19 14:41, Mark Mielke wrote:
> It is useful to understand the risk. However, this is the same risk we
> have been successfully living with for several years now, and it seems
> abrupt to declare 3.1 and 3.2 as the Qemu version beyond which migration
> requires a whole cluster restart wheth
On Fri, Jan 18, 2019 at 09:09:31AM -0500, Mark Mielke wrote:
> On Fri, Jan 18, 2019 at 8:44 AM Daniel P. Berrangé
> wrote:
>
> > On Fri, Jan 18, 2019 at 01:57:31PM +0100, Paolo Bonzini wrote:
> > > On 18/01/19 11:21, Daniel P. Berrangé wrote:
> > > > Yes, this is exactly why I said we should make
On Fri, Jan 18, 2019 at 8:44 AM Daniel P. Berrangé
wrote:
> On Fri, Jan 18, 2019 at 01:57:31PM +0100, Paolo Bonzini wrote:
> > On 18/01/19 11:21, Daniel P. Berrangé wrote:
> > > Yes, this is exactly why I said we should make the migration blocker
> > > be conditional on any L2 guest having been s
On Fri, Jan 18, 2019 at 01:57:31PM +0100, Paolo Bonzini wrote:
> On 18/01/19 11:21, Daniel P. Berrangé wrote:
> > On Fri, Jan 18, 2019 at 10:16:34AM +, Dr. David Alan Gilbert wrote:
> >> * Paolo Bonzini (pbonz...@redhat.com) wrote:
> >>> On 18/01/19 11:02, Dr. David Alan Gilbert wrote:
> >
On Fri, Jan 18, 2019 at 7:57 AM Paolo Bonzini wrote:
> On 18/01/19 11:21, Daniel P. Berrangé wrote:
> > On Fri, Jan 18, 2019 at 10:16:34AM +, Dr. David Alan Gilbert wrote:
> >> * Paolo Bonzini (pbonz...@redhat.com) wrote:
> >>> The solution is to restart the VM using "-cpu host,-vmx".
> >> Th
On 18/01/19 11:21, Daniel P. Berrangé wrote:
> On Fri, Jan 18, 2019 at 10:16:34AM +, Dr. David Alan Gilbert wrote:
>> * Paolo Bonzini (pbonz...@redhat.com) wrote:
>>> On 18/01/19 11:02, Dr. David Alan Gilbert wrote:
>
> It fails if the flag is set, rather than if any nested virtualizati
On Fri, Jan 18, 2019 at 10:16:34AM +, Dr. David Alan Gilbert wrote:
> * Paolo Bonzini (pbonz...@redhat.com) wrote:
> > On 18/01/19 11:02, Dr. David Alan Gilbert wrote:
> > >>
> > >> It fails if the flag is set, rather than if any nested virtualization has
> > >> been used before.
> > >>
> > >>
* Paolo Bonzini (pbonz...@redhat.com) wrote:
> On 18/01/19 11:02, Dr. David Alan Gilbert wrote:
> >>
> >> It fails if the flag is set, rather than if any nested virtualization has
> >> been used before.
> >>
> >> I'm concerned I will end up with a requirement for *all* guests to be
> >> restarted i
On 18/01/19 11:02, Dr. David Alan Gilbert wrote:
>>
>> It fails if the flag is set, rather than if any nested virtualization has
>> been used before.
>>
>> I'm concerned I will end up with a requirement for *all* guests to be
>> restarted in order to migrate them to the new hosts, rather than just
* Mark Mielke (mark.mie...@gmail.com) wrote:
> Thank you for the work on nested virtualization. Having had live migrations
> fail in the past when nested virtualization has been active, it is great to
> see that clever people have been working on this problem!
>
> My question is about whether a mi
On Fri, Jan 18, 2019 at 7:33 AM Mark Mielke wrote:
>
> Thank you for the work on nested virtualization. Having had live migrations
> fail in the past when nested virtualization has been active, it is great to
> see that clever people have been working on this problem!
>
> My question is about whet
Thank you for the work on nested virtualization. Having had live migrations
fail in the past when nested virtualization has been active, it is great to
see that clever people have been working on this problem!
My question is about whether a migration path has been considered to allow
live migratio
15 matches
Mail list logo
