Unable to get QXL vga working

Unable to get QXL vga working

[Fantu]

Dom0:
Wheezy 64 bit with kernel from package linux-image-3.2.0-2-amd64 version
3.2.15-1, package blktap-dkms and all dependency packages for xen, spice and
usb redirection.
-------------------------
/etc/modules
------------
loop max_loop=64
xenfs
xen-evtchn
blktap
-------------------------
hg clone http://xenbits.xen.org/xen-unstable.hg (in this build changeset is
25249:a4e7fce6ee2b)
vi Makefile # removed dist-kernel to not compile kernel
-------------------------
vi Config.mk # qemu upstream unstable and seabios upstream unstable for
various spice and qxl bugfix
------------
QEMU_UPSTREAM_URL ?= git://git.qemu.org/qemu.git
SEABIOS_UPSTREAM_URL ?= git://git.seabios.org/seabios.git
SEABIOS_UPSTREAM_TAG ?= rel-1.7.0
-------------------------
Added some patches:
- autoconf: add variable for pass arbitrary options to qemu upstream v3
- tools: Improve make deb
-------------------------
./configure --enable-qemuu-spice --enable-qemuu-usbredir
--enable-qemuu-debug
-------------------------
make deb

Tested it on Windows XP domU with this xl configuration file:
-------------------------------
XP.cfg
--------- 
name='XP'
builder="hvm"
memory=1024
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/XP.disk1.xm,raw,hda,rw',',raw,hdb,ro,cdrom']
disk=['/mnt/vm/disks/XP.disk1.xm,raw,hda,rw']
boot='cd'
xen_platform_pci=1
viridian=1
device_model_version="qemu-xen"
#device_model_override="/usr/lib/xen/bin/qemu-debug.sh"
#vnc=1
#vncunused=1
#vnclisten="0.0.0.0"
#keymap="it"
spice=1
spicehost="0.0.0.0"
spiceport=6000
spicedisable_ticketing=1
on_poweroff="destroy"
on_reboot="restart"
on_crash="destroy"
stdvga=1
#device_model_args=["-vga qxl -global qxl-vga.vram_size_mb=16"]
#videoram=128
#device_model_args=["-vga qxl"]
-------------------------------
With stdvga option domU is working but graphic performance is poor with
spice.


With QXL vga option domU 
-------------------------------
videoram=128
device_model_args=["-vga qxl"]
stdvga=0
-------------------------------
DomU not start, from qemu log:
qemu-system-i386: -vga qxl: invalid option

But the option is correct and if I add:
device_model_override="/usr/lib/xen/bin/qemu-debug.sh"

qemu-debug.sh launches the same qemu-system-i386 with same options and domU
starts.
DomU sees the QXL vga but only with 4 mb allocated and/or usabled instead of
64 mb of qemu default.

We need domUs with good graphic performance, also with high resolution and
also multimedia.
We can not use gfx passthrough on our dom0s because of hardware limitation
of dell server.
QXL seems to be the only way to go.

We are testing this setup several months without success on xen.
Some initial xl and qemu ram/videoram bugs are now fixed but may be there
are other in xen not found for now.

We noticed one particular thing:

without qxl:
xc: info: VIRTUAL MEMORY ARRANGEMENT:
  Loader:        0000000000100000->000000000019dc88
  TOTAL:         0000000000000000->000000003f800000
  ENTRY ADDRESS: 0000000000100000

with qxl:
xc: info: VIRTUAL MEMORY ARRANGEMENT:
  Loader:        0000000000100000->000000000019dc88
  TOTAL:         0000000000000000->0000000038000000
  ENTRY ADDRESS: 0000000000100000

The total memory with qxl should be equal or major than total memory without
qxl.
There is something wrong about videoram, i don't know if in xl or other part
of xen.

Please someone help me to solve this problem?

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

Re: Unable to get QXL vga working

[Ian Campbell]

CCing Zhou Peng who originally added spice support to xl. Zhou, are you
interested in supporting this feature?

