From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53100) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YL807-00020x-PE for qemu-devel@nongnu.org; Tue, 10 Feb 2015 05:25:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YL804-0002EG-Jo for qemu-devel@nongnu.org; Tue, 10 Feb 2015 05:25:03 -0500 Received: from mx-v6.kamp.de ([2a02:248:0:51::16]:50090 helo=mx01.kamp.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YL804-0002Dt-8c for qemu-devel@nongnu.org; Tue, 10 Feb 2015 05:25:00 -0500 Message-ID: <54D9DC74.1020502@kamp.de> Date: Tue, 10 Feb 2015 11:24:52 +0100 From: Peter Lieven MIME-Version: 1.0 References: <54D9CEC9.9040902@kamp.de> <54D9D421.10907@redhat.com> <54D9D765.4040805@kamp.de> <54D9DACD.9020704@redhat.com> In-Reply-To: <54D9DACD.9020704@redhat.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] kvmclock_current_nsec: Assertion `time.tsc_timestamp <= migration_tsc' List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini , "qemu-devel@nongnu.org" Cc: mtosatti@redhat.com, agraf@suse.de Am 10.02.2015 um 11:17 schrieb Paolo Bonzini: > > On 10/02/2015 11:03, Peter Lieven wrote: >> My hope was that anyone has observed this post 2.2.0 already and there >> is a fix available ;-) >> >> Can you indicate what info would be helpful debugging this? >> >> Cmdline is: >> /usr/bin/qemu-2.2.0 -enable-kvm -M pc-i440fx-2.1 -nodefaults -netdev >> type=tap,id=guest19,script=no,downscript=no,ifname=tap19,vnet_hdr >> -device virtio-net-pci,netdev=guest19,mac=52:54:00:80:00:55 -netdev >> type=tap,id=guest20,script=no,downscript=no,ifname=tap20,vnet_hdr >> -device virtio-net-pci,netdev=guest20,mac=52:54:00:80:00:6f -netdev >> type=tap,id=guest21,script=no,downscript=no,ifname=tap21,vnet_hdr >> -device virtio-net-pci,netdev=guest21,mac=52:54:00:80:00:75 -serial >> null -parallel null -m 496 -monitor tcp:0:4011,server,nowait -vnc :11 >> -qmp tcp:0:3011,server,nowait -name 'gw-5000123' -boot >> order=nc,menu=on -drive >> index=2,media=cdrom,if=ide,cache=unsafe,aio=native,readonly=on -k de >> -incoming tcp:0:5011 -pidfile /var/run/qemu/vm-115.pid -mem-path >> /hugepages -mem-prealloc -rtc base=utc -usb -usbdevice tablet -no-hpet >> -vga vmware -cpu qemu64 > First of all (but unrelated to the bug) do not use "-cpu qemu64" with KVM. I remember there was an issue with kvm64 anytime in the past, but this is ages ago I think. I will change that for new vserver starts. What (which flag) is the exact issue with qemu64 vs. kvm64 > > Second, what downtime or bandwidth setting? What is the actual > downtime? Can you print time.tsc_timestamp and migration_tsc on the > destination? From my logs: migrate_set_speed 1200M migrate_set_capability auto-converge on migrate_set_capability xbzrle off The max_downtime was default. I will add debugging output around that assertion and try to reproduce. Thank you, Peter