Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Xen: Devel

Unable to get QXL vga working

 

 

First page Previous page 1 2 Next page Last page  View All Xen devel RSS feed   Index | Next | Previous | View Threaded


fantonifabio at tiscali

May 7, 2012, 8:01 AM

Post #26 of 41 (511 views)
Permalink
Re: Unable to get QXL vga working / videomem over 4MB issue [In reply to]

Fantu wrote
>
>
> Anthony PERARD-2 wrote
>>
>> On Fri, May 4, 2012 at 9:28 AM, Ian Campbell <Ian.Campbell@> wrote:
>>> Anthony -- any idea why the videoram setting doesn't work with upstream
>>> qemu?
>>
>> Well, the parameter could be pass to qemu qxl, but it's not yet. But
>> then, it seams you have to have this value of at least 32MB, otherwise
>> the value is increase in qemu.
>>
>> For cirrus/stdvga, there is no way to pass the parameter to qemu, the
>> size in qemu is fixed to 8MB.
>>
>> --
>> Anthony PERARD
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@.xen
>> http://lists.xen.org/xen-devel
>>
> I have already tried -global qxl-vga.vram_size for setting more videoram
> on qxl but not work,have always 4 mb, also with qemu-upstream unstable,
> the default code in qemu should have 64 mb and minimum 16 mb, why and
> where it sets 4 mb?
> Now I will try also with 1.1-rc0 and seabios 1.7.0.
>
I did other tests with new build (see
http://xen.1045712.n5.nabble.com/Test-result-of-xen-unstable-changeset-25259-td5691153.html
here for detail)

Precise domU start but X crash, same error also with Wheezy with more update
package include qxl driver
Here some details:
-------------------------------
PRECISEHVM.cfg
--------
name='PRECISEHVM'
builder="hvm"
memory=1024
#maxmem=1536
vcpus=2
hap=1
pae=1
acpi=1
apic=1
nx=1
vif=['bridge=xenbr0']
#vfb=['vnc=1,vncunused=1,vnclisten="0.0.0.0",keymap="it"']
#disk=['/mnt/vm/disks/PRECISEHVM.disk1.xm,raw,hda,rw',
'/dev/sr0,raw,hdb,ro,cdrom']
disk=['/mnt/vm/disks/PRECISEHVM.disk1.xm,raw,hda,rw']
boot='c'
xen_platform_pci=1
device_model_version='qemu-xen'
#vnc=1
#vncunused=1
#vnclisten="0.0.0.0"
#keymap="it"
stdvga=0
spice=1
spicehost='0.0.0.0'
spiceport=6000
spicedisable_ticketing=1
#device_model_args=["-device","qxl-vga","-global","qxl-vga.vram_size=33554432"]
device_model_args=["-vga","qxl"]
videoram=128
-------------------------------
Full X log: http://xen.1045712.n5.nabble.com/file/n5691285/Xorg.0.log
Xorg.0.log

I also tried to remove videoram parameter but not start
-------------------------------
xl create /etc/xen/PRECISEHVM.cfg
Parsing config file /etc/xen/PRECISEHVM.cfg
xc: info: VIRTUAL MEMORY ARRANGEMENT:
Loader: 0000000000100000->000000000019dc88
TOTAL: 0000000000000000->000000003f800000
ENTRY ADDRESS: 0000000000100000
xc: info: PHYSICAL MEMORY ALLOCATION:
4KB PAGES: 0x0000000000000200
2MB PAGES: 0x00000000000001fb
1GB PAGES: 0x0000000000000000
libxl: error: libxl_qmp.c:687:libxl__qmp_initialize: Connection error:
Connection refused
libxl: error: libxl_exec.c:200:libxl__wait_for_offspring: Device Model died
during startup
libxl: error: libxl_create.c:709:do_domain_create: device model did not
start: -1
-------------------------------
/var/log/xen/qemu-dm-PRECISEHVM.log
-------------------------
do_spice_init: starting 0.10.1
spice_server_add_interface: SPICE_INTERFACE_MIGRATION
spice_server_add_interface: SPICE_INTERFACE_KEYBOARD
spice_server_add_interface: SPICE_INTERFACE_MOUSE
qemu: hardware error: xen: failed to populate ram at 3f800000
CPU #0:
EAX=00000000 EBX=00000000 ECX=00000000 EDX=00000633
ESI=00000000 EDI=00000000 EBP=00000000 ESP=00000000
EIP=0000fff0 EFL=00000002 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0000 00000000 0000ffff 00009300
CS =f000 ffff0000 0000ffff 00009b00
SS =0000 00000000 0000ffff 00009300
DS =0000 00000000 0000ffff 00009300
FS =0000 00000000 0000ffff 00009300
GS =0000 00000000 0000ffff 00009300
LDT=0000 00000000 0000ffff 00008200
TR =0000 00000000 0000ffff 00008b00
GDT= 00000000 0000ffff
IDT= 00000000 0000ffff
CR0=60000010 CR2=00000000 CR3=00000000 CR4=00000000
DR0=00000000 DR1=00000000 DR2=00000000 DR3=00000000
DR6=ffff0ff0 DR7=00000400
EFER=0000000000000000
FCW=037f FSW=0000 [ST=0] FTW=00 MXCSR=00001f80
FPR0=0000000000000000 0000 FPR1=0000000000000000 0000
FPR2=0000000000000000 0000 FPR3=0000000000000000 0000
FPR4=0000000000000000 0000 FPR5=0000000000000000 0000
FPR6=0000000000000000 0000 FPR7=0000000000000000 0000
XMM00=00000000000000000000000000000000
XMM01=00000000000000000000000000000000
XMM02=00000000000000000000000000000000
XMM03=00000000000000000000000000000000
XMM04=00000000000000000000000000000000
XMM05=00000000000000000000000000000000
XMM06=00000000000000000000000000000000
XMM07=00000000000000000000000000000000
CPU #1:
EAX=00000000 EBX=00000000 ECX=00000000 EDX=00000633
ESI=00000000 EDI=00000000 EBP=00000000 ESP=00000000
EIP=0000fff0 EFL=00000002 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=1
ES =0000 00000000 0000ffff 00009300
CS =f000 ffff0000 0000ffff 00009b00
SS =0000 00000000 0000ffff 00009300
DS =0000 00000000 0000ffff 00009300
FS =0000 00000000 0000ffff 00009300
GS =0000 00000000 0000ffff 00009300
LDT=0000 00000000 0000ffff 00008200
TR =0000 00000000 0000ffff 00008b00
GDT= 00000000 0000ffff
IDT= 00000000 0000ffff
CR0=60000010 CR2=00000000 CR3=00000000 CR4=00000000
DR0=00000000 DR1=00000000 DR2=00000000 DR3=00000000
DR6=ffff0ff0 DR7=00000400
EFER=0000000000000000
FCW=037f FSW=0000 [ST=0] FTW=00 MXCSR=00001f80
FPR0=0000000000000000 0000 FPR1=0000000000000000 0000
FPR2=0000000000000000 0000 FPR3=0000000000000000 0000
FPR4=0000000000000000 0000 FPR5=0000000000000000 0000
FPR6=0000000000000000 0000 FPR7=0000000000000000 0000
XMM00=00000000000000000000000000000000
XMM01=00000000000000000000000000000000
XMM02=00000000000000000000000000000000
XMM03=00000000000000000000000000000000
XMM04=00000000000000000000000000000000
XMM05=00000000000000000000000000000000
XMM06=00000000000000000000000000000000
XMM07=00000000000000000000000000000000
-------------------------------

