From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Alexey <alukardd@alukardd.org>
Cc: Qemu devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] live migration between different qemu versions
Date: Thu, 21 Jan 2016 11:49:38 +0000 [thread overview]
Message-ID: <20160121114937.GE2446@work-vm> (raw)
In-Reply-To: <5a37c43587e03e8636a1ddfbfadd82f6@alukardd.org>
* Alexey (alukardd@alukardd.org) wrote:
> Hello,
>
> On 2016-01-16 02:24, Eric Blake wrote:
> >On 01/12/2016 05:11 AM, Dr. David Alan Gilbert wrote:
> >
> >>>Tell me please right way to append zeros to "BIOS (ia32) ROM Ext.
> >>>(137*512)"
> >>>file?
> >>
> >>I'd use dd; something like:
> >> dd if=/dev/zero bs=1 count=18944 >> theromfile
> >>I think that should do it (203264-184320=18944)
> >
> >Or simpler:
> >
> >truncate --size=203264 theromfile
> It's great! I have successfully did migration of VM from qemu 2.3.0 to qemu
> 2.5.0.
>
> But when I try migrate to another side I got error:
> qemu-system-x86_64: error while loading state for instance 0x0 of device
> 'fw_cfg'
> qemu-system-x86_64: load of migration failed: No such file or directory
>
> Is it possible to do this migration?
Backwards migration doens't get much upstream testing; it looks like
this is the same as:
https://bugs.launchpad.net/qemu/+bug/1536487
Dave
> Regards,
> Alexey Mochkin.
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2016-01-21 11:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 15:46 [Qemu-devel] live migration between different qemu versions Alexey
2016-01-11 19:51 ` Dr. David Alan Gilbert
2016-01-11 20:49 ` Alexey
2016-01-12 9:19 ` Dr. David Alan Gilbert
2016-01-12 9:56 ` Alexey
2016-01-12 10:04 ` Dr. David Alan Gilbert
2016-01-12 10:24 ` Alexey
2016-01-12 12:11 ` Dr. David Alan Gilbert
2016-01-15 23:24 ` Eric Blake
2016-01-19 15:12 ` Alexey
2016-01-21 11:49 ` Dr. David Alan Gilbert [this message]
2016-01-21 11:55 ` Alexey
2016-01-12 12:00 ` Gerd Hoffmann
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=20160121114937.GE2446@work-vm \
--to=dgilbert@redhat.com \
--cc=alukardd@alukardd.org \
--cc=qemu-devel@nongnu.org \
/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).