From: Fabio Fantoni <fabio.fantoni@m2r.biz>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Jan Beulich <JBeulich@suse.com>,
Anthony PERARD <anthony.perard@citrix.com>,
spice-devel@lists.freedesktop.org
Subject: Re: [Qemu-devel] Qxl problem with xen domU, is xen spice and/or qemu bugs?
Date: Thu, 26 Sep 2013 12:28:24 +0200 [thread overview]
Message-ID: <52440C48.4010702@m2r.biz> (raw)
In-Reply-To: <1380023404.3918.33.camel@nilsson.home.kraxel.org>
[-- Attachment #1: Type: text/plain, Size: 2027 bytes --]
Il 24/09/2013 13:50, Gerd Hoffmann ha scritto:
> Hi,
>
>> Someone can help me to find the problem that makes qxl unusable please?
> #1 git cherry-pick c58c7b959b93b864a27fd6b3646ee1465ab8832b
Thanks for reply, did this on my new test build.
>
> #2 When using f19 try without X11 first. You should have a working
> framebuffer console on qxldrmfb before trying to get X11 going.
I tried on Fedora19 minimal installation and with qxl the text console
is working and lsmod show also qxl.
Is this your intended or is there something else I must test before X11?
>
> #3 qxl has a bunch of tracepoints. Enable them, then compare xen
> results with kvm/tcg results to see where things start going wrong.
I enabled qxl debug with these qemu paramters:
-global qxl-vga.debug=1 -global qxl-vga.guestdebug=20
With Fedora19 I have some difficult to found exact problem and compare
with kvm.
I tried to test Fedora19 on debian sid kvm host same qemu version (1.6)
on both sides but with qxl fails to start the DE, also in fallback mode.
Probably there are also regression on qemu and/or spice about qxl.
The qemu log returns nothing relevant with only few lines on xen test
with also qxl debug enabled.
I tried also W7 domU on xen with spice-guest-tools-0.65.exe and qxl:
domU starts, loads correctly the DE, vdagent and mouse are both working,
but screen refreshing is very lagging (also only open of start menu).
The qemu log become of 22 mb in only few minutes, mainly qxl debug.
Can you check the W7 qemu log on attachment to see if there are strange
things to solve also on spice and/or qemu?
Thanks for any reply.
>
> #4 qxl needs a permanent mapping of the two pci memory bars as the
> (host virtual) memory location of these bars is passed to the
> spice-server library. That might need some special care on xen
> due to the mapcache. Disclamer: It's been a few years I looked
> closer at this, so things in the xen world might have changed
> meanwhile ...
>
> HTH,
> Gerd
>
>
[-- Attachment #2: qemu-dm-W7.7z --]
[-- Type: application/octet-stream, Size: 2166051 bytes --]
next prev parent reply other threads:[~2013-09-26 10:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 11:13 [Qemu-devel] Qxl problem with xen domU, is xen spice and/or qemu bugs? Fabio Fantoni
2013-09-24 11:50 ` Gerd Hoffmann
2013-09-26 10:28 ` Fabio Fantoni [this message]
2013-09-26 13:04 ` Fabio Fantoni
2013-09-27 8:51 ` Gerd Hoffmann
2013-09-27 13:53 ` Fabio Fantoni
2013-10-01 12:52 ` Fabio Fantoni
2013-12-04 16:10 ` Fabio Fantoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52440C48.4010702@m2r.biz \
--to=fabio.fantoni@m2r.biz \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=anthony.perard@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=spice-devel@lists.freedesktop.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).