xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
* Question about hvmloader, vgabios and qxl problem
@ 2012-04-06  8:09 Fantu
  2012-04-10 10:17 ` Fantu
  2012-04-10 10:26 ` Ian Campbell
  0 siblings, 2 replies; 3+ messages in thread
From: Fantu @ 2012-04-06  8:09 UTC (permalink / raw)
  To: xen-devel

I spent several days to test xen-unstable with qemu upstream and spice qxl
usbredirection, I found several problems resolved or resolution in progress.
Unfortunately there is a problem that I can not fix or workaround, the qxl
graphic, with qemu and seabios unstable working but with ram assigned not
working more than 4 mb.
There is something missing or wrong in the initialization of the xen domU
that prevents the proper use of videoram with qxl but when I did not find
exactly what.
I am currently looking hvmloader and vgabios, apparently they did not
provide support for qxl and more videoram, so maybe the problem is there.
Vgabios is not updated to last version with qxl support, is used by qemu
upstream and need to be updated?
Hvmloader need to be modify for qxl support?
Thanks for any reply and sorry for bad english.

--
View this message in context: http://xen.1045712.n5.nabble.com/Question-about-hvmloader-vgabios-and-qxl-problem-tp5622311p5622311.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Question about hvmloader, vgabios and qxl problem
  2012-04-06  8:09 Question about hvmloader, vgabios and qxl problem Fantu
@ 2012-04-10 10:17 ` Fantu
  2012-04-10 10:26 ` Ian Campbell
  1 sibling, 0 replies; 3+ messages in thread
From: Fantu @ 2012-04-10 10:17 UTC (permalink / raw)
  To: xen-devel

I'm still desperately trying to solve the problem videoram/qxl.
About hvmloader I see pci.c on tools/firmware/hvmloader, virtual_vga
considers only std and cirrus, this can cause problems?
About memory allocation on libxc have limit for effective videoram
allocation to 16mb? I see for example this old patch:
changeset 19036 with allowing user to specify up to 16mb of vram
I see change on tools/libxc/xc_hvm_build.c but I not understand if limit
memory allocation or is other.
About libxl there are recent patch about ram/videoram fix but I not sure I
am not sure of the complete resolution of the problem in libxl, here too,
unfortunately I have trouble understanding some things and I can not find
any problems.
Thanks for any reply and sorry for bad english.

--
View this message in context: http://xen.1045712.n5.nabble.com/Question-about-hvmloader-vgabios-and-qxl-problem-tp5622311p5629542.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Question about hvmloader, vgabios and qxl problem
  2012-04-06  8:09 Question about hvmloader, vgabios and qxl problem Fantu
  2012-04-10 10:17 ` Fantu
@ 2012-04-10 10:26 ` Ian Campbell
  1 sibling, 0 replies; 3+ messages in thread
From: Ian Campbell @ 2012-04-10 10:26 UTC (permalink / raw)
  To: Fantu; +Cc: xen-devel@lists.xensource.com

On Fri, 2012-04-06 at 09:09 +0100, Fantu wrote:

> I am currently looking hvmloader and vgabios, apparently they did not
> provide support for qxl and more videoram, so maybe the problem is there.

> Vgabios is not updated to last version with qxl support, is used by qemu
> upstream and need to be updated?

VGA BIOS is not used with SeaBIOS (and therefore not used with upstream
qemu), it is only used with ROMBIOS. SeaBIOS loads any option ROMs
directly from the (emulated) hardware devices (like a real BIOS would).

Ian.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2012-04-10 10:26 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-04-06  8:09 Question about hvmloader, vgabios and qxl problem Fantu
2012-04-10 10:17 ` Fantu
2012-04-10 10:26 ` Ian Campbell

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).