public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Ren, Yongjie" <yongjie.ren@intel.com>
Cc: Avi Kivity <avi@redhat.com>, KVM list <kvm@vger.kernel.org>
Subject: Re: can't restore a guest saved by an older qemu
Date: Fri, 02 Mar 2012 09:47:58 +0100	[thread overview]
Message-ID: <4F50893E.8090006@siemens.com> (raw)
In-Reply-To: <1B4B44D9196EFF41AE41FDA404FC0A10053959@SHSMSX101.ccr.corp.intel.com>

On 2012-03-02 07:33, Ren, Yongjie wrote:
> Hi Avi,
> I can't restore a guest saved by an older qemu. I wonder if this issue is introduced by some latest commits on the file 'hw/i8254.c'.
> The new commit: b5ed4b6f  (on Mar 1)    I tried to restore a guest using this qemu.
> The old commit: 9d636ae7  (on Feb 11)    I saved a guest using this qemu.
> 
> I got some error when restoring a guest saved by an old qemu now.
> [root@vt-nhm9 jay]# qemu-system-x86_64 -smp 4 -m 1024 -hda rhel6u1.qcow -incoming "exec:dd if=save.img"
> Could not open option rom 'vapic.bin': No such file or directory
> qemu-system-x86_64: pci_add_option_rom: failed to find romfile "pxe-rtl8139.rom"
> VNC server running on `::1:5900'
> Unknown ramblock "0000:00:03.0/rtl8139.rom", cannot accept migration
> qemu: warning: error while loading state for instance 0x0 of device 'ram'
> load of migration failed

Confirmed. I get a different error, but something is broken here as
well. Bisecting...

Thanks,
Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2012-03-02  8:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-02  6:33 can't restore a guest saved by an older qemu Ren, Yongjie
2012-03-02  8:47 ` Jan Kiszka [this message]
2012-03-02  8:58   ` Zhang, Yang Z
2012-03-02  9:21     ` [PATCH] qemu-kvm: Fix migration from older version due to i8254 changes Jan Kiszka
2012-03-02  9:32       ` Ren, Yongjie
2012-03-07 10:48       ` Avi Kivity

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=4F50893E.8090006@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=yongjie.ren@intel.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