All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Paolo Bonzini <pbonzini@redhat.com>,
	qemu-stable@nongnu.org, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Migration from older Qemu to Qemu 2.0.0 does not work
Date: Wed, 14 May 2014 10:29:41 +0200	[thread overview]
Message-ID: <53732975.2000201@profihost.ag> (raw)
In-Reply-To: <53732524.3080101@redhat.com>

Am 14.05.2014 10:11, schrieb Paolo Bonzini:
> Il 14/05/2014 09:17, Stefan Priebe - Profihost AG ha scritto:
>> i now was able to catch the error.
>>
>> It is:
>> Length mismatch: 0000:00:12.0/virtio-net-pci.rom: 40000 in != 10000
>> qemu: warning: error while loading state for instance 0x0 of device 'ram'
>> load of migration failed
> 
> This is a bug of your distribution.  The file sizes for ROMs should
> never change.  In particular, if you round the sizes up to the next
> power of 2 you should always have:
> 
> 128k for bios.bin
> 256k for bios-256k.bin
> 64k for pxe-*.rom
> 256k for efi-*.rom
> 64k for vgabios-*
> 
> Unfortunately, most distribution get pxe-*.rom sizes wrong, because at
> some point iPXE grew more features and didn't fit in 64k anymore with
> the default configuration.  I know at least Fedora does.
> 
> The solution is to copy the binaries from the QEMU git repository
> (directory pc-bios/) to /usr/share/qemu.

Hi,

i compile qemu on my own.

I have the rom files under /usr/share/kvm and they look like this:
ls -la /usr/share/kvm/*.rom
-rw-r--r-- 1 root root 173568 May 14 09:39 /usr/share/kvm/efi-e1000.rom
-rw-r--r-- 1 root root 174592 May 14 09:39 /usr/share/kvm/efi-eepro100.rom
-rw-r--r-- 1 root root 173056 May 14 09:39 /usr/share/kvm/efi-ne2k_pci.rom
-rw-r--r-- 1 root root 173056 May 14 09:39 /usr/share/kvm/efi-pcnet.rom
-rw-r--r-- 1 root root 176640 May 14 09:39 /usr/share/kvm/efi-rtl8139.rom
-rw-r--r-- 1 root root 171008 May 14 09:39 /usr/share/kvm/efi-virtio.rom
-rw-r--r-- 1 root root  67072 May 14 09:39 /usr/share/kvm/pxe-e1000.rom
-rw-r--r-- 1 root root  61440 May 14 09:39 /usr/share/kvm/pxe-eepro100.rom
-rw-r--r-- 1 root root  61440 May 14 09:39 /usr/share/kvm/pxe-ne2k_pci.rom
-rw-r--r-- 1 root root  61440 May 14 09:39 /usr/share/kvm/pxe-pcnet.rom
-rw-r--r-- 1 root root  61440 May 14 09:39 /usr/share/kvm/pxe-rtl8139.rom
-rw-r--r-- 1 root root  60416 May 14 09:39 /usr/share/kvm/pxe-virtio.rom

currently i don't know what's wrong.

Stefan

  reply	other threads:[~2014-05-14  8:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-09 13:13 [Qemu-devel] Migration from older Qemu to Qemu 2.0.0 does not work Stefan Priebe - Profihost AG
2014-05-09 13:41 ` Dr. David Alan Gilbert
2014-05-09 16:14   ` Stefan Priebe - Profihost AG
2014-05-09 16:29     ` Dr. David Alan Gilbert
2014-05-09 20:08       ` Stefan Priebe
2014-05-09 17:05 ` Paolo Bonzini
2014-05-09 20:53   ` Stefan Priebe
2014-05-14  7:17   ` Stefan Priebe - Profihost AG
2014-05-14  8:11     ` Paolo Bonzini
2014-05-14  8:29       ` Stefan Priebe - Profihost AG [this message]
2014-05-14  8:36         ` Paolo Bonzini
2014-05-14  8:38           ` Stefan Priebe - Profihost AG
2014-05-14  9:00             ` Paolo Bonzini
2014-05-14  9:25               ` Stefan Priebe - Profihost AG
2014-05-14  9:34                 ` Paolo Bonzini

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=53732975.2000201@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@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.