xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Anthony PERARD <anthony.perard@citrix.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: Fabio Fantoni <fabio.fantoni@heliman.it>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen 4.3 development update RC2 imminent
Date: Tue, 21 May 2013 15:06:31 +0100	[thread overview]
Message-ID: <519B7F67.2050602@citrix.com> (raw)
In-Reply-To: <CAFLBxZZTosUM9_LadwHxCgSi6yoADxWYfVA1XYFnYtO=iG0Yhw@mail.gmail.com>

On 20/05/13 11:33, George Dunlap wrote:
> * qxl not actually working
>   > qxl apparently not enabled during compile by default
>   > Appear to be some other bugs even when it is working:
>   >   http://lists.xen.org/archives/html/xen-devel/2012-11/msg00713.html
>   owner: ? (Anthony was going to take a look)
>   We need to either fix both of these problems or disable qxl for 4.3

I've been able to track down this error:
> Spice-CRITICAL **: red_memslots.c:123:get_virt: slot_id 194 too big,
addr=c2c2c2c2c2c2c2c2

This little patch fix it:
diff --git a/hw/qxl.c b/hw/qxl.c
index 96887c4..db2e02e 100644
--- a/hw/qxl.c
+++ b/hw/qxl.c
@@ -390,6 +390,7 @@ static void init_qxl_ram(PCIQXLDevice *d)
     d->ram->int_pending = cpu_to_le32(0);
     d->ram->int_mask    = cpu_to_le32(0);
     d->ram->update_surface = 0;
+    d->ram->monitors_config = 0;
     SPICE_RING_INIT(&d->ram->cmd_ring);
     SPICE_RING_INIT(&d->ram->cursor_ring);
     SPICE_RING_INIT(&d->ram->release_ring);

But then, once this applied, qxl is still not able to start. Xorg crash
(in the guest), and here is why:

(XEN) emulate.c:88:d18 bad mmio size 16
(XEN) io.c:201:d18 MMIO emulation failed @ 0033:7fd2de390430: f3 0f 6f
19 41 83 e8 403
(XEN) emulate.c:88:d18 bad mmio size 16
(XEN) io.c:201:d18 MMIO emulation failed @ 0033:7fd2de390430: f3 0f 6f
19 41 83 e8 403

The backtrace of X:
(EE) 0: /usr/bin/X (xorg_backtrace+0x3d) [0x57f48d]
(EE) 1: /usr/bin/X (0x400000+0x1831e9) [0x5831e9]
(EE) 2: /usr/lib/libpthread.so.0 (0x7fd2de7c0000+0xf0e0) [0x7fd2de7cf0e0]
(EE) 3: /usr/lib/libpixman-1.so.0 (0x7fd2de300000+0x90430) [0x7fd2de390430]
(EE) 4: /usr/lib/libpixman-1.so.0 (0x7fd2de300000+0x9066b) [0x7fd2de39066b]
(EE) 5: /usr/lib/libpixman-1.so.0 (pixman_image_composite32+0x481)
[0x7fd2de30bb01]
(EE) 6: /usr/lib/xorg/modules/drivers/qxl_drv.so (0x7fd2dc260000+0x9345)
[0x7fd2dc269345]
(EE) 7: /usr/lib/xorg/modules/drivers/qxl_drv.so (0x7fd2dc260000+0xa1c7)
[0x7fd2dc26a1c7]
(EE) 8: /usr/lib/xorg/modules/drivers/qxl_drv.so (0x7fd2dc260000+0xeb1f)
[0x7fd2dc26eb1f]
(EE) 9: /usr/lib/xorg/modules/drivers/qxl_drv.so
(0x7fd2dc260000+0x11ecf) [0x7fd2dc271ecf]
(EE) 10: /usr/bin/X (0x400000+0x170353) [0x570353]
(EE) 11: /usr/bin/X (0x400000+0xc0b95) [0x4c0b95]
(EE) 12: /usr/bin/X (0x400000+0x34726) [0x434726]
(EE) 13: /usr/bin/X (0x400000+0x3721e) [0x43721e]
(EE) 14: /usr/bin/X (0x400000+0x26895) [0x426895]
(EE) 15: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7fd2dd621a15]
(EE) 16: /usr/bin/X (0x400000+0x26bdd) [0x426bdd]
(EE)
(EE) Segmentation fault at address 0x0

So I giving up on this issue for now. So I think we can disable "vga = qxl".

-- 
Anthony PERARD

  parent reply	other threads:[~2013-05-21 14:06 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-20 10:33 Xen 4.3 development update RC2 imminent George Dunlap
2013-05-20 10:36 ` George Dunlap
2013-05-20 17:12   ` Keir Fraser
2013-05-21  8:13     ` Tim Deegan
2013-05-21 10:22       ` Jan Beulich
2013-05-21  8:19   ` Jan Beulich
2013-05-21  8:22     ` George Dunlap
2013-05-21  8:25       ` Jan Beulich
2013-05-20 10:51 ` Wei Liu
2013-05-20 11:09   ` George Dunlap
2013-05-20 11:16     ` Ian Campbell
2013-05-20 11:32       ` George Dunlap
2013-05-20 11:46         ` Ian Campbell
2013-05-20 13:42           ` George Dunlap
2013-05-20 11:15   ` Ian Campbell
2013-05-20 11:22 ` George Dunlap
2013-05-20 11:26 ` Ian Campbell
2013-05-20 11:28   ` George Dunlap
2013-05-20 11:48     ` Ian Campbell
2013-05-21 14:06 ` Anthony PERARD [this message]
2013-05-21 14:31   ` Andrew Cooper
2013-05-21 14:49     ` George Dunlap
2013-05-21 14:55     ` Jan Beulich
2013-05-21 14:58       ` Andrew Cooper
2013-05-21 15:07         ` Jan Beulich
2013-05-21 16:13       ` George Dunlap
2013-05-21 16:16         ` George Dunlap
2013-05-22 12:49           ` Fabio Fantoni
2013-05-22 12:58             ` Andrew Cooper
2013-05-22 15:05             ` George Dunlap
2013-05-22 16:30               ` Pasi Kärkkäinen
2013-05-22 16:54                 ` George Dunlap
2013-05-23  7:39                   ` Jan Beulich
2013-05-23 10:36                     ` Fabio Fantoni
2013-05-23 10:39                       ` Andrew Cooper
2013-05-23 10:54                         ` George Dunlap
2013-05-23 14:17                           ` Fabio Fantoni
2013-05-23 14:26                             ` George Dunlap
2013-05-23 14:35                               ` George Dunlap
2013-05-23 14:58                               ` Fabio Fantoni
2013-05-23 15:10                                 ` Pasi Kärkkäinen
2013-05-23 16:10                                   ` George Dunlap
2013-05-23 16:07                                 ` George Dunlap
2013-05-24 13:56                                   ` Fabio Fantoni
2013-05-24 13:59                                     ` George Dunlap
2013-05-24 14:53                                       ` Fabio Fantoni
2013-05-24 15:52                                         ` George Dunlap
2013-05-23 14:32                             ` George Dunlap
2013-05-23 10:48                       ` Jan Beulich
2013-05-23 10:31                   ` Fabio Fantoni
2013-05-23 14:01                     ` Pasi Kärkkäinen
2013-05-22 12:48   ` 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=519B7F67.2050602@citrix.com \
    --to=anthony.perard@citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=fabio.fantoni@heliman.it \
    --cc=xen-devel@lists.xen.org \
    /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).