videoram seems reserve the ram and from X log QXL videoram seems to be at
correct size but probably qemu can't use it.

--
View this message in context: http://xen.1045712.n5.nabble.com/Unable-to-get-QXL-vga-working-tp5667919p5691285.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

_______________________________________________
Xen-devel mailing list
Xen-devel [at] lists
http://lists.xen.org/xen-devel


pasik at iki

May 8, 2012, 9:24 AM

Post #27 of 41 (494 views)
Permalink
Re: Unable to get QXL vga working / videomem over 4MB issue [In reply to]

On Fri, May 04, 2012 at 12:32:19PM +0100, Ian Campbell wrote:
> On Fri, 2012-05-04 at 12:21 +0100, Anthony PERARD wrote:
> > On Fri, May 4, 2012 at 9:28 AM, Ian Campbell <Ian.Campbell [at] citrix> wrote:
> > > Anthony -- any idea why the videoram setting doesn't work with upstream
> > > qemu?
> >
> > Well, the parameter could be pass to qemu qxl, but it's not yet. But
> > then, it seams you have to have this value of at least 32MB, otherwise
> > the value is increase in qemu.
> >
> > For cirrus/stdvga, there is no way to pass the parameter to qemu, the
> > size in qemu is fixed to 8MB.
>
> OK, so this is simply a feature which upstream qemu doesn't have. That's
> fine.
>

Is this something that should be forward-ported from qemu-xen-traditional
to upstream qemu ?

> I guess xl.cfg(5) needs updating to make it clear that this option only
> applies to qemu-xen-traditional.
>
> The docs also currently say that for stdvga the default is 8MB and for
> not stdvga (by which I guess it means Cirrus) the default if 4MB. So I
> guess even this is inaccurate for qemu-xen-upstream?
>
> Can someone send a patch please?
>

For the documentation patch maybe add this to the 4.2 status todo list
as a reminder :)

-- Pasi


_______________________________________________
Xen-devel mailing list
Xen-devel [at] lists
http://lists.xen.org/xen-devel


Ian.Campbell at citrix

May 8, 2012, 12:15 PM

Post #28 of 41 (497 views)
Permalink
Re: Unable to get QXL vga working / videomem over 4MB issue [In reply to]

On Tue, 2012-05-08 at 17:24 +0100, Pasi Kšrkkšinen wrote:
> On Fri, May 04, 2012 at 12:32:19PM +0100, Ian Campbell wrote:
> > On Fri, 2012-05-04 at 12:21 +0100, Anthony PERARD wrote:
> > > On Fri, May 4, 2012 at 9:28 AM, Ian Campbell <Ian.Campbell [at] citrix> wrote:
> > > > Anthony -- any idea why the videoram setting doesn't work with upstream
> > > > qemu?
> > >
> > > Well, the parameter could be pass to qemu qxl, but it's not yet. But
> > > then, it seams you have to have this value of at least 32MB, otherwise
> > > the value is increase in qemu.
> > >
> > > For cirrus/stdvga, there is no way to pass the parameter to qemu, the
> > > size in qemu is fixed to 8MB.
> >
> > OK, so this is simply a feature which upstream qemu doesn't have. That's
> > fine.
> >
>
> Is this something that should be forward-ported from qemu-xen-traditional
> to upstream qemu ?

If there are reasons why this should be configurable, then I guess so.
Are you going to look into that?

This doesn't seem like 4.2 material to me though.

> > I guess xl.cfg(5) needs updating to make it clear that this option only
> > applies to qemu-xen-traditional.
> >
> > The docs also currently say that for stdvga the default is 8MB and for
> > not stdvga (by which I guess it means Cirrus) the default if 4MB. So I
> > guess even this is inaccurate for qemu-xen-upstream?
> >
> > Can someone send a patch please?
> >
>
> For the documentation patch maybe add this to the 4.2 status todo list
> as a reminder :)

Please make requests for additions to the TODO list in the most recent
TODO list thread, with a link to the relevant thread. Otherwise the
chances are I won't remember when I update the list, since I only look
at replies in the TODO threads.

Ian.


