Re: [Xen-devel] Unable to get QXL vga working

[ZhouPeng <zpengxen@xxxxxxxxx>]

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@xxxxxxxxxx> 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@xxxxxxxxxxxxx> wrote:
>> > On Thu, 3 May 2012, ZhouPeng wrote:
>> >> >> > What do you mean by "disabling graphic"? Do you mean disabling the 
>> >> >> > vga
>> >> >> > card?
>> >> >> No, not disable the vga card.
>> >> >> But booting in Text mode.
>> >> >
>> >> > Then you are manually starting X11 with the spice driver?
>> >> Always in text mode.
>> >> Never start X11.
>> >> Using stdard vga but not qxl-vga.
>> >
>> > so you didn't actually test qxl at all, did you?
>> Didn't test qxl but only spice.
>
> So to return to my question at the start of this thread -- is qxl
> something you would be interested in supporting? (I think you said yes,
> but we've been somewhat sidetracked on the distinction between SPICE
> support and QXL support).
>
> In any case this is definitely 4.3 material IMHO since we are now
> feature frozen for 4.2.
>
> Ian.
>



-- 
Zhou Peng

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