[Spice-devel] screen freezed for 2-3 minutes on spice connect on xen windows 7 domU's with qxl after save/restore

[Fabio Fantoni]

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 at 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.