From: Fabio Fantoni <fabio.fantoni@m2r.biz>
To: xen-devel@lists.xen.org
Cc: Anthony PERARD <anthony.perard@citrix.com>,
Jan Beulich <JBeulich@suse.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Xen domUs seem unable to use one qxl memory bar
Date: Wed, 24 Feb 2016 16:44:31 +0100 [thread overview]
Message-ID: <56CDCFDF.8040303@m2r.biz> (raw)
Today I was trying a newer version of qxl driver on windows 10 domU (on
dom0 with xen 4.6) and I got a windows blue screen about the updated driver.
On latest xl dmesg line I found this error which I suppose is related:
> (XEN) memory.c:161:d0v0 Could not allocate order=18 extent: id=53
> memflags=0 (0 of 1)
Checking the few commits added in the latest update I found this one:
https://cgit.freedesktop.org/~teuf/qxl-wddm-dod/commit/?id=5df8c4f318d808a8381a948da3ce15b5d4aa6682
Here it starts to use the second qxl memory bar which was unused before
in windows qxl drivers FWIK.
This additional memory bar is not present in stdvga and if I remember
correctly when I started to try qxl vga some years ago I was not able to
boot the domUs at all for one or more problem about memory, solved by
Jan Beulich and/or Anthony Perard.
After such fixes qxl was usable, now I use it even in production windows
domUs with monitor resolution up to 1920x1080.
Can someone tell me if the second qxl memory bar is really "unusable" or
something, please?
If yes how can it be solved?
If you need more information/tests tell me and I'll post them.
Thanks for any reply and sorry for my bad english.
next reply other threads:[~2016-02-24 15:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 15:44 Fabio Fantoni [this message]
2016-03-07 15:00 ` Xen domUs seem unable to use one qxl memory bar 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=56CDCFDF.8040303@m2r.biz \
--to=fabio.fantoni@m2r.biz \
--cc=JBeulich@suse.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=anthony.perard@citrix.com \
--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).