All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicholas Thomas <nick@bytemark.co.uk>
To: "Andreas Färber" <afaerber@suse.de>
Cc: qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>,
	Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] (Another) 1.4.1 -> 1.5.0 migration failure
Date: Tue, 21 May 2013 13:20:19 +0100	[thread overview]
Message-ID: <1369138819.15129.1550.camel@eboracum.office.bytemark.co.uk> (raw)
In-Reply-To: <519B60A3.4030508@suse.de>

On Tue, 2013-05-21 at 13:55 +0200, Andreas Färber wrote:
> Hi,
> 
> Am 21.05.2013 13:33, schrieb Nicholas Thomas:
> > 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?
> 
> Negative, the watchdog has not undergone anything like the virtio
> refactorings. Are you using any virtio devices so that device numbering
> might somehow be different?

Virtio networking, discs, and the balloon device too. The full command
line looks like this:

/opt/qemu-1.4.1/bin/qemu-system-x86_64 -enable-kvm -S -name test -M pc
-watchdog i6300esb -watchdog-action reset -smp 1 -m 1024M
-L /opt/qemu-1.4.1/share/qemu -balloon virtio -vga cirrus -vnc
127.0.0.1:0, -drive
file=nbd:unix:/tmp/vm.test/disc-vda.sock,serial=vda,format=raw,if=virtio
-monitor unix:/tmp/vm.test/monitor,server -serial
unix:/tmp/vm.test/serial,server,nowait -boot order=ndc -usb -usbdevice
tablet -net user,vlan=50,name=user,restrict=y -k en-gb -net
nic,model=virtio,macaddr=fe:ff:fe:00:01:64,name=t35600,vlan=896 -net
tap,script=no,downscript=no,name=t35600,vlan=896,ifname=t35600 -rtc
base=utc,clock=host

lspci in the guest on 1.4.1:

00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II]
00:01.2 USB Controller: Intel Corporation 82371SB PIIX3 USB [Natoma/Triton II] (rev 01)
00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
00:02.0 VGA compatible controller: Cirrus Logic GD 5446
00:03.0 Ethernet controller: Qumranet, Inc. Device 1000
00:04.0 Unclassified device [00ff]: Qumranet, Inc. Device 1002
00:05.0 SCSI storage controller: Qumranet, Inc. Device 1001
00:06.0 System peripheral: Intel Corporation 6300ESB Watchdog Timer

lspci on 1.5.0:
00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II]
00:01.2 USB Controller: Intel Corporation 82371SB PIIX3 USB [Natoma/Triton II] (rev 01)
00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
00:02.0 VGA compatible controller: Cirrus Logic GD 5446
00:03.0 Ethernet controller: Qumranet, Inc. Device 1000
00:04.0 Unclassified device [00ff]: Qumranet, Inc. Device 1002
00:05.0 SCSI storage controller: Qumranet, Inc. Device 1001
00:06.0 System peripheral: Intel Corporation 6300ESB Watchdog Timer

lspci -vvv on 1.4.1:
[...]
00:06.0 System peripheral: Intel Corporation 6300ESB Watchdog Timer
	Subsystem: Qumranet, Inc. Device 1100
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
	Region 0: Memory at febf3000 (32-bit, non-prefetchable) [size=16]

lspci -vvv on 1.5.0:
[...]
00:06.0 System peripheral: Intel Corporation 6300ESB Watchdog Timer
	Subsystem: Qumranet, Inc. Device 1100
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Region 0: Memory at febf3000 (32-bit, non-prefetchable) [size=16]

So they seem to be identical from the guest's point of view?

/Nick

  reply	other threads:[~2013-05-21 12:20 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 [this message]
2013-05-21 16:55 ` mdroth
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=1369138819.15129.1550.camel@eboracum.office.bytemark.co.uk \
    --to=nick@bytemark.co.uk \
    --cc=afaerber@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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 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.