From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:42760) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aO6gK-0005hN-AA for qemu-devel@nongnu.org; Tue, 26 Jan 2016 11:41:29 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aO6gH-0004NK-JB for qemu-devel@nongnu.org; Tue, 26 Jan 2016 11:41:28 -0500 Received: from mail5.windriver.com ([192.103.53.11]:34842 helo=mail5.wrs.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aO6gH-0004Ip-BE for qemu-devel@nongnu.org; Tue, 26 Jan 2016 11:41:25 -0500 Message-ID: <56A7A1A8.4060704@windriver.com> Date: Tue, 26 Jan 2016 10:41:12 -0600 From: Chris Friesen MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] high outage times for qemu virtio network links during live migration, trying to debug List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: libvir-list@redhat.com, qemu-devel@nongnu.org Hi, I'm using libvirt (1.2.12) with qemu (2.2.0) in the context of OpenStack. If I live-migrate a guest with virtio network interfaces, I see a ~1200msec delay in processing the network packets, and several hundred of them get dropped. I get the dropped packets, but I'm not sure why the delay is there. I instrumented qemu and libvirt, and the strange thing is that this delay seems to happen before qemu actually starts doing any migration-related work. (i.e. before qmp_migrate() is called) Looking at my timestamps, the start of the glitch seems to coincide with libvirtd calling qemuDomainMigratePrepareTunnel3Params(), and the end of the glitch occurs when the migration is complete and we're up and running on the destination. My question is, why doesn't qemu continue processing virtio packets while the dirty page scanning and memory transfer over the network is proceeding? Thanks, Chris (Please CC me on responses, I'm not subscribed to the lists.)