Re: [Xen-devel] [TestDay] F20 Xen 4.4 RC3 Spice support

[Fabio Fantoni <fabio.fantoni@xxxxxxx>]

Il 07/02/2014 10:08, Dario Faggioli ha scritto:
> On gio, 2014-02-06 at 08:35 +0100, Fabio Fantoni wrote:
> > 2014-02-06 5:23 GMT+01:00 Eric Houby <ehouby@xxxxxxxxx>:
> >          Is there a knob for qxl support?
> >          
> >          [root@xen ~]# cat /var/log/xen/qemu-dm-f20.log
> >          qemu-system-i386: -vga qxl: invalid option
> >
> >
> > Here there is a patch that add qxl support in libxl updated to xen
> > 4.4-rc3 if you want add it:
> > https://github.com/Fantu/Xen/commit/f1e3f78f7b9580700591cebd98e9263645bff56b
> >
> > Or you can simply compile from this already ready for spice/qxl
> > testing:
> > https://github.com/Fantu/Xen/commits/rebase/m2r-testing
> >
> >
> >
> > Is not upstream for now because there is something on xen that make it
> > not working on linux domUs with qxl driver active and working with
> > high performance problem on windows domUs.
> Right.
>
> > I spent several days without finding the exact problem to be solved :(
> > If you want you can try it out and see if anything changes using
> > Fedora instead of Debian as dom0, differents kernel domUs etc.
> > Maybe you could even find some new informations/errors useful for
> > solving the problem.
> Yep, that would help... let us know! :-)
>
> Anyway, first of all, sorry for my spice/qxl ignorance.
>
> What I just wanted to say is this: searching the wiki, all I found about
> spice and QXL is this section in the QEMU Upstream page:
> http://wiki.xen.org/wiki/QEMU_Upstream#SPICE_.2F_QXL
>
> Perhaps someone of you can double check whether the information there is
> still fresh and accurate enough? Perhaps it's also worth adding
> references to the patches mentioned above (with the proper disclaimer
> about the known issues, of course)?
>
> Also, maybe for the next DocsDay, this would be a nice one to have too:
> http://wiki.xen.org/wiki/Xen_Document_Days/TODO#Spice_Config_Example_for_upstream_QEMU
>
> If keen on doing any of the above that involves modifying the wiki, send
> me a note, and I think I can provide the necessary permissions.
The wiki should be updated, the qxl patch for libxl part is complete and 
correct and can be used for tests:
https://github.com/Fantu/Xen/commit/f1e3f78f7b9580700591cebd98e9263645bff56b
the actual problem is off of libxl.
Probably are on hvmloader, qemu and/or kernel.

The latest mail about qxl problem that I send:
http://lists.xen.org/archives/html/xen-devel/2013-12/msg00758.html

Shortly in the latest tests I have got:
- on windows 7 domU with xen_platform_pci=0 the worse video refresh 
performance with qxl seems was "solved" but unfortunately is a problem 
without pv drivers (neeeded for xl save/restore/shutdown).
- on Saucy (ubuntu 13.10) domU with "xen/pvhvm: If xen_platform_pci=0 is 
set don't blow up" patch even with xen_platform_pci=0 I got a 100% cpu 
X.org and black screen. So there is probably another problem on linux 
domUs kernel-side and/or xorg's qxl drivers.
- on Fedora19 domU, comparing kvm and xen hosts the only difference I 
have found is the following error in /var/log/messages:
> ioremap error for 0xfc001000-0xfc002000, requested 0x10, got 0x0
There also this from old tests:
> And about xen hypervisor logs (with xl dmesg) the only difference 
> between stdvga and qxl (same domU) is that qxl log has 3 "pci dev bar" 
> more.
Which may be useful to understand if further hvmloader modification are 
needed.
I have not knowledge about it to say anything certain.

If someone want help me, please reply if further tests/data needed and 
I'll post them.
Thanks for any reply.

> Thanks and Regards,
> Dario

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel