From: mdroth <mdroth@linux.vnet.ibm.com>
To: Nicholas Thomas <nick@bytemark.co.uk>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] (Another) 1.4.1 -> 1.5.0 migration failure
Date: Tue, 21 May 2013 11:55:56 -0500 [thread overview]
Message-ID: <20130521165556.GA13602@vm> (raw)
In-Reply-To: <1369136018.15129.1538.camel@eboracum.office.bytemark.co.uk>
On Tue, May 21, 2013 at 12:33:38PM +0100, Nicholas Thomas wrote:
> Hi all,
>
> Migrating from:
>
> /opt/qemu-1.4.1/bin/qemu-system-x86_64 -M pc -watchdog i6300esb
> -watchdog-action reset [...]
>
> to:
>
> /opt/qemu-1.5.0/bin/qemu-system-x86_64 -M pc-i440fx-1.4 -watchdog
> i6300esb -watchdog-action reset [...]
>
> I get:
>
> qemu: warning: error while loading state for instance 0x0 of device
> '0000:00:06.0/i6300esb_wdt'
> load of migration failed
>
> Perhaps a similar issue to the network device one? I'm afraid I'm not
> sure how to debug these...
Doesn't look like it, here's a dump of the SaveStateEntry's (i just
added some debug statements in vmstate_register_with_alias_id):
verison: 1.4.1, se->idstr: timer, se->instance_id: 0
verison: 1.4.1, se->idstr: cpu_common, se->instance_id: 0
verison: 1.4.1, se->idstr: kvm-tpr-opt, se->instance_id: 0
verison: 1.4.1, se->idstr: apic, se->instance_id: 0
verison: 1.4.1, se->idstr: kvmclock, se->instance_id: 0
verison: 1.4.1, se->idstr: fw_cfg, se->instance_id: 0
verison: 1.4.1, se->idstr: PCIBUS, se->instance_id: 0
verison: 1.4.1, se->idstr: 0000:00:00.0/I440FX, se->instance_id: 0
verison: 1.4.1, se->idstr: 0000:00:01.0/PIIX3, se->instance_id: 0
verison: 1.4.1, se->idstr: i8259, se->instance_id: 0
verison: 1.4.1, se->idstr: i8259, se->instance_id: 1
verison: 1.4.1, se->idstr: ioapic, se->instance_id: 0
verison: 1.4.1, se->idstr: 0000:00:02.0/vga, se->instance_id: 0
verison: 1.4.1, se->idstr: hpet, se->instance_id: 0
verison: 1.4.1, se->idstr: mc146818rtc, se->instance_id: 0
verison: 1.4.1, se->idstr: i8254, se->instance_id: 0
verison: 1.4.1, se->idstr: serial, se->instance_id: 0
verison: 1.4.1, se->idstr: ps2kbd, se->instance_id: 0
verison: 1.4.1, se->idstr: ps2mouse, se->instance_id: 0
verison: 1.4.1, se->idstr: pckbd, se->instance_id: 0
verison: 1.4.1, se->idstr: vmmouse, se->instance_id: 0
verison: 1.4.1, se->idstr: port92, se->instance_id: 0
verison: 1.4.1, se->idstr: dma, se->instance_id: 0
verison: 1.4.1, se->idstr: dma, se->instance_id: 1
verison: 1.4.1, se->idstr: fdc, se->instance_id: 0
verison: 1.4.1, se->idstr: 0000:00:01.1/ide, se->instance_id: 0
verison: 1.4.1, se->idstr: i2c_bus, se->instance_id: 0
verison: 1.4.1, se->idstr: 0000:00:01.3/piix4_pm, se->instance_id: 0
verison: 1.4.1, se->idstr: 0000:00:06.0/i6300esb_wdt, se->instance_id: 0
version: 1.5.0, se->idstr: timer, se->instance_id: 0
version: 1.5.0, se->idstr: cpu_common, se->instance_id: 0
version: 1.5.0, se->idstr: cpu, se->instance_id: 0
version: 1.5.0, se->idstr: kvm-tpr-opt, se->instance_id: 0
version: 1.5.0, se->idstr: apic, se->instance_id: 0
version: 1.5.0, se->idstr: kvmclock, se->instance_id: 0
version: 1.5.0, se->idstr: fw_cfg, se->instance_id: 0
version: 1.5.0, se->idstr: PCIBUS, se->instance_id: 0
version: 1.5.0, se->idstr: 0000:00:00.0/I440FX, se->instance_id: 0
version: 1.5.0, se->idstr: 0000:00:01.0/PIIX3, se->instance_id: 0
version: 1.5.0, se->idstr: i8259, se->instance_id: 0
version: 1.5.0, se->idstr: i8259, se->instance_id: 1
version: 1.5.0, se->idstr: ioapic, se->instance_id: 0
version: 1.5.0, se->idstr: 0000:00:02.0/vga, se->instance_id: 0
version: 1.5.0, se->idstr: hpet, se->instance_id: 0
version: 1.5.0, se->idstr: mc146818rtc, se->instance_id: 0
version: 1.5.0, se->idstr: i8254, se->instance_id: 0
version: 1.5.0, se->idstr: serial, se->instance_id: 0
version: 1.5.0, se->idstr: ps2kbd, se->instance_id: 0
version: 1.5.0, se->idstr: ps2mouse, se->instance_id: 0
version: 1.5.0, se->idstr: pckbd, se->instance_id: 0
version: 1.5.0, se->idstr: vmmouse, se->instance_id: 0
version: 1.5.0, se->idstr: port92, se->instance_id: 0
version: 1.5.0, se->idstr: dma, se->instance_id: 0
version: 1.5.0, se->idstr: dma, se->instance_id: 1
version: 1.5.0, se->idstr: fdc, se->instance_id: 0
version: 1.5.0, se->idstr: 0000:00:01.1/ide, se->instance_id: 0
version: 1.5.0, se->idstr: i2c_bus, se->instance_id: 0
version: 1.5.0, se->idstr: 0000:00:01.3/piix4_pm, se->instance_id: 0
version: 1.5.0, se->idstr: 0000:00:06.0/i6300esb_wdt, se->instance_id: 0
Seems like the actual load is failing, but the VMSD hasn't changed so
i'm not sure what's going on.
>
> /Nick
>
>
>
next prev parent reply other threads:[~2013-05-21 17:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 11:33 [Qemu-devel] (Another) 1.4.1 -> 1.5.0 migration failure Nicholas Thomas
2013-05-21 11:55 ` Andreas Färber
2013-05-21 12:20 ` Nicholas Thomas
2013-05-21 16:55 ` mdroth [this message]
2013-05-21 17:26 ` mdroth
2013-05-21 17:50 ` Peter Maydell
2013-05-21 20:43 ` mdroth
2013-05-21 21:16 ` Peter Maydell
2013-05-21 22:07 ` mdroth
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=20130521165556.GA13602@vm \
--to=mdroth@linux.vnet.ibm.com \
--cc=nick@bytemark.co.uk \
--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).