_______________________________________________
Xen-devel mailing list
Xen-devel [at] lists
http://lists.xen.org/xen-devel


fantonifabio at tiscali

May 9, 2012, 7:07 AM

Post #29 of 41 (502 views)
Permalink
Re: Unable to get QXL vga working / videomem over 4MB issue [In reply to]

Ian Campbell-10 wrote
>
> On Tue, 2012-05-08 at 17:24 +0100, Pasi Kärkkäinen wrote:
>> On Fri, May 04, 2012 at 12:32:19PM +0100, Ian Campbell wrote:
>> > On Fri, 2012-05-04 at 12:21 +0100, Anthony PERARD wrote:
>> > > On Fri, May 4, 2012 at 9:28 AM, Ian Campbell &lt;Ian.Campbell@&gt;
>> wrote:
>> > > > Anthony -- any idea why the videoram setting doesn't work with
>> upstream
>> > > > qemu?
>> > >
>> > > Well, the parameter could be pass to qemu qxl, but it's not yet. But
>> > > then, it seams you have to have this value of at least 32MB,
>> otherwise
>> > > the value is increase in qemu.
>> > >
>> > > For cirrus/stdvga, there is no way to pass the parameter to qemu, the
>> > > size in qemu is fixed to 8MB.
>> >
>> > OK, so this is simply a feature which upstream qemu doesn't have.
>> That's
>> > fine.
>> >
>>
>> Is this something that should be forward-ported from qemu-xen-traditional
>> to upstream qemu ?
>
> If there are reasons why this should be configurable, then I guess so.
> Are you going to look into that?
>
> This doesn't seem like 4.2 material to me though.
>
>> > I guess xl.cfg(5) needs updating to make it clear that this option only
>> > applies to qemu-xen-traditional.
>> >
>> > The docs also currently say that for stdvga the default is 8MB and for
>> > not stdvga (by which I guess it means Cirrus) the default if 4MB. So I
>> > guess even this is inaccurate for qemu-xen-upstream?
>> >
>> > Can someone send a patch please?
>> >
>>
>> For the documentation patch maybe add this to the 4.2 status todo list
>> as a reminder :)
>
> Please make requests for additions to the TODO list in the most recent
> TODO list thread, with a link to the relevant thread. Otherwise the
> chances are I won't remember when I update the list, since I only look
> at replies in the TODO threads.
>
> Ian.
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@.xen
> http://lists.xen.org/xen-devel
>
I may have found something that makes the problem clearer.
With Precise hvm domU with spice and cirrus (default vga) on qemu-xen lspci
show 32 mb but Xorg only sees 4 mb.

----------------------------------------------------
lspci -vvv
...
00:02.0 VGA compatible controller: Cirrus Logic GD 5446 (prog-if 00 [VGA
controller])
Subsystem: Red Hat, Inc Device 1100
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 0
Region 0: Memory at f0000000 (32-bit, prefetchable) [size=&lt;b>32M*]
Region 1: Memory at f3020000 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at f3000000 [disabled] [size=64K]
Kernel modules: cirrusfb
...
-----------------
Xorg.0.log
---------------
...
[ 6.443] (--) CIRRUS(0): VideoRAM: 4096 kByte
...
----------------------------------------------------

If you need more information I'll post it.

--
View this message in context: http://xen.1045712.n5.nabble.com/Unable-to-get-QXL-vga-working-tp5667919p5697470.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

_______________________________________________
Xen-devel mailing list
Xen-devel [at] lists
http://lists.xen.org/xen-devel


anthony.perard at gmail

May 9, 2012, 9:01 AM

Post #30 of 41 (509 views)
Permalink
Re: Unable to get QXL vga working / videomem over 4MB issue [In reply to]

> I may have found something that makes the problem clearer.
> With Precise hvm domU with spice and cirrus (default vga) on qemu-xen lspci
> show 32 mb but Xorg only sees 4 mb.
>
> ----------------------------------------------------
> lspci -vvv
> ...
> 00:02.0 VGA compatible controller: Cirrus Logic GD 5446 (prog-if 00 [VGA
> controller])
>        Subsystem: Red Hat, Inc Device 1100
>        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B- DisINTx-
>        Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
> <MAbort- >SERR- <PERR- INTx-
>        Latency: 0
>        Region 0: Memory at f0000000 (32-bit, prefetchable) [size=&lt;b>32M*]
>        Region 1: Memory at f3020000 (32-bit, non-prefetchable) [size=4K]
>        Expansion ROM at f3000000 [disabled] [size=64K]
>        Kernel modules: cirrusfb
> ...
> -----------------
> Xorg.0.log
> ---------------
> ...
> [     6.443] (--) CIRRUS(0): VideoRAM: 4096 kByte
> ...
> ----------------------------------------------------
>
> If you need more information I'll post it.

This is probably not related.

I try to run qxl, and found the same issue as you, Xorg-server
segfault. But I see that Xen give an error message:
(XEN) emulate.c:97:d24 bad mmio size 16
(XEN) io.c:199:d24 MMIO emulation failed @ 0033:7ff5dd8d7938: f3 0f 6f
19 f3 0f 6f 51 10 f3

That probably why qxl does not work with Xen.

--
Anthony PERARD

_______________________________________________
Xen-devel mailing list
Xen-devel [at] lists
http://lists.xen.org/xen-devel


heliman at katamail

May 11, 2012, 5:19 AM

Post #31 of 41 (489 views)
Permalink
Re: Unable to get QXL vga working / videomem over 4MB issue [In reply to]

Anthony PERARD-2 wrote
>
> For cirrus/stdvga, there is no way to pass the parameter to qemu, the
> size in qemu is fixed to 8MB.
>

How can you see these 8MB ?
In my tests with cirrus/stdvga, in a Linux guest lspci always report 32M and
Xorg.0.log report "VideoRAM: 4096 kByte". In a Windows XP/7 guest the Device
Manager show 32M as well. This is confusing.
Is there a better way to check videoram and videoram usage in a Linux or
Windows guest?