On Thu, 2012-04-26 at 16:23 +0100, Fantu wrote:
> Dom0:
> Wheezy 64 bit with kernel from package linux-image-3.2.0-2-amd64 version
> 3.2.15-1, package blktap-dkms and all dependency packages for xen, spice and
> usb redirection.
> -------------------------
> /etc/modules
> ------------
> loop max_loop=64
> xenfs
> xen-evtchn
> blktap
> -------------------------
> hg clone http://xenbits.xen.org/xen-unstable.hg (in this build changeset is
> 25249:a4e7fce6ee2b)
> vi Makefile # removed dist-kernel to not compile kernel
> -------------------------
> vi Config.mk # qemu upstream unstable and seabios upstream unstable for
> various spice and qxl bugfix
> ------------
> QEMU_UPSTREAM_URL ?= git://git.qemu.org/qemu.git
> SEABIOS_UPSTREAM_URL ?= git://git.seabios.org/seabios.git
> SEABIOS_UPSTREAM_TAG ?= rel-1.7.0
> -------------------------
> Added some patches:
> - autoconf: add variable for pass arbitrary options to qemu upstream v3
> - tools: Improve make deb
> -------------------------
> ./configure --enable-qemuu-spice --enable-qemuu-usbredir
> --enable-qemuu-debug
> -------------------------
> make deb
> 
> Tested it on Windows XP domU with this xl configuration file:
> -------------------------------
> XP.cfg
> --------- 
> name='XP'
> builder="hvm"
> memory=1024
> 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/XP.disk1.xm,raw,hda,rw',',raw,hdb,ro,cdrom']
> disk=['/mnt/vm/disks/XP.disk1.xm,raw,hda,rw']
> boot='cd'
> xen_platform_pci=1
> viridian=1
> device_model_version="qemu-xen"
> #device_model_override="/usr/lib/xen/bin/qemu-debug.sh"
> #vnc=1
> #vncunused=1
> #vnclisten="0.0.0.0"
> #keymap="it"
> spice=1
> spicehost="0.0.0.0"
> spiceport=6000
> spicedisable_ticketing=1
> on_poweroff="destroy"
> on_reboot="restart"
> on_crash="destroy"
> stdvga=1
> #device_model_args=["-vga qxl -global qxl-vga.vram_size_mb=16"]
> #videoram=128
> #device_model_args=["-vga qxl"]
> -------------------------------
> With stdvga option domU is working but graphic performance is poor with
> spice.
> 
> 
> With QXL vga option domU 
> -------------------------------
> videoram=128
> device_model_args=["-vga qxl"]
> stdvga=0
> -------------------------------
> DomU not start, from qemu log:
> qemu-system-i386: -vga qxl: invalid option
> 
> But the option is correct and if I add:
> device_model_override="/usr/lib/xen/bin/qemu-debug.sh"
> 
> qemu-debug.sh launches the same qemu-system-i386 with same options and domU
> starts.
> DomU sees the QXL vga but only with 4 mb allocated and/or usabled instead of
> 64 mb of qemu default.
> 
> We need domUs with good graphic performance, also with high resolution and
> also multimedia.
> We can not use gfx passthrough on our dom0s because of hardware limitation
> of dell server.
> QXL seems to be the only way to go.
> 
> We are testing this setup several months without success on xen.
> Some initial xl and qemu ram/videoram bugs are now fixed but may be there
> are other in xen not found for now.
> 
> We noticed one particular thing:
> 
> without qxl:
> xc: info: VIRTUAL MEMORY ARRANGEMENT:
>   Loader:        0000000000100000->000000000019dc88
>   TOTAL:         0000000000000000->000000003f800000
>   ENTRY ADDRESS: 0000000000100000
> 
> with qxl:
> xc: info: VIRTUAL MEMORY ARRANGEMENT:
>   Loader:        0000000000100000->000000000019dc88
>   TOTAL:         0000000000000000->0000000038000000
>   ENTRY ADDRESS: 0000000000100000
> 
> The total memory with qxl should be equal or major than total memory without
> qxl.
> There is something wrong about videoram, i don't know if in xl or other part
> of xen.
> 
> Please someone help me to solve this problem?
> 
> --
> View this message in context: http://xen.1045712.n5.nabble.com/Unable-to-get-QXL-vga-working-tp5667919p5667919.html
> Sent from the Xen - Dev mailing list archive at Nabble.com.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

Re: Unable to get QXL vga working

[ZhouPeng]

Hi Fantu,

Thanks for your response.

xl doesn't support qxl-related option at the moment.
I will test upstream-qemu-xen these days, and if it works well
with qxl device, I will be glad to add qxl support to xl.

Best,

On Thu, Apr 26, 2012 at 11:39 PM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
> CCing Zhou Peng who originally added spice support to xl. Zhou, are you
> interested in supporting this feature?
>
> On Thu, 2012-04-26 at 16:23 +0100, Fantu wrote:
>> Dom0:
>> Wheezy 64 bit with kernel from package linux-image-3.2.0-2-amd64 version
>> 3.2.15-1, package blktap-dkms and all dependency packages for xen, spice and
>> usb redirection.
>> -------------------------
>> /etc/modules
>> ------------
>> loop max_loop=64
>> xenfs
>> xen-evtchn
>> blktap
>> -------------------------
>> hg clone http://xenbits.xen.org/xen-unstable.hg (in this build changeset is
>> 25249:a4e7fce6ee2b)
>> vi Makefile # removed dist-kernel to not compile kernel
>> -------------------------
>> vi Config.mk # qemu upstream unstable and seabios upstream unstable for
>> various spice and qxl bugfix
>> ------------
>> QEMU_UPSTREAM_URL ?= git://git.qemu.org/qemu.git
>> SEABIOS_UPSTREAM_URL ?= git://git.seabios.org/seabios.git
>> SEABIOS_UPSTREAM_TAG ?= rel-1.7.0
>> -------------------------
>> Added some patches:
>> - autoconf: add variable for pass arbitrary options to qemu upstream v3
>> - tools: Improve make deb
>> -------------------------
>> ./configure --enable-qemuu-spice --enable-qemuu-usbredir
>> --enable-qemuu-debug
>> -------------------------
>> make deb
>>
>> Tested it on Windows XP domU with this xl configuration file:
>> -------------------------------
>> XP.cfg
>> ---------
>> name='XP'
>> builder="hvm"
>> memory=1024
>> 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/XP.disk1.xm,raw,hda,rw',',raw,hdb,ro,cdrom']
>> disk=['/mnt/vm/disks/XP.disk1.xm,raw,hda,rw']
>> boot='cd'
>> xen_platform_pci=1
>> viridian=1
>> device_model_version="qemu-xen"
>> #device_model_override="/usr/lib/xen/bin/qemu-debug.sh"
>> #vnc=1
>> #vncunused=1
>> #vnclisten="0.0.0.0"
>> #keymap="it"
>> spice=1
>> spicehost="0.0.0.0"
>> spiceport=6000
>> spicedisable_ticketing=1
>> on_poweroff="destroy"
>> on_reboot="restart"
>> on_crash="destroy"
>> stdvga=1
>> #device_model_args=["-vga qxl -global qxl-vga.vram_size_mb=16"]
>> #videoram=128
>> #device_model_args=["-vga qxl"]
>> -------------------------------
>> With stdvga option domU is working but graphic performance is poor with
>> spice.
>>
>>
>> With QXL vga option domU
>> -------------------------------
>> videoram=128
>> device_model_args=["-vga qxl"]
>> stdvga=0
>> -------------------------------
>> DomU not start, from qemu log:
>> qemu-system-i386: -vga qxl: invalid option
>>
>> But the option is correct and if I add:
>> device_model_override="/usr/lib/xen/bin/qemu-debug.sh"
>>
>> qemu-debug.sh launches the same qemu-system-i386 with same options and domU
>> starts.
>> DomU sees the QXL vga but only with 4 mb allocated and/or usabled instead of
>> 64 mb of qemu default.
>>
>> We need domUs with good graphic performance, also with high resolution and
>> also multimedia.
>> We can not use gfx passthrough on our dom0s because of hardware limitation
>> of dell server.
>> QXL seems to be the only way to go.
>>
>> We are testing this setup several months without success on xen.
>> Some initial xl and qemu ram/videoram bugs are now fixed but may be there
>> are other in xen not found for now.
>>
>> We noticed one particular thing:
>>
>> without qxl:
>> xc: info: VIRTUAL MEMORY ARRANGEMENT:
>>   Loader:        0000000000100000->000000000019dc88
>>   TOTAL:         0000000000000000->000000003f800000
>>   ENTRY ADDRESS: 0000000000100000
>>
>> with qxl:
>> xc: info: VIRTUAL MEMORY ARRANGEMENT:
>>   Loader:        0000000000100000->000000000019dc88
>>   TOTAL:         0000000000000000->0000000038000000
>>   ENTRY ADDRESS: 0000000000100000
>>
>> The total memory with qxl should be equal or major than total memory without
>> qxl.
>> There is something wrong about videoram, i don't know if in xl or other part
>> of xen.
>>
>> Please someone help me to solve this problem?
>>
>> --
>> View this message in context: http://xen.1045712.n5.nabble.com/Unable-to-get-QXL-vga-working-tp5667919p5667919.html
>> Sent from the Xen - Dev mailing list archive at Nabble.com.
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> http://lists.xen.org/xen-devel
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel



