From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54739) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XUy3H-0005Bs-NZ for qemu-devel@nongnu.org; Fri, 19 Sep 2014 09:16:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XUy3C-0001V7-E6 for qemu-devel@nongnu.org; Fri, 19 Sep 2014 09:16:43 -0400 Received: from mail-we0-f169.google.com ([74.125.82.169]:43251) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XUy3C-0001Tb-5O for qemu-devel@nongnu.org; Fri, 19 Sep 2014 09:16:38 -0400 Received: by mail-we0-f169.google.com with SMTP id w61so2478041wes.14 for ; Fri, 19 Sep 2014 06:16:32 -0700 (PDT) Message-ID: <541C2D39.1060607@m2r.biz> Date: Fri, 19 Sep 2014 15:18:49 +0200 From: Fabio Fantoni MIME-Version: 1.0 References: <53BBA83C.3010307@m2r.biz> <1404809604.30343.5.camel@cihla.spice.brq.redhat.com> <53BBC2AA.4030503@m2r.biz> <53BBC952.1040902@m2r.biz> <54130761.6080501@m2r.biz> In-Reply-To: <54130761.6080501@m2r.biz> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [Qemu-devel] [Spice-devel] screen freezed for 2-3 minutes on spice connect on xen windows 7 domU's with qxl after save/restore List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: xen-devel , "qemu-devel@nongnu.org" , spice-devel@lists.freedesktop.org Cc: Jan Beulich Il 12/09/2014 16:46, Fabio Fantoni ha scritto: > Il 08/07/2014 12:34, Fabio Fantoni ha scritto: >> Il 08/07/2014 12:06, Fabio Fantoni ha scritto: >>> Il 08/07/2014 10:53, David Jaša ha scritto: >>>> Hi, >>>> >>>> On Út, 2014-07-08 at 10:13 +0200, Fabio Fantoni wrote: >>>>> On xen 4.5 (tried with qemu 2.0.0/2.1-rc0, spice 0.12.5 and client >>>>> with >>>>> spice-gtk 0.23/0.25) windows 7 domUs with qxl vga works good as kvm >>>>> except for one problem after xl save/restore, when after restore on >>>>> spice client connect the domU's screen freezed for 2-3 minutes (and >>>>> seems also windows), after this time seems that all return to works >>>>> correctly. >>>>> This problem happen also if spice client connect long time after >>>>> restore. >>>>> With stdvga not have this problem but stdvga has many missed >>>>> resolutions >>>>> and bad refresh performance. >>>>> >>>>> If you need more tests/informations tell me and I'll post them. >>>> Client and server logs would certainly help. Please run: >>>> * virt-viewer with --spice-debug option >>>> * spice-server with SPICE_DEBUG_LEVEL environment variable set >>>> to 4 or 5 (if you use qemu+libvirt, use qemu:env element: >>>> http://libvirt.org/drvqemu.html#qemucommand ) >>>> and note the location in the logs where the freeze takes place. >>>> >>>> Regards, >>>> >>>> David >>> >>> Thanks for your reply, in attachments: >>> - domU's xl cfg: W7.cfg >>> - xl -vvv create/save/restore: xen logs.txt >>> - remote-viewer with --spice-debug after domU's start until xl save: >>> spicelog-1.txt (zipped) >>> - remote-viewer with --spice-debug after domU's xl restore: >>> spicelog-2.txt >> >> Sorry for my forgetfulness, here also qemu's log: >> - after domU's start until xl save: qemu-dm-W7.log.1 >> - after domU's xl restore: qemu-dm-W7.log >> >>> >>> If you need more tests/informations tell me and I'll post them. >>> >>> >>>> Thanks for any reply and sorry for my bad english. >>>> >>>> _______________________________________________ >>>> Spice-devel mailing list >>>> Spice-devel@lists.freedesktop.org >>>> http://lists.freedesktop.org/mailman/listinfo/spice-devel >> > > The problem persist, this time I saw these in xl dmesg after restore: > > (XEN) HVM2 restore: CPU 0 > (XEN) HVM2 restore: CPU 1 > (XEN) HVM2 restore: PIC 0 > (XEN) HVM2 restore: PIC 1 > (XEN) HVM2 restore: IOAPIC 0 > (XEN) HVM2 restore: LAPIC 0 > (XEN) HVM2 restore: LAPIC 1 > (XEN) HVM2 restore: LAPIC_REGS 0 > (XEN) HVM2 restore: LAPIC_REGS 1 > (XEN) HVM2 restore: PCI_IRQ 0 > (XEN) HVM2 restore: ISA_IRQ 0 > (XEN) HVM2 restore: PCI_LINK 0 > (XEN) HVM2 restore: PIT 0 > (XEN) HVM2 restore: RTC 0 > (XEN) HVM2 restore: HPET 0 > (XEN) HVM2 restore: PMTIMER 0 > (XEN) HVM2 restore: MTRR 0 > (XEN) HVM2 restore: MTRR 1 > (XEN) HVM2 restore: VIRIDIAN_DOMAIN 0 > (XEN) HVM2 restore: VIRIDIAN_VCPU 0 > (XEN) HVM2 restore: VIRIDIAN_VCPU 1 > (XEN) HVM2 restore: VMCE_VCPU 0 > (XEN) HVM2 restore: VMCE_VCPU 1 > (XEN) HVM2 restore: TSC_ADJUST 0 > (XEN) HVM2 restore: TSC_ADJUST 1 > (XEN) memory.c:216:d2v0 Domain 2 page number 77579 invalid > (XEN) memory.c:216:d2v0 Domain 2 page number 7757a invalid > (XEN) memory.c:216:d2v0 Domain 2 page number 7757b invalid > (XEN) memory.c:216:d2v0 Domain 2 page number 7757c invalid > (XEN) memory.c:216:d2v0 Domain 2 page number 7757d invalid > (XEN) memory.c:216:d2v0 Domain 2 page number 7757e invalid > (XEN) memory.c:216:d2v0 Domain 2 page number 7757f invalid > (XEN) memory.c:216:d2v0 Domain 2 page number 77580 invalid > (XEN) memory.c:216:d2v0 Domain 2 page number 77581 invalid > (XEN) memory.c:216:d2v0 Domain 2 page number 77582 invalid > (XEN) memory.c:216:d2v0 Domain 2 page number 77583 invalid > (XEN) memory.c:216:d2v0 Domain 2 page number 77584 invalid > (XEN) memory.c:216:d2v0 Domain 2 page number 77585 invalid > (XEN) memory.c:216:d2v0 Domain 2 page number 77586 invalid > (XEN) memory.c:216:d2v0 Domain 2 page number 77587 invalid > (XEN) memory.c:216:d2v0 Domain 2 page number 77588 invalid > (XEN) memory.c:216:d2v0 Domain 2 page number 77589 invalid > (XEN) memory.c:216:d2v0 Domain 2 page number 7758a invalid > (XEN) memory.c:216:d2v0 Domain 2 page number 7758b invalid > (XEN) memory.c:216:d2v0 Domain 2 page number 7758c invalid > (XEN) memory.c:216:d2v0 Domain 2 page number 7758d invalid > (XEN) memory.c:216:d2v0 Domain 2 page number 7758e invalid > (XEN) memory.c:216:d2v0 Domain 2 page number 7758f invalid > (XEN) memory.c:216:d2v0 Domain 2 page number 77590 invalid > (XEN) memory.c:216:d2v0 Domain 2 page number 77591 invalid > (XEN) memory.c:216:d2v0 Domain 2 page number 77592 invalid > (XEN) memory.c:216:d2v0 Domain 2 page number 77593 invalid > (XEN) memory.c:216:d2v0 Domain 2 page number 77594 invalid > (XEN) memory.c:216:d2v0 Domain 2 page number 77595 invalid > (XEN) memory.c:216:d2v0 Domain 2 page number 77596 invalid > (XEN) memory.c:216:d2v0 Domain 2 page number 77597 invalid > (XEN) memory.c:216:d2v0 Domain 2 page number 77598 invalid > (XEN) grant_table.c:1272:d2v0 Expanding dom (2) grant table from (4) > to (32) frames. > (XEN) irq.c:380: Dom2 callback via changed to GSI 24 > > Tested on latest staging (commit > 7d203b337fb2dcd148d2df850e25b67c792d4d0b) plus the spice patches: > https://github.com/Fantu/Xen/commits/rebase/m2r-staging > > If you need more informations or tests tell me and I'll post them. > Thanks for any reply and sorry for my bad english. I did another tests updating to latest git staging (commit 3e2331d271cc0882e4013c8f20398c46c35f90a1) and is nomore problem of "only" 2-3 minutes but now when it appears to restart (after 2-3 minutes) windows domUs undefinitely hangs instead. No further details in xen and domU's logs. If you need more tests/details tell me and I'll do them. Thanks for any reply.