--
View this message in context: http://xen.1045712.n5.nabble.com/Unable-to-get-QXL-vga-working-tp5667919p5702906.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

_______________________________________________
Xen-devel mailing list
Xen-devel [at] lists
http://lists.xen.org/xen-devel


anthony.perard at citrix

May 11, 2012, 6:00 AM

Post #32 of 41 (488 views)
Permalink
Re: Unable to get QXL vga working / videomem over 4MB issue [In reply to]

On Fri, May 11, 2012 at 1:19 PM, Geraldes <heliman [at] katamail> wrote:
>
> Anthony PERARD-2 wrote
>>
>> For cirrus/stdvga, there is no way to pass the parameter to qemu, the
>> size in qemu is fixed to 8MB.
>>
>
> How can you see these 8MB ?

This is just the size of the vram allocated by qemu, I saw this in the code.

> In my tests with cirrus/stdvga, in a Linux guest lspci always report 32M and
> Xorg.0.log report "VideoRAM: 4096 kByte". In a Windows XP/7 guest the Device
> Manager show 32M as well. This is confusing.

It seams that part of the 32MB are used to do other kind of operation
that just accessing to the vram. For the 4MB instead of 8 reported by
Xorg, I don't know. There is probably a reason why Cirrus will report
4 instead of 8.

> Is there a better way to check videoram and videoram usage in a Linux or
> Windows guest?

I don't think so.

--
Anthony PERARD

_______________________________________________
Xen-devel mailing list
Xen-devel [at] lists
http://lists.xen.org/xen-devel


zpengxen at gmail

May 23, 2012, 8:13 PM

Post #33 of 41 (481 views)
Permalink
Re: Unable to get QXL vga working [In reply to]

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 dmesg:

(XEN) page_alloc.c:1284:d0 Over-allocation for domain 22: 98561 > 98560
(XEN) memory.c:131:d0 Could not allocate order=0 extent: id=22
memflags=0 (2328 of 16384)
(XEN) HVM22: HVM Loader
(XEN) HVM22: Detected Xen v4.2-unstable
(XEN) HVM22: Xenbus rings @0xfeffc000, event channel 3
(XEN) HVM22: System requested SeaBIOS
(XEN) HVM22: CPU speed is 2660 MHz


Qemu log appended:

char device redirected to /dev/pts/9
do_spice_init: starting 0.7.1
spice_server_add_interface: SPICE_INTERFACE_KEYBOARD
spice_server_add_interface: SPICE_INTERFACE_MOUSE
ram_size: 67108864 // 64M for qxl
qemu: hardware error: xen: failed to populate ram at 17800000 // by
xen_ram_alloc
CPU #0:
EAX=00000000 EBX=00000000 ECX=00000000 EDX=00000633
ESI=00000000 EDI=00000000 EBP=00000000 ESP=00000000
EIP=0000fff0 EFL=00000002 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0000 00000000 0000ffff 00009300
CS =f000 ffff0000 0000ffff 00009b00
SS =0000 00000000 0000ffff 00009300
DS =0000 00000000 0000ffff 00009300
FS =0000 00000000 0000ffff 00009300
GS =0000 00000000 0000ffff 00009300
LDT=0000 00000000 0000ffff 00008200
TR =0000 00000000 0000ffff 00008b00
GDT= 00000000 0000ffff
IDT= 00000000 0000ffff
CR0=60000010 CR2=00000000 CR3=00000000 CR4=00000000
DR0=00000000 DR1=00000000 DR2=00000000 DR3=00000000
DR6=ffff0ff0 DR7=00000400
EFER=0000000000000000
FCW=037f FSW=0000 [ST=0] FTW=00 MXCSR=00001f80
FPR0=0000000000000000 0000 FPR1=0000000000000000 0000
FPR2=0000000000000000 0000 FPR3=0000000000000000 0000
FPR4=0000000000000000 0000 FPR5=0000000000000000 0000
FPR6=0000000000000000 0000 FPR7=0000000000000000 0000
XMM00=00000000000000000000000000000000 XMM01=00000000000000000000000000000000
XMM02=00000000000000000000000000000000 XMM03=00000000000000000000000000000000
XMM04=00000000000000000000000000000000 XMM05=00000000000000000000000000000000
XMM06=00000000000000000000000000000000 XMM07=00000000000000000000000000000000

On Fri, May 4, 2012 at 4:30 PM, Ian Campbell <Ian.Campbell [at] citrix> wrote:
> On Fri, 2012-05-04 at 02:15 +0100, ZhouPeng wrote:
>> On Thu, May 3, 2012 at 9:56 PM, Stefano Stabellini
>> <stefano.stabellini [at] eu> wrote:
>> > On Thu, 3 May 2012, ZhouPeng wrote:
>> >> >> > What do you mean by "disabling graphic"? Do you mean disabling the vga
>> >> >> > card?
>> >> >> No, not disable the vga card.
>> >> >> But booting in Text mode.
>> >> >
>> >> > Then you are manually starting X11 with the spice driver?
>> >> Always in text mode.
>> >> Never start X11.
>> >> Using stdard vga but not qxl-vga.
>> >
>> > so you didn't actually test qxl at all, did you?
>> Didn't test qxl but only spice.
>
> So to return to my question at the start of this thread -- is qxl
> something you would be interested in supporting? (I think you said yes,
> but we've been somewhat sidetracked on the distinction between SPICE
> support and QXL support).
>
> In any case this is definitely 4.3 material IMHO since we are now
> feature frozen for 4.2.
>
> Ian.
>



--
Zhou Peng

_______________________________________________
Xen-devel mailing list
Xen-devel [at] lists
http://lists.xen.org/xen-devel