-- 
Zhou Peng

Re: Unable to get QXL vga working

[Fantu]

Zhou Peng wrote
> 
> Hi Fantu,
> 
> Thanks for your response.
> 
> xl doesn't support qxl-related option at the moment.
> I will test upstream-qemu-xen these days, and if it works well
> with qxl device, I will be glad to add qxl support to xl.
> 
> Best,
> 
> On Thu, Apr 26, 2012 at 11:39 PM, Ian Campbell <Ian.Campbell@>
> wrote:
>> CCing Zhou Peng who originally added spice support to xl. Zhou, are you
>> interested in supporting this feature?
>>
>> On Thu, 2012-04-26 at 16:23 +0100, Fantu wrote:
>>> Dom0:
>>> Wheezy 64 bit with kernel from package linux-image-3.2.0-2-amd64 version
>>> 3.2.15-1, package blktap-dkms and all dependency packages for xen, spice
>>> and
>>> usb redirection.
>>> -------------------------
>>> /etc/modules
>>> ------------
>>> loop max_loop=64
>>> xenfs
>>> xen-evtchn
>>> blktap
>>> -------------------------
>>> hg clone http://xenbits.xen.org/xen-unstable.hg (in this build changeset
>>> is
>>> 25249:a4e7fce6ee2b)
>>> vi Makefile # removed dist-kernel to not compile kernel
>>> -------------------------
>>> vi Config.mk # qemu upstream unstable and seabios upstream unstable for
>>> various spice and qxl bugfix
>>> ------------
>>> QEMU_UPSTREAM_URL ?= git://git.qemu.org/qemu.git
>>> SEABIOS_UPSTREAM_URL ?= git://git.seabios.org/seabios.git
>>> SEABIOS_UPSTREAM_TAG ?= rel-1.7.0
>>> -------------------------
>>> Added some patches:
>>> - autoconf: add variable for pass arbitrary options to qemu upstream v3
>>> - tools: Improve make deb
>>> -------------------------
>>> ./configure --enable-qemuu-spice --enable-qemuu-usbredir
>>> --enable-qemuu-debug
>>> -------------------------
>>> make deb
>>>
>>> Tested it on Windows XP domU with this xl configuration file:
>>> -------------------------------
>>> XP.cfg
>>> ---------
>>> name='XP'
>>> builder="hvm"
>>> memory=1024
>>> 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/XP.disk1.xm,raw,hda,rw',',raw,hdb,ro,cdrom']
>>> disk=['/mnt/vm/disks/XP.disk1.xm,raw,hda,rw']
>>> boot='cd'
>>> xen_platform_pci=1
>>> viridian=1
>>> device_model_version="qemu-xen"
>>> #device_model_override="/usr/lib/xen/bin/qemu-debug.sh"
>>> #vnc=1
>>> #vncunused=1
>>> #vnclisten="0.0.0.0"
>>> #keymap="it"
>>> spice=1
>>> spicehost="0.0.0.0"
>>> spiceport=6000
>>> spicedisable_ticketing=1
>>> on_poweroff="destroy"
>>> on_reboot="restart"
>>> on_crash="destroy"
>>> stdvga=1
>>> #device_model_args=["-vga qxl -global qxl-vga.vram_size_mb=16"]
>>> #videoram=128
>>> #device_model_args=["-vga qxl"]
>>> -------------------------------
>>> With stdvga option domU is working but graphic performance is poor with
>>> spice.
>>>
>>>
>>> With QXL vga option domU
>>> -------------------------------
>>> videoram=128
>>> device_model_args=["-vga qxl"]
>>> stdvga=0
>>> -------------------------------
>>> DomU not start, from qemu log:
>>> qemu-system-i386: -vga qxl: invalid option
>>>
>>> But the option is correct and if I add:
>>> device_model_override="/usr/lib/xen/bin/qemu-debug.sh"
>>>
>>> qemu-debug.sh launches the same qemu-system-i386 with same options and
>>> domU
>>> starts.
>>> DomU sees the QXL vga but only with 4 mb allocated and/or usabled
>>> instead of
>>> 64 mb of qemu default.
>>>
>>> We need domUs with good graphic performance, also with high resolution
>>> and
>>> also multimedia.
>>> We can not use gfx passthrough on our dom0s because of hardware
>>> limitation
>>> of dell server.
>>> QXL seems to be the only way to go.
>>>
>>> We are testing this setup several months without success on xen.
>>> Some initial xl and qemu ram/videoram bugs are now fixed but may be
>>> there
>>> are other in xen not found for now.
>>>
>>> We noticed one particular thing:
>>>
>>> without qxl:
>>> xc: info: VIRTUAL MEMORY ARRANGEMENT:
>>>   Loader:        0000000000100000->000000000019dc88
>>>   TOTAL:         0000000000000000->000000003f800000
>>>   ENTRY ADDRESS: 0000000000100000
>>>
>>> with qxl:
>>> xc: info: VIRTUAL MEMORY ARRANGEMENT:
>>>   Loader:        0000000000100000->000000000019dc88
>>>   TOTAL:         0000000000000000->0000000038000000
>>>   ENTRY ADDRESS: 0000000000100000
>>>
>>> The total memory with qxl should be equal or major than total memory
>>> without
>>> qxl.
>>> There is something wrong about videoram, i don't know if in xl or other
>>> part
>>> of xen.
>>>
>>> Please someone help me to solve this problem?
>>>
>>> --
>>> View this message in context:
>>> http://xen.1045712.n5.nabble.com/Unable-to-get-QXL-vga-working-tp5667919p5667919.html
>>> Sent from the Xen - Dev mailing list archive at Nabble.com.
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@.xen
>>> http://lists.xen.org/xen-devel
>>
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@.xen
>> http://lists.xen.org/xen-devel
> 
> 
> 
> -- 
> Zhou Peng
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@.xen
> http://lists.xen.org/xen-devel
> 


