All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>, qemu-devel@nongnu.org
Cc: quintela@redhat.com, dgilbert@redhat.com, mst@redhat.com
Subject: Re: [Qemu-devel] broken cross-version migration from 2.2 to 2.1
Date: Wed, 10 Dec 2014 16:48:31 +0100	[thread overview]
Message-ID: <54886B4F.7070805@redhat.com> (raw)
In-Reply-To: <54886AE4.3030403@redhat.com>



On 10/12/2014 16:46, Paolo Bonzini wrote:
> 
> 
> On 10/12/2014 16:38, Igor Mammedov wrote:
>> CCing to migration maintainers a couple migration regressions in 2.2:
>>
>> 1st error:
>>
>> source: 
>>  qemu-system-x86_64-2.2 -enable-kvm -m 512  -monitor stdio -M pc-i440fx-2.1
>>  (qemu) stop
>>  (qemu) migrate "exec:gzip -c > STATEFILE.gz"
>>
>> target:
>>  qemu-system-x86_64-2.1 -enable-kvm -m 512  -monitor stdio  -incoming "exec: gzip -c -d STATEFILE.gz" -M pc-i440fx-2.1
>>  qemu: warning: error while loading state for instance 0x0 of device 'serial'
>>  qemu-system-x86_64-2.1: load of migration failed: No such file or directory
>>
>> 2nd error:
>>
>> source:
>>  qemu-system-x86_64-2.2 -enable-kvm -smp 2 -m 512  -monitor stdio   -M pc-i440fx-2.1
>>  (qemu) stop
>>  (qemu) migrate "exec:gzip -c > STATEFILE.gz"
>>
>> target:
>>  qemu-system-x86_64-2.1 -enable-kvm -smp 2 -m 512 -monitor stdio -M pc-i440fx-2.1 -incoming "exec: gzip -c -d STATEFILE.gz"
>>  qemu: warning: error while loading state for instance 0x1 of device 'apic'
>>  qemu-system-x86_64-2.1: load of migration failed: No such file or directory
>>
>>
> 
> A lot of subsections were added between 2.1 and 2.2.  Which ones are
> being migrated in these cases?

Hmm, it's thr_ipending and apic_sipi.  /me debugs.

Paolo

      reply	other threads:[~2014-12-10 15:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-10 15:38 [Qemu-devel] broken cross-version migration from 2.2 to 2.1 Igor Mammedov
2014-12-10 15:46 ` Paolo Bonzini
2014-12-10 15:48   ` Paolo Bonzini [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54886B4F.7070805@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.