stefano.stabellini at eu

May 24, 2012, 3:13 AM

Post #34 of 41 (481 views)
Permalink
Re: Unable to get QXL vga working [In reply to]

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.

_______________________________________________
Xen-devel mailing list
Xen-devel [at] lists
http://lists.xen.org/xen-devel


zpengxen at gmail

May 24, 2012, 4:28 AM

Post #35 of 41 (480 views)
Permalink
Re: Unable to get QXL vga working [In reply to]

On Thu, May 24, 2012 at 6:13 PM, Stefano Stabellini
<stefano.stabellini [at] eu> 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.
--
Zhou Peng

_______________________________________________
Xen-devel mailing list
Xen-devel [at] lists
http://lists.xen.org/xen-devel


fantonifabio at tiscali

Jun 11, 2012, 4:56 AM

Post #36 of 41 (471 views)
Permalink
Re: Unable to get QXL vga working [In reply to]

Il 24/05/2012 13:28, ZhouPeng ha scritto:
> On Thu, May 24, 2012 at 6:13 PM, Stefano Stabellini
> <stefano.stabellini [at] eu> 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?
Attachments: smime.p7s (4.39 KB)


zpengxen at gmail

Jun 13, 2012, 2:02 AM

Post #37 of 41 (469 views)
Permalink
Re: Unable to get QXL vga working [In reply to]

On Mon, Jun 11, 2012 at 7:56 PM, Fabio Fantoni <fantonifabio [at] tiscali> wrote:
> Il 24/05/2012 13:28, ZhouPeng ha scritto:
>
>> On Thu, May 24, 2012 at 6:13 PM, Stefano Stabellini
>> <stefano.stabellini [at] eu> †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).

Could you find qxl vga card (named "Red Hat QXL GPU") in your
windows hvm's device manager to make sure your qxl is working?

My testing hvm-guest is Win XP.

I played "Harry Potter" in my LAN smoothly, qxl gives
great enhancement .

Although I don't test win7 and linux, I think it should work for them.
> I tried also with qemu 1.1.0 but nothing change.

I am not sure qemu 1.1.0 accept all the patches for xen.

Could you have a try of git://xenbits.xen.org/qemu-upstream-unstable.git

It is build and installed by default, you should enable spice support.
spice can be enabled like below:

+++ b/tools/Makefile Sat May 26 12:31:01 2012 +0800
@@ -157,6 +157,7 @@ subdir-all-qemu-xen-dir subdir-install-q
--bindir=$(LIBEXEC) \
--datadir=$(SHAREDIR)/qemu-xen \
--disable-kvm \
+ --enable-spice \

> Does it work correctly for you? If so can I have some detail of your
> configurations please?

My vm.cfg:

name = 'xpPro_spice'
firmware_override = '/usr/lib/xen/boot/hvmloader'
builder = 'hvm'
memory = '1024'
device_model_version = 'qemu-xen'
device_model_override = '/usr/lib/xen/bin/qemu-system-i386'
disk = [ 'file:/path-to-img/xpPro.img,ioemu:hda,w' ]
vif = ['ip=192.168.1.112, type=ioemu, bridge=eth0, mac=00:21:97:CB:0E:7D']
sdl=0
vnc=0
vncviewer=0
serial = 'pty'
vcpus=1
usbdevice='tablet'
#spice
spice=1
qxl=1
#qxlram=64
#qxlvram=64
spiceport=6000
spicehost='192.168.1.187'
spicedisable_ticketing = 1
spiceagent_mouse = 0 # (1|0)

> 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?

I think audio support can be considered after qxl accpted.
>
>


--
Zhou Peng

_______________________________________________
Xen-devel mailing list
Xen-devel [at] lists
http://lists.xen.org/xen-devel


fantonifabio at tiscali

Jun 13, 2012, 2:38 AM

Post #38 of 41 (467 views)
Permalink
Re: Unable to get QXL vga working [In reply to]

Il 13/06/2012 11:02, ZhouPeng ha scritto:
> On Mon, Jun 11, 2012 at 7:56 PM, Fabio Fantoni<fantonifabio [at] tiscali> wrote:
>> Il 24/05/2012 13:28, ZhouPeng ha scritto:
>>
>>> On Thu, May 24, 2012 at 6:13 PM, Stefano Stabellini
>>> <stefano.stabellini [at] eu> 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).
> Could you find qxl vga card (named "Red Hat QXL GPU") in your
> windows hvm's device manager to make sure your qxl is working?
>
> My testing hvm-guest is Win XP.
>
> I played "Harry Potter" in my LAN smoothly, qxl gives
> great enhancement .
>
> Although I don't test win7 and linux, I think it should work for them.
>> I tried also with qemu 1.1.0 but nothing change.
> I am not sure qemu 1.1.0 accept all the patches for xen.
>
> Could you have a try of git://xenbits.xen.org/qemu-upstream-unstable.git
>
> It is build and installed by default, you should enable spice support.
> spice can be enabled like below:
>
> +++ b/tools/Makefile Sat May 26 12:31:01 2012 +0800
> @@ -157,6 +157,7 @@ subdir-all-qemu-xen-dir subdir-install-q
> --bindir=$(LIBEXEC) \
> --datadir=$(SHAREDIR)/qemu-xen \
> --disable-kvm \
> + --enable-spice \
>
>> Does it work correctly for you? If so can I have some detail of your
>> configurations please?
> My vm.cfg:
>
> name = 'xpPro_spice'
> firmware_override = '/usr/lib/xen/boot/hvmloader'
> builder = 'hvm'
> memory = '1024'
> device_model_version = 'qemu-xen'
> device_model_override = '/usr/lib/xen/bin/qemu-system-i386'
> disk = [ 'file:/path-to-img/xpPro.img,ioemu:hda,w' ]
> vif = ['ip=192.168.1.112, type=ioemu, bridge=eth0, mac=00:21:97:CB:0E:7D']
> sdl=0
> vnc=0
> vncviewer=0
> serial = 'pty'
> vcpus=1
> usbdevice='tablet'
> #spice
> spice=1
> qxl=1
> #qxlram=64
> #qxlvram=64
> spiceport=6000
> spicehost='192.168.1.187'
> spicedisable_ticketing = 1
> spiceagent_mouse = 0 # (1|0)
>
>> 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?
> I think audio support can be considered after qxl accpted.
>>
>
Thanks for reply, qxl driver is installed, windows see qxl video card,
already compiled qemu with spice with patch I send months ago, already
tried git://xenbits.xen.org/qemu-upstream-unstable.git before 1.1.
Unfortunately the results are always the same.
Here a quick recording:
Windows 7 test: http://fantu.it/vari/spiceqxldebug1.mkv
Debian wheezy test: http://fantu.it/vari/spiceqxldebug2.mkv
Are not new but the result of the last test is the same.
I hope I can help you understand the problem.
If you need more information ask.
Attachments: smime.p7s (4.39 KB)