Thanks for reply, about QXL some patches need to be backported from qemu
upstream unstable to qemu upstream xen, now I don't know exactly which of
them solve the domU boot problem with spice and qxl, with qemu and seabios
of xen (1.0.1) doesn't work while with qemu and seabios unstable it does.
There are also some videoram bug or problem on xen, probably bugfix/patch
are necessary also outside of libxl, I tried to look for the problem and
solve it myself but I don't have enough knowledge now.

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

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

Re: Unable to get QXL vga working

[Fantu]

Zhou Peng wrote
> 
> Hi Fantu,
> 
> Thanks for your response.
> 
> xl doesn't support qxl-related option at the moment.
> I will test upstream-qemu-xen these days, and if it works well
> with qxl device, I will be glad to add qxl support to xl.
> 
Hello, any news about this?
Thanks in advance


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

Re: Unable to get QXL vga working

[ZhouPeng]

On Wed, May 2, 2012 at 4:21 PM, Fantu <fantonifabio@tiscali.it> wrote:
>
> Zhou Peng wrote
>>
>> Hi Fantu,
>>
>> Thanks for your response.
>>
>> xl doesn't support qxl-related option at the moment.
>> I will test upstream-qemu-xen these days, and if it works well
>> with qxl device, I will be glad to add qxl support to xl.
>>
> Hello, any news about this?
> Thanks in advance

It seems you are using the upstream-qemu.
There are some special patches for upstream-qemu-xen(I don't track if all the
patches have been accepted by qemu)

The git repos for upstream-qemu-xen:
  Stefano Stabellini's tree:
git://xenbits.xen.org/people/sstabellini/qemu-dm.git
  Anthony's tree: git://xenbits.xen.org/people/aperard/qemu-dm.git

I am watching upstream-qemu-xen's progress too, but I have not tracked
it for months.

I was plan to test the latest upstream-qemu-xen and response to you,
but I encounter a problem when preparing the environment using the upstream xen:
  # xl list
  libxl: error: libxl.c:506:libxl_list_domain: geting domain info
list: Operation not permitted
  libxl_domain_infolist failed.

So I suggest you  to have a try of upstream-qemu-xen if not yet.
In my test many months ago, it didn't support graphic, and spice was tested
with linux-hvm disabling graphic.

How to configure upstream-qemu-xen:
./configure --target-list=i386-softmmu --enable-spice
   --enable-xen --extra-cflags=-I${path-to-xen}/dist/install/usr/include
   --extra-ldflags=-L${path-to-xen}/dist/install/usr/lib

CCing to Stefano, who may help you on upstream-qemu-xen.
>
> --
> View this message in context: http://xen.1045712.n5.nabble.com/Unable-to-get-QXL-vga-working-tp5667919p5679908.html
> Sent from the Xen - Dev mailing list archive at Nabble.com.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel



-- 
Zhou Peng

Re: Unable to get QXL vga working

[Fantu]

upstream-qemu-xen extra patches are included in upstream-qemu unstable (now
at 1.1-rc0)
I can run hvm domU correctly, on xen-unstable with xl, also with spice.
Some info about my last test system:
Dom0:
Wheezy 64 bit with kernel from package linux-image-3.2.0-2-amd64 version
3.2.15-1, package blktap-dkms and all dependency packages for xen, spice and
usb redirection.
-------------------------
/etc/modules
------------
loop max_loop=64
xenfs
xen-evtchn
blktap
-------------------------
hg clone http://xenbits.xen.org/xen-unstable.hg (in this build changeset is
25249:a4e7fce6ee2b)
vi Makefile # removed dist-kernel to not compile kernel
-------------------------
Added some patches:
- autoconf: add variable for pass arbitrary options to qemu upstream v3
- tools: Improve make deb
-------------------------
./configure --enable-qemuu-spice --enable-qemuu-usbredir
--enable-qemuu-debug
-------------------------
make deb

