xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Fabio Fantoni <fabio.fantoni@m2r.biz>
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: Qxl problem with xen domU, is xen spice and/or qemu bugs?
Date: Tue, 24 Sep 2013 13:50:04 +0200	[thread overview]
Message-ID: <1380023404.3918.33.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <524173CB.5000203@m2r.biz>

  Hi,

> Someone can help me to find the problem that makes qxl unusable please?

#1 git cherry-pick c58c7b959b93b864a27fd6b3646ee1465ab8832b

#2 When using f19 try without X11 first.  You should have a working
   framebuffer console on qxldrmfb before trying to get X11 going.

#3 qxl has a bunch of tracepoints.  Enable them, then compare xen
   results with kvm/tcg results to see where things start going wrong.

#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

  reply	other threads:[~2013-09-24 11:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-24 11:13 Qxl problem with xen domU, is xen spice and/or qemu bugs? Fabio Fantoni
2013-09-24 11:50 ` Gerd Hoffmann [this message]
2013-09-26 10:28   ` Fabio Fantoni
2013-09-26 13:04     ` Fabio Fantoni
2013-09-27  8:51       ` [Qemu-devel] " Gerd Hoffmann
2013-09-27 13:53         ` Fabio Fantoni
2013-10-01 12:52           ` [Qemu-devel] " 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=1380023404.3918.33.camel@nilsson.home.kraxel.org \
    --to=kraxel@redhat.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=fabio.fantoni@m2r.biz \
    --cc=ian.campbell@citrix.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).