zpengxen at gmail

Jun 13, 2012, 4:40 AM

Post #39 of 41 (481 views)
Permalink
Re: Unable to get QXL vga working [In reply to]

On Wed, Jun 13, 2012 at 5:38 PM, Fabio Fantoni <fantonifabio [at] tiscali> wrote:
> Il 13/06/2012 11:02, ZhouPeng ha scritto:
>
>> On Mon, Jun 11, 2012 at 7:56 PM, Fabio Fantoni<fantonifabio [at] tiscali>
>> †wrote:
>>>
>>> Il 24/05/2012 13:28, ZhouPeng ha scritto:
>>>
>>>> On Thu, May 24, 2012 at 6:13 PM, Stefano Stabellini
>>>> <stefano.stabellini [at] eu> † †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).
>>
>> Could you find qxl vga card †(named "Red Hat QXL GPU") in your
>> windows hvm's device manager to make sure your qxl is working?
>>
>> My testing hvm-guest is Win XP.
>>
>> I played "Harry Potter" in my LAN smoothly, qxl gives
>> great enhancement .
>>
>> Although I don't test win7 and linux, I think it should work for them.
>>>
>>> I tried also with qemu 1.1.0 but nothing change.
>>
>> I am not sure qemu 1.1.0 accept all the patches for xen.
>>
>> Could you have a try of git://xenbits.xen.org/qemu-upstream-unstable.git
>>
>> It is build and installed by default, you should enable spice support.
>> spice can be enabled like below:
>>
>> +++ b/tools/Makefile † †Sat May 26 12:31:01 2012 +0800
>> @@ -157,6 +157,7 @@ subdir-all-qemu-xen-dir subdir-install-q
>> † † † † --bindir=$(LIBEXEC) \
>> † † † † --datadir=$(SHAREDIR)/qemu-xen \
>> † † † † --disable-kvm \
>> + † † † --enable-spice \
>>
>>> Does it work correctly for you? If so can I have some detail of your
>>> configurations please?
>>
>> My vm.cfg:
>>
>> name = 'xpPro_spice'
>> firmware_override = '/usr/lib/xen/boot/hvmloader'
>> builder = 'hvm'
>> memory = '1024'
>> device_model_version = 'qemu-xen'
>> device_model_override = '/usr/lib/xen/bin/qemu-system-i386'
>> disk = [ 'file:/path-to-img/xpPro.img,ioemu:hda,w' ]
>> vif = ['ip=192.168.1.112, type=ioemu, bridge=eth0, mac=00:21:97:CB:0E:7D']
>> sdl=0
>> vnc=0
>> vncviewer=0
>> serial = 'pty'
>> vcpus=1
>> usbdevice='tablet'
>> #spice
>> spice=1
>> qxl=1
>> #qxlram=64
>> #qxlvram=64
>> spiceport=6000
>> spicehost='192.168.1.187'
>> spicedisable_ticketing = 1
>> spiceagent_mouse = 0 # (1|0)
>>
>>> 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?
>>
>> I think audio support can be considered after qxl accpted.
>>>
>>>
>>
> Thanks for reply, qxl driver is installed, windows see qxl video card,
> already compiled qemu with spice with patch I send months ago, already tried
> git://xenbits.xen.org/qemu-upstream-unstable.git before 1.1.
> Unfortunately the results are always the same.
> Here a quick recording:
> Windows 7 test: http://fantu.it/vari/spiceqxldebug1.mkv

oh... it shows spice+qxl running on Xen get
significant performance reduction compared with KVM ...

> Debian wheezy test: http://fantu.it/vari/spiceqxldebug2.mkv
> Are not new but the result of the last test is the same.
> I hope I can help you understand the problem.
> If you need more information ask.

--
Zhou Peng

_______________________________________________
Xen-devel mailing list
Xen-devel [at] lists
http://lists.xen.org/xen-devel


fantonifabio at tiscali

Jun 14, 2012, 6:51 AM

Post #40 of 41 (472 views)
Permalink
Re: Unable to get QXL vga working [In reply to]