One domU xl configuration file:
---------------------------------
XP.cfg
-------------
name='XP'
builder="hvm"
memory=1024
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/XP.disk1.xm,raw,hda,rw']
boot='cd'
xen_platform_pci=1
viridian=1
device_model_version="qemu-xen"
#vnc=1
#vncunused=1
#vnclisten="0.0.0.0"
#keymap="it"
spice=1
spicehost="0.0.0.0"
spiceport=6000
spicedisable_ticketing=1
on_poweroff="destroy"
on_reboot="restart"
on_crash="destroy"
stdvga=1
---------------------------------

About QXL I tried to add:
stdvga=0
videoram=128
device_model_args=["-device","qxl-vga"]

About qxl there are problems about videoram not allocated or not used over 4
mb (same as default cirrus vga).
At the moment I haven't found solution for this problem, probably some
bugfix and/or change are needed on xen.

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

Re: Unable to get QXL vga working / videomem over 4MB issue

[Pasi Kärkkäinen]

On Thu, May 03, 2012 at 05:28:44AM -0700, Fantu wrote:
> 
> About qxl there are problems about videoram not allocated or not used over 4
> mb (same as default cirrus vga).
> At the moment I haven't found solution for this problem, probably some
> bugfix and/or change are needed on xen.
> 

Is this a regression in xen-unstable compared to xen 4.1 ? 

afaik you can get at least 16 MB of video memory for HVM guest with Xen 4.1.

-- Pasi

Re: Unable to get QXL vga working / videomem over 4MB issue

[Fantu]

Pasi Kärkkäinen wrote
> 
> On Thu, May 03, 2012 at 05:28:44AM -0700, Fantu wrote:
>> 
>> About qxl there are problems about videoram not allocated or not used
>> over 4
>> mb (same as default cirrus vga).
>> At the moment I haven't found solution for this problem, probably some
>> bugfix and/or change are needed on xen.
>> 
> 
> Is this a regression in xen-unstable compared to xen 4.1 ? 
> 
> afaik you can get at least 16 MB of video memory for HVM guest with Xen
> 4.1.
> 
> -- Pasi
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@.xen
> http://lists.xen.org/xen-devel
> 
Thanks for reply
Probably xen-unstable with qemu upstream doesn't support videoram setting.
qxl default videoram is 64 mb but I also tried to set 16 mb without result,
it always see only 4 mb, not enough for correct working qxl.

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

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

Re: Unable to get QXL vga working / videomem over 4MB issue

[Pasi Kärkkäinen]

On Thu, May 03, 2012 at 07:27:11AM -0700, Fantu wrote:
> 
> Pasi Kärkkäinen wrote
> > 
> > On Thu, May 03, 2012 at 05:28:44AM -0700, Fantu wrote:
> >> 
> >> About qxl there are problems about videoram not allocated or not used
> >> over 4
> >> mb (same as default cirrus vga).
> >> At the moment I haven't found solution for this problem, probably some
> >> bugfix and/or change are needed on xen.
> >> 
> > 
> > Is this a regression in xen-unstable compared to xen 4.1 ? 
> > 
> > afaik you can get at least 16 MB of video memory for HVM guest with Xen
> > 4.1.
> > 
> > -- Pasi
> > 
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@.xen
> > http://lists.xen.org/xen-devel
> > 
> Thanks for reply
> Probably xen-unstable with qemu upstream doesn't support videoram setting.
> qxl default videoram is 64 mb but I also tried to set 16 mb without result,
> it always see only 4 mb, not enough for correct working qxl.
> 

Ok. If you use qemu-upstream and cirrus/stdvga (without qxl), does videomem >4MB work then ?

-- Pasi

Re: Unable to get QXL vga working / videomem over 4MB issue

[Fantu]

Pasi Kärkkäinen wrote
> 
> On Thu, May 03, 2012 at 07:27:11AM -0700, Fantu wrote:
>> 
>> Pasi Kärkkäinen wrote
>> > 
>> > On Thu, May 03, 2012 at 05:28:44AM -0700, Fantu wrote:
>> >> 
>> >> About qxl there are problems about videoram not allocated or not used
>> >> over 4
>> >> mb (same as default cirrus vga).
>> >> At the moment I haven't found solution for this problem, probably some
>> >> bugfix and/or change are needed on xen.
>> >> 
>> > 
>> > Is this a regression in xen-unstable compared to xen 4.1 ? 
>> > 
>> > afaik you can get at least 16 MB of video memory for HVM guest with Xen
>> > 4.1.
>> > 
>> > -- Pasi
>> > 
>> > 
>> > _______________________________________________
>> > Xen-devel mailing list
>> > Xen-devel@.xen
>> > http://lists.xen.org/xen-devel
>> > 
>> Thanks for reply
>> Probably xen-unstable with qemu upstream doesn't support videoram
>> setting.
>> qxl default videoram is 64 mb but I also tried to set 16 mb without
>> result,
>> it always see only 4 mb, not enough for correct working qxl.
>> 
> 
> Ok. If you use qemu-upstream and cirrus/stdvga (without qxl), does
> videomem >4MB work then ?
> 
> -- Pasi
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@.xen
> http://lists.xen.org/xen-devel
> 
No, always 4 mb, also with cirrus or stdvga videoram setting not work.

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

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

Re: Unable to get QXL vga working / videomem over 4MB issue

[Ian Campbell]

(putting Pasi back in the CC, please retain CCs on xen-devel)

