xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Fabio Fantoni <fantonifabio@tiscali.it>
To: ZhouPeng <zpengxen@gmail.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	"Keir (Xen.org)" <keir@xen.org>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: Unable to get QXL vga working
Date: Mon, 11 Jun 2012 13:56:39 +0200	[thread overview]
Message-ID: <4FD5DCF7.2070103@tiscali.it> (raw)
In-Reply-To: <CAAh7U5O3HMmRbUVEY1iUUt3wvU=a1ZyoAC5vzYg5su9+Y_ALwg@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2072 bytes --]

Il 24/05/2012 13:28, ZhouPeng ha scritto:
> On Thu, May 24, 2012 at 6:13 PM, Stefano Stabellini
> <stefano.stabellini@eu.citrix.com>  wrote:
>> On Thu, 24 May 2012, ZhouPeng wrote:
>>> Sorry for late reply, I am not on this mail these days because of my work.
>>>
>>> I further test qxl-vga and I think I figure out the problem in some extend.
>>>
>>> If using qxl device, the default memory size of vga is 64M.
>>> Which will cause xen_ram_alloc(qemu/xen-all.c) fails.
>>>
>>> The exact reason is xc_domain_populate_physmap_exact fails, because
>>> xen-hypervisor
>>> fail,
>>> it's because of   alloc_domheap_pages(d, a->extent_order, a->memflags)
>>> fails in hypervisor.
>>>
>>> I am not very familiar with xen's memory management, Does 64M exceed
>>> xen's heap space in this context?
>> XL sets an upper bound of memory that can be allocated to the VM in
>> libxl__build_pre, calling xc_domain_setmaxmem.
>> My guess is that a 64MB allocation would go over that limit.
>> You could try increasing the limit manually changing the
>> xc_domain_setmaxmem call in libxl__build_pre, or you could try setting
>> videoram=64 in the VM config file.
> Your guess is absolutely right!
>
> But set videoram=128 or
> xc_domain_setmaxmem(ctx->xch, domid, info->target_memkb +
> LIBXL_MAXMEM_CONSTANT + 2 * 64 * 1024);
>
> Then I successfuly install qxl driver in win-hvm and QXL can work properly.
>
> I will send some patch to add qxl support to libxl.
I tried your 3 patches taken from the mailing list, it works but doesn't 
solve qxl problems for me, on linux domU (Precise and Wheezy) xorg 
doesn't start and on windows 7 I have heavy performance problem (unusable).
I tried also with qemu 1.1.0 but nothing change.
Does it work correctly for you? If so can I have some detail of your 
configurations please?
For audio support this is needed too: (tested and working)
-device intel-hda,id=sound0 -device hda-duplex,id=sound0-codec0 on qemu 
invocation and env QEMU_AUDIO_DRV=spice
Can you add audio support on libxl please?




[-- Attachment #1.2: Firma crittografica S/MIME --]
[-- Type: application/pkcs7-signature, Size: 4497 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2012-06-11 11:56 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-26 15:23 Unable to get QXL vga working Fantu
2012-04-26 15:39 ` Ian Campbell
2012-04-27  5:15   ` ZhouPeng
2012-04-27  9:23     ` Fantu
2012-05-02  8:21     ` Fantu
2012-05-03 11:31       ` ZhouPeng
2012-05-03 12:28         ` Fantu
2012-05-03 14:00           ` Unable to get QXL vga working / videomem over 4MB issue Pasi Kärkkäinen
2012-05-03 14:27             ` Fantu
2012-05-03 16:02               ` Pasi Kärkkäinen
2012-05-04  8:23                 ` Fantu
2012-05-04  8:28                   ` Ian Campbell
2012-05-04  8:56                     ` Fantu
2012-05-04 11:21                     ` Anthony PERARD
2012-05-04 11:32                       ` Ian Campbell
2012-05-08 16:24                         ` Pasi Kärkkäinen
2012-05-08 19:15                           ` Ian Campbell
2012-05-09 14:07                             ` Fantu
2012-05-09 16:01                               ` Anthony PERARD
2012-05-04 12:02                       ` Fantu
2012-05-07 15:01                         ` Fantu
2012-05-11 12:19                       ` Geraldes
2012-05-11 13:00                         ` Anthony PERARD
2012-05-03 12:46         ` Unable to get QXL vga working Stefano Stabellini
2012-05-03 12:56           ` ZhouPeng
2012-05-03 13:05             ` Stefano Stabellini
2012-05-03 13:05               ` ZhouPeng
2012-05-03 13:13                 ` Ian Campbell
2012-05-03 13:27                   ` ZhouPeng
2012-05-03 13:56                 ` Stefano Stabellini
2012-05-04  1:15                   ` ZhouPeng
2012-05-04  8:30                     ` Ian Campbell
2012-05-24  3:13                       ` ZhouPeng
2012-05-24 10:13                         ` Stefano Stabellini
2012-05-24 11:28                           ` ZhouPeng
2012-06-11 11:56                             ` Fabio Fantoni [this message]
2012-06-13  9:02                               ` ZhouPeng
2012-06-13  9:38                                 ` Fabio Fantoni
2012-06-13 11:40                                   ` ZhouPeng
2012-06-14 13:51                                     ` Fabio Fantoni
2012-06-15  7:36                                       ` ZhouPeng

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=4FD5DCF7.2070103@tiscali.it \
    --to=fantonifabio@tiscali.it \
    --cc=Ian.Campbell@citrix.com \
    --cc=keir@xen.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=zpengxen@gmail.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).