Il 13/06/2012 13:40, ZhouPeng ha scritto:
> On Wed, Jun 13, 2012 at 5:38 PM, Fabio Fantoni<fantonifabio [at] tiscali> wrote:
>> Il 13/06/2012 11:02, ZhouPeng ha scritto:
>>
>>> On Mon, Jun 11, 2012 at 7:56 PM, Fabio Fantoni<fantonifabio [at] tiscali>
>>> wrote:
>>>> Il 24/05/2012 13:28, ZhouPeng ha scritto:
>>>>
>>>>> On Thu, May 24, 2012 at 6:13 PM, Stefano Stabellini
>>>>> <stefano.stabellini [at] eu> 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).
>>> Could you find qxl vga card (named "Red Hat QXL GPU") in your
>>> windows hvm's device manager to make sure your qxl is working?
>>>
>>> My testing hvm-guest is Win XP.
>>>
>>> I played "Harry Potter" in my LAN smoothly, qxl gives
>>> great enhancement .
>>>
>>> Although I don't test win7 and linux, I think it should work for them.
>>>> I tried also with qemu 1.1.0 but nothing change.
>>> I am not sure qemu 1.1.0 accept all the patches for xen.
>>>
>>> Could you have a try of git://xenbits.xen.org/qemu-upstream-unstable.git
>>>
>>> It is build and installed by default, you should enable spice support.
>>> spice can be enabled like below:
>>>
>>> +++ b/tools/Makefile Sat May 26 12:31:01 2012 +0800
>>> @@ -157,6 +157,7 @@ subdir-all-qemu-xen-dir subdir-install-q
>>> --bindir=$(LIBEXEC) \
>>> --datadir=$(SHAREDIR)/qemu-xen \
>>> --disable-kvm \
>>> + --enable-spice \
>>>
>>>> Does it work correctly for you? If so can I have some detail of your
>>>> configurations please?
>>> My vm.cfg:
>>>
>>> name = 'xpPro_spice'
>>> firmware_override = '/usr/lib/xen/boot/hvmloader'
>>> builder = 'hvm'
>>> memory = '1024'
>>> device_model_version = 'qemu-xen'
>>> device_model_override = '/usr/lib/xen/bin/qemu-system-i386'
>>> disk = [ 'file:/path-to-img/xpPro.img,ioemu:hda,w' ]
>>> vif = ['ip=192.168.1.112, type=ioemu, bridge=eth0, mac=00:21:97:CB:0E:7D']
>>> sdl=0
>>> vnc=0
>>> vncviewer=0
>>> serial = 'pty'
>>> vcpus=1
>>> usbdevice='tablet'
>>> #spice
>>> spice=1
>>> qxl=1
>>> #qxlram=64
>>> #qxlvram=64
>>> spiceport=6000
>>> spicehost='192.168.1.187'
>>> spicedisable_ticketing = 1
>>> spiceagent_mouse = 0 # (1|0)
>>>
>>>> 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?
>>> I think audio support can be considered after qxl accpted.
>>>>
>> Thanks for reply, qxl driver is installed, windows see qxl video card,
>> already compiled qemu with spice with patch I send months ago, already tried
>> git://xenbits.xen.org/qemu-upstream-unstable.git before 1.1.
>> Unfortunately the results are always the same.
>> Here a quick recording:
>> Windows 7 test: http://fantu.it/vari/spiceqxldebug1.mkv
> oh... it shows spice+qxl running on Xen get
> significant performance reduction compared with KVM ...
>
>> Debian wheezy test: http://fantu.it/vari/spiceqxldebug2.mkv
>> Are not new but the result of the last test is the same.
>> I hope I can help you understand the problem.
>> If you need more information ask.
We are trying to reproduce your results but failed so far.
Can you give me details about the dom0 used for your tests please?
For example here are details about my testing dom0:
Wheezy 64 bit with kernel from package linux-image-3.2.0-2-amd64 version
3.2.18-1, package blktap-dkms and all dependency packages for xen 4.2,
spice and usb redirection.
-------------------------
/etc/modules
------------
loop max_loop=64
xenfs
xen-evtchn
blktap
-------------------------
hg clone http://xenbits.xen.org/xen-unstable.hg
vi config/StdGNU.mk # Workaround for Wheezy with multiarch support,
there are parts that use LIBDIR set here instead of the one in configure
(libdir)
LIBLEAFDIR_x86_64 ?= lib
vi Config.mk
PYTHON_PREFIX_ARG =
-------------------------
Added some patches:
- autoconf: add variable for pass arbitrary options to qemu upstream v3
- tools: Improve make deb
- libxc: do not "panic" if a kernel is not a bzImage.
- tools/hotplug/Linux/init.d/: added other xen kernel modules on
xencommons start
- 3 patches for add qxl support
-------------------------
./configure --enable-qemuu-spice --enable-qemuu-usbredir
--enable-qemuu-debug
-------------------------
make deb

Is qxl someway affected by physical video card of dom0?
Have you installed spice-guest-tools-0.1.exe
<http://spice-space.org/download/binaries/spice-guest-tools-0.1.exe>
from spice site, if no what do you use for qxl driver?
Have you also installed gplpv driver or not?
Thanks for any reply.
Attachments: smime.p7s (4.39 KB)


zpengxen at gmail

Jun 15, 2012, 12:36 AM

Post #41 of 41 (477 views)
Permalink
Re: Unable to get QXL vga working [In reply to]

