All of lore.kernel.org
 help / color / mirror / Atom feed
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: Tue, 12 Jan 2016 09:19:38 +0000	[thread overview]
Message-ID: <20160112091937.GE2455@work-vm> (raw)
In-Reply-To: <4e396059b95b088f1cf3c6b6668160d5@alukardd.org>

* Alexey (alukardd@alukardd.org) wrote:
> Hi David.
> 
> On 2016-01-11 22:51, Dr. David Alan Gilbert wrote:
> >* Alexey (alukardd@alukardd.org) wrote:
> >>Hello.
> >
> >Hi,
> >
> >>I have two servers between which I need have live migration.
> >>
> >>First server have QEMU emulator version 2.3.0
> >>Second server have QEMU emulator version 2.5.0
> >>
> >>Migration command look like this:
> >>/usr/bin/virsh migrate --live DOMAIN_NAME --migrateuri
> >>tcp://second.server
> >>qemu+ssh://second.server/system --verbose
> >>
> >>I got next error on console:
> >>error: operation failed: migration job: unexpectedly failed
> >>
> >>And next error in log on second server:
> >>2016-01-11T15:07:12.888647Z qemu-system-x86_64: Length too large:
> >>/rom@genroms/efi-virtio.rom: 0x32000 > 0x2d000: Invalid argument
> >>2016-01-11T15:07:12.888685Z qemu-system-x86_64: error while loading
> >>state
> >>for instance 0x0 of device 'ram'
> >>2016-01-11T15:07:12.889733Z qemu-system-x86_64: load of migration
> >>failed:
> >>Invalid argument
> >>
> >>In my libvirt domain I have option <rom bar="off"/>.
> >>
> >>I need to do a live migration in any possible way. How can I do this
> >>one?
> 
> >Is the efi-virtio ROM that you're using on the two versions the same
> >identical size?

> No, I have different efi-virtio.rom files, and I try to find a way which
> allows me not to copy the same efi-virtio.rom to all servers.

Right, the error does look like it's just complaining about the ROM size:

  2016-01-11T15:07:12.888647Z qemu-system-x86_64: Length too large:
  /rom@genroms/efi-virtio.rom: 0x32000 > 0x2d000: Invalid argument

It copes with small variations, but as soon as it flips over a 4K (?)
boundary then it has nowhere to put the extra data coming from the
larger ROM.

> >Also, can you post the commandline that you're using please.
> I already done this in my first email: virsh migrate...
> >>/usr/bin/virsh migrate --live DOMAIN_NAME --migrateuri
> >>tcp://second.server
> >>qemu+ssh://second.server/system --verbose

I meant for the QEMU itself; but if we've already found the ROMs are
different sizes, lets fix that first and see how you go.

Dave

> 
> Regards,
> Alexey Mochkin.
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

  reply	other threads:[~2016-01-12  9:19 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 [this message]
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
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=20160112091937.GE2455@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 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.