On Fri, 2012-05-04 at 09:23 +0100, Fantu wrote:
> Pasi Kärkkäinen wrote
> > Ok. If you use qemu-upstream and cirrus/stdvga (without qxl), does
> > videomem >4MB work then ?
> > 
> No, always 4 mb, also with cirrus or stdvga videoram setting not work.

But with Qemu-xen-traditional it does work?

Anthony -- any idea why the videoram setting doesn't work with upstream
qemu?

Re: Unable to get QXL vga working / videomem over 4MB issue

[Fantu]

Ian Campbell-10 wrote
> 
> (putting Pasi back in the CC, please retain CCs on xen-devel)
> 
> On Fri, 2012-05-04 at 09:23 +0100, Fantu wrote:
>> Pasi Kärkkäinen wrote
>> > Ok. If you use qemu-upstream and cirrus/stdvga (without qxl), does
>> > videomem >4MB work then ?
>> > 
>> No, always 4 mb, also with cirrus or stdvga videoram setting not work.
> 
> But with Qemu-xen-traditional it does work?
> 
> Anthony -- any idea why the videoram setting doesn't work with upstream
> qemu?
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@.xen
> http://lists.xen.org/xen-devel
> 
With qemu-xen-traditional videoram setting with stdvga work.
About Spice on qemu-upstream for now we did only basic tests and it seems to
be working but without qxl  limited to 4 mb many of spices features are not
full working.
Qxl vga can be used also without spice and with videoram to 32 or 64 mb I
think can give better graphic performance with hvm domU.
For now is not good even without multimedia use.

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

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

Re: Unable to get QXL vga working / videomem over 4MB issue

[Anthony PERARD]

On Fri, May 4, 2012 at 9:28 AM, Ian Campbell <Ian.Campbell@citrix.com> 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

Re: Unable to get QXL vga working / videomem over 4MB issue

[Ian Campbell]

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@citrix.com> 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.

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?

Ian.

Re: Unable to get QXL vga working / videomem over 4MB issue

[Pasi Kärkkäinen]

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@citrix.com> 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

Re: Unable to get QXL vga working / videomem over 4MB issue

[Ian Campbell]

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@citrix.com> 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.

Re: Unable to get QXL vga working / videomem over 4MB issue

[Fantu]

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 <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.
>> > 
>> > 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@lists.xen.org
http://lists.xen.org/xen-devel

Re: Unable to get QXL vga working / videomem over 4MB issue

[Anthony PERARD]

> 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@lists.xen.org
http://lists.xen.org/xen-devel

Re: Unable to get QXL vga working / videomem over 4MB issue

[Fantu]

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.

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

Re: Unable to get QXL vga working / videomem over 4MB issue

[Fantu]

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.

Re: Unable to get QXL vga working / videomem over 4MB issue

[Geraldes]

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.

Re: Unable to get QXL vga working / videomem over 4MB issue

[Anthony PERARD]

On Fri, May 11, 2012 at 1:19 PM, Geraldes <heliman@katamail.com> 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

Re: Unable to get QXL vga working

[Stefano Stabellini]

On Thu, 3 May 2012, ZhouPeng wrote:
> On Wed, May 2, 2012 at 4:21 PM, Fantu <fantonifabio@tiscali.it> wrote:
> >
> > Zhou Peng wrote
> >>
> >> Hi Fantu,
> >>
> >> Thanks for your response.
> >>
> >> xl doesn't support qxl-related option at the moment.
> >> I will test upstream-qemu-xen these days, and if it works well
> >> with qxl device, I will be glad to add qxl support to xl.
> >>
> > Hello, any news about this?
> > Thanks in advance
> 
> It seems you are using the upstream-qemu.
> There are some special patches for upstream-qemu-xen(I don't track if all the
> patches have been accepted by qemu)
> 
> The git repos for upstream-qemu-xen:
>   Stefano Stabellini's tree:
> git://xenbits.xen.org/people/sstabellini/qemu-dm.git
>   Anthony's tree: git://xenbits.xen.org/people/aperard/qemu-dm.git
> 
> I am watching upstream-qemu-xen's progress too, but I have not tracked
> it for months.

That is my personal tree. Now upstream QEMU is integrated in
xen-unstable, so the tree that should be used
is: http://xenbits.xen.org/git-http/qemu-upstream-unstable.git


> I was plan to test the latest upstream-qemu-xen and response to you,
> but I encounter a problem when preparing the environment using the upstream xen:
>   # xl list
>   libxl: error: libxl.c:506:libxl_list_domain: geting domain info
> list: Operation not permitted
>   libxl_domain_infolist failed.

This looks like a basic setup issue.


> So I suggest you  to have a try of upstream-qemu-xen if not yet.
> In my test many months ago, it didn't support graphic, and spice was tested
> with linux-hvm disabling graphic.

What do you mean by "disabling graphic"? Do you mean disabling the vga
card?


> How to configure upstream-qemu-xen:
> ./configure --target-list=i386-softmmu --enable-spice
>    --enable-xen --extra-cflags=-I${path-to-xen}/dist/install/usr/include
>    --extra-ldflags=-L${path-to-xen}/dist/install/usr/lib
> 
> CCing to Stefano, who may help you on upstream-qemu-xen.

Yes, it is true that you need to add --enable-spice to the configure
command line options.

Re: Unable to get QXL vga working

[ZhouPeng]

