search for: stdvga

Hello, xl.cfg.pod.5 documentation tweaks/improvements: - videoram: Document that only qemu-xen-traditional device-model currently supports changing the amount of video memory for stdvga graphics device. - videoram: Better document the default amount of videoram for both stdvga and Cirrus. - stdvga: Add a note that stdvga allows bigger amount of videoram and bigger resolutions. Signed-off-by: Pasi Kärkkäinen <pasik@iki.fi> --- docs/man/xl.cfg.pod.5.orig 2012-08-25 0...

document update in xl.cfg.pod.5 for ''stdvga=1'' by default Signed-off-by: Yongjie Ren <yongjie.ren@intel.com> diff -r b98feb4d6359 docs/man/xl.cfg.pod.5 --- a/docs/man/xl.cfg.pod.5 Tue Jun 26 12:56:31 2012 +0800 +++ b/docs/man/xl.cfg.pod.5 Tue Jun 26 13:27:19 2012 +0800 @@ -718,9 +718,10 @@ =item B<stdvga=BOOLEAN> S...

...; And yes, if bios pokes at a specific bar then we do > need to list this info in the virtio spec so this makes > it an issue that is virtio related. Hmm, virtio-vga is a two-in-one device basically. When virtio is enabled it behaves like virtio-gpu-pci, otherwise it behaves very simliar to stdvga. So you need to know nothing about virtio to handle the vga side, and I want keep it that way. When no vga compatibility is needed there always is the option to just use virtio-gpu-pci instead. > Yes, it's not about what we put there now. It's about being able > to move things abou...

...; And yes, if bios pokes at a specific bar then we do > need to list this info in the virtio spec so this makes > it an issue that is virtio related. Hmm, virtio-vga is a two-in-one device basically. When virtio is enabled it behaves like virtio-gpu-pci, otherwise it behaves very simliar to stdvga. So you need to know nothing about virtio to handle the vga side, and I want keep it that way. When no vga compatibility is needed there always is the option to just use virtio-gpu-pci instead. > Yes, it's not about what we put there now. It's about being able > to move things abou...

...n/xl.cfg.pod.5 @@ -1009,14 +1009,16 @@ in the B<VFB_SPEC_STRING> for configuring virtual frame buffer devices Sets the amount of RAM which the emulated video card will contain, which in turn limits the resolutions and bit depths which will be available. -The default amount of video ram for stdvga is 8MB which is sufficient -for e.g. 1600x1200 at 32bpp and videoram option is currently working -only when using the qemu-xen-traditional device-model. - -When using the emulated Cirrus graphics card (B<vga="cirrus">) -the amount of video ram is fixed at 4MB which is sufficient -fo...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everybody, i can run windows nt properly under xen hvm. However when i use cirrus logic driver if i switch of screen size i have green or yellow flood. I tried to use stdvga but when i use it i have only 16bit color and only 800x600. What kind of driver can i use with stdvga ? regards, - -- Alexandre CABROL PERALES - -- Ingenieur Securite des Systemes d''Information Mob. : 06.98.82.03.06 Mail : alexandre.cabrol@artal.fr Key fingerprint = 1E6B B8DF 5001...

Hi! In struct ioreq are the "addr", "size", "count" and "data" 64bit fields. So handle 64bit operations in stdvga instead of throwing away the upper 32bits (see attached patch). This fixes some noisy xen messages like "invalid io size: 8". Signed-off-by: Christoph Egger <Christoph.Egger@amd.com> -- AMD Saxony, Dresden, Germany Operating System Research Center Legal Information: AMD Saxon...

Is it possible to change stdvga after installation of Windows 7 as PV domU? Tnx. -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 _______________________________________________ xen-discuss mailing list xen-discuss@opensolaris.org

Hi all, This is the test report of xen-unstable tree. There are one bug found. Version Info: ================================================================= xen-changeset: 25256 Dom0: linux.git 3.1.0-rc7 (commit: d93dc5c...) ================================================================= New issue(1) ============== 1. cpu weight out of range error when create hvm domU

...N) irq.c:270: Dom14 PCI link 3 changed 5 -> 0 (XEN) irq.c:2234: dom14: pirq 51 or emuirq 23 already mapped (XEN) vmsi.c:108:d32767 Unsupported delivery mode 3 (XEN) emulate.c:88:d14 bad mmio size 16 (XEN) io.c:199:d14 MMIO emulation failed @ 0033:7fa98cc628b4: 66 0f 7f 0f 0f 28 56 10 0f 29 (XEN) stdvga.c:147:d14 entering stdvga and caching modes (XEN) stdvga.c:151:d14 leaving stdvga (XEN) emulate.c:88:d14 bad mmio size 16 (XEN) io.c:199:d14 MMIO emulation failed @ 0033:7f28312e98b4: 66 0f 7f 0f 0f 28 56 10 0f 29 (XEN) stdvga.c:147:d14 entering stdvga and caching modes Xen 4.2 unstable on Ubuntu...

