From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:44181) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UelYI-0000f3-L7 for qemu-devel@nongnu.org; Tue, 21 May 2013 08:20:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UelYD-0002ga-IR for qemu-devel@nongnu.org; Tue, 21 May 2013 08:20:26 -0400 Received: from bacon.sh.bytemark.co.uk ([2001:41c8:20:862:3::25]:33295) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UelYD-0002gP-DR for qemu-devel@nongnu.org; Tue, 21 May 2013 08:20:21 -0400 From: Nicholas Thomas In-Reply-To: <519B60A3.4030508@suse.de> References: <1369136018.15129.1538.camel@eboracum.office.bytemark.co.uk> <519B60A3.4030508@suse.de> Content-Type: text/plain; charset="UTF-8" Date: Tue, 21 May 2013 13:20:19 +0100 Message-ID: <1369138819.15129.1550.camel@eboracum.office.bytemark.co.uk> Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] (Another) 1.4.1 -> 1.5.0 migration failure List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Andreas =?ISO-8859-1?Q?F=E4rber?= Cc: qemu-devel@nongnu.org, Anthony Liguori , Juan Quintela On Tue, 2013-05-21 at 13:55 +0200, Andreas F=C3=A4rber wrote: > Hi, >=20 > Am 21.05.2013 13:33, schrieb Nicholas Thomas: > > Migrating from: > >=20 > > /opt/qemu-1.4.1/bin/qemu-system-x86_64 -M pc -watchdog i6300esb > > -watchdog-action reset [...]=20 > >=20 > > to: > >=20 > > /opt/qemu-1.5.0/bin/qemu-system-x86_64 -M pc-i440fx-1.4 -watchdog > > i6300esb -watchdog-action reset [...]=20 > >=20 > > I get:=20 > >=20 > > qemu: warning: error while loading state for instance 0x0 of device > > '0000:00:06.0/i6300esb_wdt' > > load of migration failed > >=20 > > Perhaps a similar issue to the network device one? >=20 > 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=3Dnbd:unix:/tmp/vm.test/disc-vda.sock,serial=3Dvda,format=3Draw,if=3Dv= irtio -monitor unix:/tmp/vm.test/monitor,server -serial unix:/tmp/vm.test/serial,server,nowait -boot order=3Dndc -usb -usbdevice tablet -net user,vlan=3D50,name=3Duser,restrict=3Dy -k en-gb -net nic,model=3Dvirtio,macaddr=3Dfe:ff:fe:00:01:64,name=3Dt35600,vlan=3D896 -ne= t tap,script=3Dno,downscript=3Dno,name=3Dt35600,vlan=3D896,ifname=3Dt35600 -r= tc base=3Dutc,clock=3Dhost 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 I= I] 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 I= I] 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=3Dfast >TAbort- SERR- TAbort- SERR-