From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Hoffmann Subject: Re: Qxl problem with xen domU, is xen spice and/or qemu bugs? Date: Tue, 24 Sep 2013 13:50:04 +0200 Message-ID: <1380023404.3918.33.camel@nilsson.home.kraxel.org> References: <524173CB.5000203@m2r.biz> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <524173CB.5000203@m2r.biz> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org To: Fabio Fantoni Cc: xen-devel , Ian Campbell , Stefano Stabellini , George Dunlap , "qemu-devel@nongnu.org" , Jan Beulich , Anthony PERARD , spice-devel@lists.freedesktop.org List-Id: xen-devel@lists.xenproject.org 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