From: Jason Wang <jasowang@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Amit Shah <amit.shah@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu list <qemu-devel@nongnu.org>,
Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PULL 8/9] static checker: e1000-82540em got aliased to e1000
Date: Wed, 6 Apr 2016 09:48:19 +0800 [thread overview]
Message-ID: <57046AE3.8000105@redhat.com> (raw)
In-Reply-To: <20160405133233.GF2242@work-vm>
On 04/05/2016 09:32 PM, Dr. David Alan Gilbert wrote:
> * Amit Shah (amit.shah@redhat.com) wrote:
>> On (Tue) 23 Feb 2016 [15:02:58], Jason Wang wrote:
>>>>> This means that 2.5 cannot migrate 2.4 virtual machines, right? Is that
>>>>> something we want to rectify in 2.6 by making e1000-82540em an alias of
>>>>> e1000 (instead of the other way round)?
>>>> You're right; I misread it. With that commit (8304402033):
>>>>
>>>> 2.4 with e1000-82540em will not migrate to 2.5 with e1000-82540em.
>>>>
>>>> This is despite they're aliased (so the cmdline is backward
>>>> compatible), but the migration device name actually changed.
>>>>
>>>> Of course, 2.5->2.4 will also not work.
>>>>
>>>> Since 2.4 emits 'e1000-82540em' as the device name in the migration
>>>> stream, and 2.5 emits just 'e1000', we have two different names for
>>>> the same device in two versions.
>>>>
>>>> To fix this, we'll need a hack on the dest side to allow e1000 and
>>>> e1000-82540em in the migration stream for the device, and this can be
>>>> done for 2.6 and 2.5.stable.
>>>>
>>>> Jason, can you attempt this?
>>>>
>>> Sure, but just need to understand the "problem". If I understand this
>>> correctly, the issue only happen for JSON description at the end of
>>> migration stream, and it won't break migration in fact?
>> No, this does break migration.
>>
>> The stream contained 'e1000-82540em' as the section header for the
>> device earlier. It now only has 'e1000'. So a newer qemu will only
>> accept 'e1000', but not 'e1000-82540em' (from an older release).
> OK, so do we need to get this fixed for 2.6 - i.e. now.
>
> Dave
Sorry for the late response.
Have a try with 2.4 -> 2.5 migration and it works. Looking at
save_section_header(), it will save se->idstr which seems always be
"e1000" even if e1000-82540em is used in cli, or is there anything I missed?
>
>> Amit
> --
> Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2016-04-06 1:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 13:56 [Qemu-devel] [PULL 0/9] migration: small fixes Amit Shah
2016-02-05 13:56 ` [Qemu-devel] [PULL 1/9] ram: Split host_from_stream_offset() into two helper functions Amit Shah
2016-02-05 13:56 ` [Qemu-devel] [PULL 2/9] migration: rename 'file' in MigrationState to 'to_dst_file' Amit Shah
2016-02-05 13:56 ` [Qemu-devel] [PULL 3/9] savevm: Split load vm state function qemu_loadvm_state Amit Shah
2016-02-05 13:56 ` [Qemu-devel] [PULL 4/9] migration/ram: Fix some helper functions' parameter to use PageSearchStatus Amit Shah
2016-02-05 13:56 ` [Qemu-devel] [PULL 5/9] qmp-commands.hx: Fix the missing options for migration parameters commands Amit Shah
2016-02-05 13:56 ` [Qemu-devel] [PULL 6/9] qmp-commands.hx: Document the missing options for migration capability commands Amit Shah
2016-02-05 13:56 ` [Qemu-devel] [PULL 7/9] migration: remove useless code Amit Shah
2016-02-05 13:56 ` [Qemu-devel] [PULL 8/9] static checker: e1000-82540em got aliased to e1000 Amit Shah
2016-02-11 13:04 ` Paolo Bonzini
2016-02-22 12:39 ` Amit Shah
2016-02-23 7:02 ` Jason Wang
2016-02-23 7:41 ` Amit Shah
2016-04-05 13:32 ` Dr. David Alan Gilbert
2016-04-06 1:48 ` Jason Wang [this message]
2016-04-06 13:52 ` Amit Shah
2016-04-07 7:25 ` Jason Wang
2016-02-05 13:56 ` [Qemu-devel] [PULL 9/9] migration: fix bad string passed to error_report() Amit Shah
2016-02-05 15:06 ` [Qemu-devel] [PULL 0/9] migration: small fixes Peter Maydell
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=57046AE3.8000105@redhat.com \
--to=jasowang@redhat.com \
--cc=amit.shah@redhat.com \
--cc=dgilbert@redhat.com \
--cc=pbonzini@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).