From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:59434) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WmhF5-00030h-Qs for qemu-devel@nongnu.org; Tue, 20 May 2014 06:26:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WmhEz-0007mE-NV for qemu-devel@nongnu.org; Tue, 20 May 2014 06:25:55 -0400 Received: from mx1.redhat.com ([209.132.183.28]:21969) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WmhEz-0007m9-GK for qemu-devel@nongnu.org; Tue, 20 May 2014 06:25:49 -0400 Message-ID: <1400581536.29693.12.camel@nilsson.home.kraxel.org> From: Gerd Hoffmann Date: Tue, 20 May 2014 12:25:36 +0200 In-Reply-To: <33183CC9F5247A488A2544077AF19020815E8F5E@SZXEMA503-MBS.china.huawei.com> References: <33183CC9F5247A488A2544077AF19020815E8148@SZXEMA503-MBS.china.huawei.com> <1399987647.7118.63.camel@nilsson.home.kraxel.org> <33183CC9F5247A488A2544077AF19020815E873D@SZXEMA503-MBS.china.huawei.com> <537344AD.3030000@redhat.com> <33183CC9F5247A488A2544077AF19020815E8DBC@SZXEMA503-MBS.china.huawei.com> <1400136613.2922.21.camel@nilsson.home.kraxel.org> <33183CC9F5247A488A2544077AF19020815E8F5E@SZXEMA503-MBS.china.huawei.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] usb: usb tablet freeze when save/restore guest os List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Gonglei (Arei)" Cc: Paolo Bonzini , "xen-devel@lists.xen.org" , "Huangweidong (C)" , "qemu-devel@nongnu.org" , "Michael S. Tsirkin" Hi, > As for Xen, It's too later. After suspend vm, the qemu process can response the event > of usb tablet event. Because guest os's vcpus are paused, guest os cannot response > interrupt injected by qemu. Then the interrupt will be lost. When the guest can't handle the interrupt (due to being stopped) it should continue to be tagged pending in the ioapic. And this should be migrated over with the ioapic state, so the guest should receive and handle the interrupt after being restarted to the target machine. IIRC ioapic migration works differently in kvm and xen. Maybe you've hit a xen live migration bug. cheers, Gerd