[Top][All Lists]

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

Re: [Qemu-devel] Migration from older Qemu to Qemu 2.0.0 does not work

From: Stefan Priebe - Profihost AG
Subject: Re: [Qemu-devel] Migration from older Qemu to Qemu 2.0.0 does not work
Date: Wed, 14 May 2014 09:17:23 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0


i now was able to catch the error.

It is:
Length mismatch: 0000:00:12.0/virtio-net-pci.rom: 40000 in != 10000
qemu: warning: error while loading state for instance 0x0 of device 'ram'
load of migration failed


Am 09.05.2014 19:05, schrieb Paolo Bonzini:
> Il 09/05/2014 15:13, Stefan Priebe - Profihost AG ha scritto:
>> I see no output at the monitor of Qemu 2.0.
>> # migrate -d tcp:a.b.c.d:6000
>> # info migrate
>> capabilities: xbzrle: off x-rdma-pin-all: off auto-converge: on
>> zero-blocks: off
>> Migration status: failed
>> total time: 0 milliseconds
>> The target machine is still running at this point with no output.
> Anything on its stdout?
> Another test you could do, in addition to changing the devices, is this:
> 1) try with commit 6141f3bd6904df7cf9519c6444a14a608b9874c4 on the
> destination (the next one caused a migration problem that was fixed
> later).  If it passes, go to step 1a.  If it fails, go to step 2.
> 1a) try with commit c01a71c1a56fa27f43449ff59e5d03b2483658a2.  If it
> passes, go to step 1b.  If it fails, report it here.
> 1b) bisect between v2.0.0 (known-bad) and
> c01a71c1a56fa27f43449ff59e5d03b2483658a2 (known-good) to find the
> culprit.  Report results.
> 2) change the source to v1.7.0 and bisect between v1.7.0 and
> 6141f3bd6904df7cf9519c6444a14a608b9874c4.  Report results.
> Thanks!
> Paolo

reply via email to

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