On Thu, May 3, 2012 at 8:46 PM, Stefano Stabellini
<stefano.stabellini@eu.citrix.com> wrote:
> On Thu, 3 May 2012, ZhouPeng wrote:
>> On Wed, May 2, 2012 at 4:21 PM, Fantu <fantonifabio@tiscali.it> wrote:
>> >
>> > Zhou Peng wrote
>> >>
>> >> Hi Fantu,
>> >>
>> >> Thanks for your response.
>> >>
>> >> xl doesn't support qxl-related option at the moment.
>> >> I will test upstream-qemu-xen these days, and if it works well
>> >> with qxl device, I will be glad to add qxl support to xl.
>> >>
>> > Hello, any news about this?
>> > Thanks in advance
>>
>> It seems you are using the upstream-qemu.
>> There are some special patches for upstream-qemu-xen(I don't track if all the
>> patches have been accepted by qemu)
>>
>> The git repos for upstream-qemu-xen:
>>   Stefano Stabellini's tree:
>> git://xenbits.xen.org/people/sstabellini/qemu-dm.git
>>   Anthony's tree: git://xenbits.xen.org/people/aperard/qemu-dm.git
>>
>> I am watching upstream-qemu-xen's progress too, but I have not tracked
>> it for months.
>
> That is my personal tree. Now upstream QEMU is integrated in
> xen-unstable, so the tree that should be used
> is: http://xenbits.xen.org/git-http/qemu-upstream-unstable.git
>
>
>> I was plan to test the latest upstream-qemu-xen and response to you,
>> but I encounter a problem when preparing the environment using the upstream xen:
>>   # xl list
>>   libxl: error: libxl.c:506:libxl_list_domain: geting domain info
>> list: Operation not permitted
>>   libxl_domain_infolist failed.
>
> This looks like a basic setup issue.
>
>
>> So I suggest you  to have a try of upstream-qemu-xen if not yet.
>> In my test many months ago, it didn't support graphic, and spice was tested
>> with linux-hvm disabling graphic.
>
> 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.
>
>> How to configure upstream-qemu-xen:
>> ./configure --target-list=i386-softmmu --enable-spice
>>    --enable-xen --extra-cflags=-I${path-to-xen}/dist/install/usr/include
>>    --extra-ldflags=-L${path-to-xen}/dist/install/usr/lib
>>
>> CCing to Stefano, who may help you on upstream-qemu-xen.
>
> Yes, it is true that you need to add --enable-spice to the configure
> command line options.



-- 
Zhou Peng

Re: Unable to get QXL vga working

[Stefano Stabellini]

[-- Attachment #1: Type: text/plain, Size: 2079 bytes --]

On Thu, 3 May 2012, ZhouPeng wrote:
> On Thu, May 3, 2012 at 8:46 PM, Stefano Stabellini
> <stefano.stabellini@eu.citrix.com> wrote:
> > On Thu, 3 May 2012, ZhouPeng wrote:
> >> On Wed, May 2, 2012 at 4:21 PM, Fantu <fantonifabio@tiscali.it> wrote:
> >> >
> >> > Zhou Peng wrote
> >> >>
> >> >> Hi Fantu,
> >> >>
> >> >> Thanks for your response.
> >> >>
> >> >> xl doesn't support qxl-related option at the moment.
> >> >> I will test upstream-qemu-xen these days, and if it works well
> >> >> with qxl device, I will be glad to add qxl support to xl.
> >> >>
> >> > Hello, any news about this?
> >> > Thanks in advance
> >>
> >> It seems you are using the upstream-qemu.
> >> There are some special patches for upstream-qemu-xen(I don't track if all the
> >> patches have been accepted by qemu)
> >>
> >> The git repos for upstream-qemu-xen:
> >>   Stefano Stabellini's tree:
> >> git://xenbits.xen.org/people/sstabellini/qemu-dm.git
> >>   Anthony's tree: git://xenbits.xen.org/people/aperard/qemu-dm.git
> >>
> >> I am watching upstream-qemu-xen's progress too, but I have not tracked
> >> it for months.
> >
> > That is my personal tree. Now upstream QEMU is integrated in
> > xen-unstable, so the tree that should be used
> > is: http://xenbits.xen.org/git-http/qemu-upstream-unstable.git
> >
> >
> >> I was plan to test the latest upstream-qemu-xen and response to you,
> >> but I encounter a problem when preparing the environment using the upstream xen:
> >>   # xl list
> >>   libxl: error: libxl.c:506:libxl_list_domain: geting domain info
> >> list: Operation not permitted
> >>   libxl_domain_infolist failed.
> >
> > This looks like a basic setup issue.
> >
> >
> >> So I suggest you  to have a try of upstream-qemu-xen if not yet.
> >> In my test many months ago, it didn't support graphic, and spice was tested
> >> with linux-hvm disabling graphic.
> >
> > 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?

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

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

Re: Unable to get QXL vga working

[ZhouPeng]

On Thu, May 3, 2012 at 9:05 PM, Stefano Stabellini
<stefano.stabellini@eu.citrix.com> wrote:
> On Thu, 3 May 2012, ZhouPeng wrote:
>> On Thu, May 3, 2012 at 8:46 PM, Stefano Stabellini
>> <stefano.stabellini@eu.citrix.com> wrote:
>> > On Thu, 3 May 2012, ZhouPeng wrote:
>> >> On Wed, May 2, 2012 at 4:21 PM, Fantu <fantonifabio@tiscali.it> wrote:
>> >> >
>> >> > Zhou Peng wrote
>> >> >>
>> >> >> Hi Fantu,
>> >> >>
>> >> >> Thanks for your response.
>> >> >>
>> >> >> xl doesn't support qxl-related option at the moment.
>> >> >> I will test upstream-qemu-xen these days, and if it works well
>> >> >> with qxl device, I will be glad to add qxl support to xl.
>> >> >>
>> >> > Hello, any news about this?
>> >> > Thanks in advance
>> >>
>> >> It seems you are using the upstream-qemu.
>> >> There are some special patches for upstream-qemu-xen(I don't track if all the
>> >> patches have been accepted by qemu)
>> >>
>> >> The git repos for upstream-qemu-xen:
>> >>   Stefano Stabellini's tree:
>> >> git://xenbits.xen.org/people/sstabellini/qemu-dm.git
>> >>   Anthony's tree: git://xenbits.xen.org/people/aperard/qemu-dm.git
>> >>
>> >> I am watching upstream-qemu-xen's progress too, but I have not tracked
>> >> it for months.
>> >
>> > That is my personal tree. Now upstream QEMU is integrated in
>> > xen-unstable, so the tree that should be used
>> > is: http://xenbits.xen.org/git-http/qemu-upstream-unstable.git
>> >
>> >
>> >> I was plan to test the latest upstream-qemu-xen and response to you,
>> >> but I encounter a problem when preparing the environment using the upstream xen:
>> >>   # xl list
>> >>   libxl: error: libxl.c:506:libxl_list_domain: geting domain info
>> >> list: Operation not permitted
>> >>   libxl_domain_infolist failed.
>> >
>> > This looks like a basic setup issue.
>> >
>> >
>> >> So I suggest you  to have a try of upstream-qemu-xen if not yet.
>> >> In my test many months ago, it didn't support graphic, and spice was tested
>> >> with linux-hvm disabling graphic.
>> >
>> > 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.
-- 
Zhou Peng

Re: Unable to get QXL vga working

[Ian Campbell]

On Thu, 2012-05-03 at 14:05 +0100, ZhouPeng wrote:
> > Then you are manually starting X11 with the spice driver?
> Always in text mode.
> Never start X11.
> Using stdard vga but not qxl-vga.

How is spice being used when you do this?

Ian.

Re: Unable to get QXL vga working

[ZhouPeng]

On Thu, May 3, 2012 at 9:13 PM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
> On Thu, 2012-05-03 at 14:05 +0100, ZhouPeng wrote:
>> > Then you are manually starting X11 with the spice driver?
>> Always in text mode.
>> Never start X11.
>> Using stdard vga but not qxl-vga.
>
> How is spice being used when you do this?
>
> Ian.
>
building upstream-qemu-xen (enable spice and xen)

Add this options in hvm-cfg to enable spice protocal
spice=1
spiceport=6000
spicehost='192.168.1.187'
spicedisable_ticketing = 1

There is some info in
http://code.google.com/p/spice4xen/wiki/Using_Upstream_Qemu

ps:
Two ways to disable graphic boot.
* install a new linux-hvm  without  graphic in install period
* set runlevel in text mode

If boot in graphic, the hvm-windows and hvm-linux will crash down
before booting completely.
-- 
Zhou Peng

Re: Unable to get QXL vga working

[Stefano Stabellini]

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?

Re: Unable to get QXL vga working

[ZhouPeng]

On Thu, May 3, 2012 at 9:56 PM, Stefano Stabellini
<stefano.stabellini@eu.citrix.com> 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.
-- 
Zhou Peng

Re: Unable to get QXL vga working

[Ian Campbell]

On Fri, 2012-05-04 at 02:15 +0100, ZhouPeng wrote:
> On Thu, May 3, 2012 at 9:56 PM, Stefano Stabellini
> <stefano.stabellini@eu.citrix.com> 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.

Re: Unable to get QXL vga working

[ZhouPeng]

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@citrix.com> 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@eu.citrix.com> 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

Re: Unable to get QXL vga working

[Stefano Stabellini]

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.

Re: Unable to get QXL vga working

[ZhouPeng]

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.
-- 
Zhou Peng

Re: Unable to get QXL vga working

[Fabio Fantoni]

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

Re: Unable to get QXL vga working

[ZhouPeng]

On Mon, Jun 11, 2012 at 7:56 PM, Fabio Fantoni <fantonifabio@tiscali.it> wrote:
> 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).

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