Il 27/05/2014 17:05, Fabio Fantoni ha scritto: > Usage: > vga="qxl" > > Qxl vga support many resolutions that not supported by stdvga, > mainly the 16:9 ones and other high up to 2560x1600. > With QXL you can get improved performance and smooth video also > with high resolutions and high quality. > Require their drivers installed in the domU and spice used > otherwise act as a simple stdvga. > > Signed-off-by...

The existing stdvga driver from xen-unstable tools/ioemu/hw/vga* does not save the emulated VGA memory contents. The symptoms include video malfunction after restore, including black screen (which can often be fixed by asking the guest to redraw) but also missing font setup etc. The attached patch fixes this by savin...

...Hoffmann wrote: > Hi, > >> can we reach agreement on whether vsock should be involved in this? > > I think the best approach would be to have guest proxy and host proxy > use vsock for the wayland protocol. Use a wayland protocol extension to > reference the buffers in stdvga / ivshmem / virtio-gpu. Only the two > proxies need to understand the extension, the client <=> guest proxy and > host proxy <=> server communication would be standard wayland protocol. Thanks for the ideas. What I haven't understood yet is how you see the actual passing of...

...Hoffmann wrote: > Hi, > >> can we reach agreement on whether vsock should be involved in this? > > I think the best approach would be to have guest proxy and host proxy > use vsock for the wayland protocol. Use a wayland protocol extension to > reference the buffers in stdvga / ivshmem / virtio-gpu. Only the two > proxies need to understand the extension, the client <=> guest proxy and > host proxy <=> server communication would be standard wayland protocol. Thanks for the ideas. What I haven't understood yet is how you see the actual passing of...

...mU and can connect to it over VNC running in dom0. However I cannot increase the resolution above 800x600. I would really like 1024x786. In the Ubuntu guest it says there graphics card is a VESA compatible, and only has 600x400 and 800x600 screen resolutions. My domU config is shown below. I have stdvga=0 I searched the mailing lists, and it said stdvga=1 may offer more video modes, but if I do that, then the domU boots, but I just get a grey screeen with a mouse pointer. No actual desktop/login window etc. So I guess my question is, using HVM and display with VNC, is it normal to be able to get...

...specific bar then we do > > need to list this info in the virtio spec so this makes > > it an issue that is virtio related. > > Hmm, virtio-vga is a two-in-one device basically. When virtio is > enabled it behaves like virtio-gpu-pci, otherwise it behaves very > simliar to stdvga. So you need to know nothing about virtio to handle > the vga side, and I want keep it that way. > > When no vga compatibility is needed there always is the option to just > use virtio-gpu-pci instead. > > > Yes, it's not about what we put there now. It's about being...

...specific bar then we do > > need to list this info in the virtio spec so this makes > > it an issue that is virtio related. > > Hmm, virtio-vga is a two-in-one device basically. When virtio is > enabled it behaves like virtio-gpu-pci, otherwise it behaves very > simliar to stdvga. So you need to know nothing about virtio to handle > the vga side, and I want keep it that way. > > When no vga compatibility is needed there always is the option to just > use virtio-gpu-pci instead. > > > Yes, it's not about what we put there now. It's about being...

...', ''fdb'', ''audio'', + dmargs = [ ''cdrom'', ''boot'', ''fda'', ''fdb'', ''soundhw'', ''localtime'', ''serial'', ''stdvga'', ''isa'', ''vcpus'', ''usb'', ''usbdevice''] ret = [] @@ -258,10 +258,9 @@ class HVMImageHandler(ImageHandler): # python doesn''t allow ''-'' in variable names...

...hda,w'' ] memory = 256 vcpus = 2 builder = ''hvm'' device_model = ''/usr/lib/xen/bin/qemu-dm'' kernel = ''/usr/lib/xen/boot/hvmloader'' name = ''vm1'' vif = [ ''type=ioemu,mac=00:16:3e:cf:ec:bd,bridge=xenbr0'' ] stdvga = 0 acpi=1 apic=1 sdl = 1 vnc = 0 vncviewer = 0 ne2000 = 0 localtime = 0 on_poweroff = ''destroy'' on_reboot = ''destroy'' on_crash = ''destroy'' boot = ''d'' cdrom = ''/dev/hdb'' I use this graphiccard: 05:02.0 VGA co...