On Thu, Jun 14, 2012 at 9:51 PM, Fabio Fantoni <fantonifabio [at] tiscali> wrote:
> Il 13/06/2012 13:40, ZhouPeng ha scritto:
>
> On Wed, Jun 13, 2012 at 5:38 PM, Fabio Fantoni <fantonifabio [at] tiscali>
> wrote:
>
> Il 13/06/2012 11:02, ZhouPeng ha scritto:
>
> On Mon, Jun 11, 2012 at 7:56 PM, Fabio Fantoni<fantonifabio [at] tiscali>
>
> †wrote:
>
> Il 24/05/2012 13:28, ZhouPeng ha scritto:
>
> On Thu, May 24, 2012 at 6:13 PM, Stefano Stabellini
> <stefano.stabellini [at] eu> † †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).
>
> Could you find qxl vga card †(named "Red Hat QXL GPU") in your
> windows hvm's device manager to make sure your qxl is working?
>
> My testing hvm-guest is Win XP.
>
> I played "Harry Potter" in my LAN smoothly, qxl gives
> great enhancement .
>
> Although I don't test win7 and linux, I think it should work for them.
>
> I tried also with qemu 1.1.0 but nothing change.
>
> I am not sure qemu 1.1.0 accept all the patches for xen.
>
> Could you have a try of git://xenbits.xen.org/qemu-upstream-unstable.git
>
> It is build and installed by default, you should enable spice support.
> spice can be enabled like below:
>
> +++ b/tools/Makefile † †Sat May 26 12:31:01 2012 +0800
> @@ -157,6 +157,7 @@ subdir-all-qemu-xen-dir subdir-install-q
> † † † † --bindir=$(LIBEXEC) \
> † † † † --datadir=$(SHAREDIR)/qemu-xen \
> † † † † --disable-kvm \
> + † † † --enable-spice \
>
> Does it work correctly for you? If so can I have some detail of your
> configurations please?
>
> My vm.cfg:
>
> name = 'xpPro_spice'
> firmware_override = '/usr/lib/xen/boot/hvmloader'
> builder = 'hvm'
> memory = '1024'
> device_model_version = 'qemu-xen'
> device_model_override = '/usr/lib/xen/bin/qemu-system-i386'
> disk = [ 'file:/path-to-img/xpPro.img,ioemu:hda,w' ]
> vif = ['ip=192.168.1.112, type=ioemu, bridge=eth0, mac=00:21:97:CB:0E:7D']
> sdl=0
> vnc=0
> vncviewer=0
> serial = 'pty'
> vcpus=1
> usbdevice='tablet'
> #spice
> spice=1
> qxl=1
> #qxlram=64
> #qxlvram=64
> spiceport=6000
> spicehost='192.168.1.187'
> spicedisable_ticketing = 1
> spiceagent_mouse = 0 # (1|0)
>
> 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?
>
> I think audio support can be considered after qxl accpted.
>
> Thanks for reply, qxl driver is installed, windows see qxl video card,
> already compiled qemu with spice with patch I send months ago, already tried
> git://xenbits.xen.org/qemu-upstream-unstable.git before 1.1.
> Unfortunately the results are always the same.
> Here a quick recording:
> Windows 7 test: http://fantu.it/vari/spiceqxldebug1.mkv
>
> oh... it shows spice+qxl running on Xen get
> significant performance reduction compared with KVM ...
>
> Debian wheezy test: http://fantu.it/vari/spiceqxldebug2.mkv
> Are not new but the result of the last test is the same.
> I hope I can help you understand the problem.
> If you need more information ask.
>
> We are trying to reproduce your results but failed so far.

From your video spiceqxldebug1.mkv, I think you have reproduced it with win7?
And your mouse interaction in win7 shows performance is significantly
reduced compared
with qxl on kvm greatly. How about view a video from remote spice client?

On my WinXP testing, the mouse interaction is better than
your win7 test (but not as good as in kvm too), and I view a movie(Harry Potter)
from remote spice client (spice client on winxp), it's smooth.

Any way, qxl improve the performance, but it is not as good as running
on kvm from my
experence (no quantitative test). I don't know the reason yet. I just
guess it should
exist in qemu-xen or hypervisor.

I think you have reproduced.

My environment is simple, use the default.
---------------------
hg clone http://xenbits.xen.org/xen-unstable.hg

Dom0 kernel: (You can get it by KERNELS ?= linux-2.6-pvops in Linux.mk
automatically)
git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
select a branch, I select xen/master (version 2.6.32.36):
$ git branch
master
* xen/master

qemu (build by default)

git://xenbits.xen.org/qemu-upstream-unstable.git
$ git branch
* dummy
master

+++ b/tools/Makefile Sat May 26 12:31:01 2012 +0800
@@ -157,6 +157,7 @@ subdir-all-qemu-xen-dir subdir-install-q
--bindir=$(LIBEXEC) \
--datadir=$(SHAREDIR)/qemu-xen \
--disable-kvm \
+ --enable-spice \

SPICE 0.7.1 is build from source code before.

Host is fc8-64bit, but dom0 kernel is replaced as described before.

> Can you give me details about the dom0 used for your tests please?
> For example here are details about my testing dom0:
> Wheezy 64 bit with kernel from package linux-image-3.2.0-2-amd64 version
> 3.2.18-1, package blktap-dkms and all dependency packages for xen 4.2, spice
> and usb redirection.
> -------------------------
> /etc/modules
> ------------
> loop max_loop=64
> xenfs
> xen-evtchn
> blktap
> -------------------------
> hg clone http://xenbits.xen.org/xen-unstable.hg
> vi config/StdGNU.mk # Workaround for Wheezy with multiarch support, there
> are parts that use LIBDIR set here instead of the one in configure (libdir)
> LIBLEAFDIR_x86_64 ?= lib
> vi Config.mk
> PYTHON_PREFIX_ARG =
> -------------------------
> Added some patches:
> - autoconf: add variable for pass arbitrary options to qemu upstream v3
> - tools: Improve make deb
> - libxc: do not "panic" if a kernel is not a bzImage.
> - tools/hotplug/Linux/init.d/: added other xen kernel modules on xencommons
> start
> - 3 patches for add qxl support
>
> -------------------------
> ./configure --enable-qemuu-spice --enable-qemuu-usbredir
> --enable-qemuu-debug
> -------------------------
> make deb
>
> Is qxl someway affected by physical video card of dom0?

I don't think so, because mainly rendered by client but not host.
> Have you installed spice-guest-tools-0.1.exe from spice site, if no what do
> you use for qxl driver?

spice-guest-tools-0.1.exe
> Have you also installed gplpv driver or not?

No.

No driver installed except from spice-guest-tools-0.1.exe.
> Thanks for any reply.

--
Zhou Peng

_______________________________________________
Xen-devel mailing list
Xen-devel [at] lists
http://lists.xen.org/xen-devel

First page Previous page 1 2 Next page Last page  View All Xen devel RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.