qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] (Another) 1.4.1 -> 1.5.0 migration failure


From: Nicholas Thomas
Subject: Re: [Qemu-devel] (Another) 1.4.1 -> 1.5.0 migration failure
Date: Tue, 21 May 2013 13:20:19 +0100

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 via email to

[Prev in Thread] Current Thread [Next in Thread]