Re: Unable to get QXL vga working

[Fabio Fantoni]

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

Il 13/06/2012 11:02, ZhouPeng ha scritto:
> On Mon, Jun 11, 2012 at 7:56 PM, Fabio Fantoni<fantonifabio@tiscali.it>  wrote:
>> 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).
> 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.


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

Re: Unable to get QXL vga working

[ZhouPeng]

On Wed, Jun 13, 2012 at 5:38 PM, Fabio Fantoni <fantonifabio@tiscali.it> wrote:
> Il 13/06/2012 11:02, ZhouPeng ha scritto:
>
>> On Mon, Jun 11, 2012 at 7:56 PM, Fabio Fantoni<fantonifabio@tiscali.it>
>>  wrote:
>>>
>>> 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).
>>
>> 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

Re: Unable to get QXL vga working

[Fabio Fantoni]

[-- Attachment #1.1.1: Type: text/plain, Size: 6391 bytes --]

Il 13/06/2012 13:40, ZhouPeng ha scritto:
> On Wed, Jun 13, 2012 at 5:38 PM, Fabio Fantoni<fantonifabio@tiscali.it>  wrote:
>> Il 13/06/2012 11:02, ZhouPeng ha scritto:
>>
>>> On Mon, Jun 11, 2012 at 7:56 PM, Fabio Fantoni<fantonifabio@tiscali.it>
>>>   wrote:
>>>> 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).
>>> 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.

[-- Attachment #1.1.2: Type: text/html, Size: 9808 bytes --]

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

Re: Unable to get QXL vga working

[ZhouPeng]

On Thu, Jun 14, 2012 at 9:51 PM, Fabio Fantoni <fantonifabio@tiscali.it> wrote:
> Il 13/06/2012 13:40, ZhouPeng ha scritto:
>
> On Wed, Jun 13, 2012 at 5:38 PM, Fabio Fantoni <fantonifabio@tiscali.it>
> wrote:
>
> Il 13/06/2012 11:02, ZhouPeng ha scritto:
>
> On Mon, Jun 11, 2012 at 7:56 PM, Fabio Fantoni<fantonifabio@tiscali.it>
>
>  wrote:
>
> 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).
>
> 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