it's always the same "pattern" there are too many 0 instead of X.
only seen: read:0x0000000000000000 ... expected:0xffffffffffffffff or read:0xffffffff00000000 ... expected:0xffffffffffffffff or read:0x0000bf000000bf00 ... expected:0xffffbfffffffbfff or read:0x0000000000000000 ... expected:0xb5b5b5b5b5b5b5b5 no idea if this helps. Stefan Am 07.02.2014 14:39, schrieb Stefan Priebe - Profihost AG: > Hi, > Am 07.02.2014 14:19, schrieb Paolo Bonzini: >> Il 07/02/2014 14:04, Stefan Priebe - Profihost AG ha scritto: >>> first of all i've now a memory image of a VM where i can reproduce it. >> >> You mean you start that VM with -incoming 'exec:cat /path/to/vm.img'? >> But google stress test doesn't report any error until you start >> migration _and_ it finishes? > > Sorry no i meant i have a VM where i saved the memory to disk - so i > don't need to wait hours until i can reproduce as it does not happen > with a fresh started VM. So it's a state file i think. > >> Another test: >> >> - start the VM with -S, migrate, do errors appear on the destination? > > I started with -S and the errors appear AFTER resuming/unpause the VM. > So it is fine until i resume it on the "new" host. > > Stefan >