[Qemu-devel] [Bug 1689499] Re: copy-storage-all/inc does not easily converge with load going on

[Expired for QEMU because there has been no activity for 60 days.] ** Changed in: qemu Status: Incomplete => Expired -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1689499 Title:

[Qemu-devel] [Bug 1689499] Re: copy-storage-all/inc does not easily converge with load going on

OK, it'll be interesting if you get something repeatable, but sometimes these type of bugs go and hide in a dark corner until someone trips over them in a more critical situation. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

[Qemu-devel] [Bug 1689499] Re: copy-storage-all/inc does not easily converge with load going on

Ok, I found an hour to set up a test environment. I already had all the bisect script written until the systems were ready, but unfortunately it is not reproducible enough with my build from git as of today's master - out of 8 tries it showed as less of a slowdown once, and never to the hours

[Qemu-devel] [Bug 1689499] Re: copy-storage-all/inc does not easily converge with load going on

I'm "incompleting" myself until I was able to provide more :-/ -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1689499 Title: copy-storage-all/inc does not easily converge with load going on Status

Re: [Qemu-devel] [Bug 1689499] Re: copy-storage-all/inc does not easily converge with load going on

On Tue, May 9, 2017 at 12:41 PM, Dr. David Alan Gilbert wrote: > Interesting. > That's quite a big difference, so if you could bisect it down it would be > interesting to figure out where the change occurred. > Hi David, if it turns out to stay reproducible enough I can

[Qemu-devel] [Bug 1689499] Re: copy-storage-all/inc does not easily converge with load going on

Interesting. That's quite a big difference, so if you could bisect it down it would be interesting to figure out where the change occurred. What happens if you just make it a 'disk' workload without the memory stress? What network interface (1G/10G etc) are you migrating over and what bandwidth