> On 05-Sep-2018, at 6:11 PM, Jaggi, Manish wrote:
>
>
>
>> On 05-Sep-2018, at 5:50 PM, Andrew Jones wrote:
>>
>> External Email
>>
>> On Wed, Sep 05, 2018 at 11:46:11AM +, Jaggi, Manish wrote:
>>> (a) Changes in KVM:
>>>
>>> - Introducing a specific error code (KVM_EINVARIANT) in cas
On Wed, Sep 05, 2018 at 12:42:05PM +, Jaggi, Manish wrote:
>
>
> > On 05-Sep-2018, at 5:50 PM, Andrew Jones wrote:
> >
> > External Email
> >
> > On Wed, Sep 05, 2018 at 11:46:11AM +, Jaggi, Manish wrote:
> >> (a) Changes in KVM:
> >>
> >> - Introducing a specific error code (KVM_EINV
> On 05-Sep-2018, at 5:50 PM, Andrew Jones wrote:
>
> External Email
>
> On Wed, Sep 05, 2018 at 11:46:11AM +, Jaggi, Manish wrote:
>> (a) Changes in KVM:
>>
>> - Introducing a specific error code (KVM_EINVARIANT) in case of invariant
>> writes.
>> This should not change anything to API
On Wed, Sep 05, 2018 at 11:46:11AM +, Jaggi, Manish wrote:
> (a) Changes in KVM:
>
> - Introducing a specific error code (KVM_EINVARIANT) in case of invariant
> writes.
> This should not change anything to API SET_ONE_REG KVM API.
> Not sure which is the best place to put the define…
> I have
> On 04-Sep-2018, at 3:24 PM, Andrew Jones wrote:
>
> External Email
>
> On Tue, Sep 04, 2018 at 09:16:58AM +, Jaggi, Manish wrote:
>>> On 31-Aug-2018, at 4:41 PM, Andrew Jones wrote:
>>> I think the sequence should look something like this:
>>>
>>> 1) Guest running on Host A with proces
On 4 September 2018 at 11:32, Dr. David Alan Gilbert
wrote:
> * Andrew Jones (drjo...@redhat.com) wrote:
>> Simply, users that migrate '-cpu host' VMs need to know what they're
>> doing.
>
> The problem here is that in the x86 world we've said:
> 'don't use -cpu host
>if you're using it be
* Andrew Jones (drjo...@redhat.com) wrote:
> On Tue, Sep 04, 2018 at 09:16:58AM +, Jaggi, Manish wrote:
> > > On 31-Aug-2018, at 4:41 PM, Andrew Jones wrote:
> > > I think the sequence should look something like this:
> > >
> > > 1) Guest running on Host A with processor a
> > > 2) Stop gue
Andrew Jones wrote:
> On Tue, Sep 04, 2018 at 09:16:58AM +, Jaggi, Manish wrote:
>> So which approach should be taken here, whats your take...
>>
[ Remoning Anthony form CC. Address don't exist anymore ]
> Inventing a base-AArch64 cpu model that can then be extended with optional
> feature
On Tue, Sep 04, 2018 at 09:16:58AM +, Jaggi, Manish wrote:
> > On 31-Aug-2018, at 4:41 PM, Andrew Jones wrote:
> > I think the sequence should look something like this:
> >
> > 1) Guest running on Host A with processor a
> > 2) Stop guest and save its state for migration
> > 3) Migrate gue
> On 31-Aug-2018, at 4:41 PM, Andrew Jones wrote:
>
> External Email
>
> Manish,
>
> Your mail reader doesn't appear to be providing any quoting, so I'm not
> sure I found all your replies. I've tried to fix up the quoting in order
> to reply here, but you should look into fixing your reader.
Manish,
Your mail reader doesn't appear to be providing any quoting, so I'm not
sure I found all your replies. I've tried to fix up the quoting in order
to reply here, but you should look into fixing your reader.
On Fri, Aug 31, 2018 at 09:52:12AM +, Jaggi, Manish wrote:
> On bleh-bleh, And
On 29-Aug-2018, at 6:46 PM, Andrew Jones
mailto:drjo...@redhat.com>> wrote:
External Email
On Wed, Aug 29, 2018 at 12:40:08PM +, Jaggi, Manish wrote:
On 28-Aug-2018, at 10:57 PM, Dr. David Alan Gilbert
mailto:dgilb...@redhat.com>> wrote:
External Email
(Cc'ing in Eric, Drew, and Peter
"Dr. David Alan Gilbert" wrote:
> * Jaggi, Manish (manish.ja...@cavium.com) wrote:
>
>> Just to add what happens in ARM64 case, qemu running on Machine A sends cpu
>> state information to Machine B.
>> This state contains MIDR value, and so Processor ID value is compared in KVM
>> and not in qem
* Jaggi, Manish (manish.ja...@cavium.com) wrote:
> Just to add what happens in ARM64 case, qemu running on Machine A sends cpu
> state information to Machine B.
> This state contains MIDR value, and so Processor ID value is compared in KVM
> and not in qemu (correcting myself).
>
> IIRC, Peter/
On Wed, Aug 29, 2018 at 12:40:08PM +, Jaggi, Manish wrote:
>
>
> > On 28-Aug-2018, at 10:57 PM, Dr. David Alan Gilbert
> > wrote:
> >
> > External Email
> >
> > (Cc'ing in Eric, Drew, and Peter for ARM stuff)
> >
> Thanks,
> > * Jaggi, Manish (manish.ja...@cavium.com) wrote:
> >>
> >>
> On 28-Aug-2018, at 10:57 PM, Dr. David Alan Gilbert
> wrote:
>
> External Email
>
> (Cc'ing in Eric, Drew, and Peter for ARM stuff)
>
Thanks,
> * Jaggi, Manish (manish.ja...@cavium.com) wrote:
>>
>>
>>> On 23-Aug-2018, at 7:59 PM, Juan Quintela wrote:
>>>
>>> External Email
>>>
>>> "J
(Cc'ing in Eric, Drew, and Peter for ARM stuff)
* Jaggi, Manish (manish.ja...@cavium.com) wrote:
>
>
> > On 23-Aug-2018, at 7:59 PM, Juan Quintela wrote:
> >
> > External Email
> >
> > "Jaggi, Manish" wrote:
> >> Hi,
> >
> > Hi
> >
> > [Note that I was confused about what do you mean with
> On 23-Aug-2018, at 7:59 PM, Juan Quintela wrote:
>
> External Email
>
> "Jaggi, Manish" wrote:
>> Hi,
>
> Hi
>
> [Note that I was confused about what do you mean with problems with
> processorID. There is no processorID on the migration stream, so I
> didn't understood what you were talk
"Jaggi, Manish" wrote:
> Hi,
Hi
[Note that I was confused about what do you mean with problems with
processorID. There is no processorID on the migration stream, so I
didn't understood what you were talking about. Until I realized that
you were trying to migrate from different cpu types]
> Po
Hi,
Posting again with my cavium ID and CCing relevant folks
Live Migration between machines with different processorIds
VM Migration between machines with different processorId values throws
error in qemu/kvm. Though this check is appropriate but is overkill where
two machines are of same SoC/
20 matches
Mail list logo
