similar to: [PATCH] xl.cfg: videoram and stdvga documentation improvements

Displaying 20 results from an estimated 3000 matches similar to: "[PATCH] xl.cfg: videoram and stdvga documentation improvements"

2012 Jun 26
1
[PATCH 2/2] document update in xl.cfg.pod.5 for 'stdvga=1' by default
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> Select a standard VGA card with VBE (VESA BIOS
2013 Sep 18
1
[PATCH] Allow 4 MB of video RAM for Cirrus graphics on traditional QEMU
Signed-off-by: Rob Hoes <rob.hoes@citrix.com> --- docs/man/xl.cfg.pod.5 | 18 +++++++------- tools/libxl/libxl_create.c | 57 ++++++++++++++++++++++++++++++++++---------- 2 files changed, 55 insertions(+), 20 deletions(-) diff --git a/docs/man/xl.cfg.pod.5 b/docs/man/xl.cfg.pod.5 index 769767b..c18604d 100644 --- a/docs/man/xl.cfg.pod.5 +++ b/docs/man/xl.cfg.pod.5 @@ -1009,14
2013 Jan 17
4
[PATCH v4] tools/libxl: Improve videoram setting
2012 Aug 01
2
Bug report about Windows 7 pro 64 bit domU on xen-unstable dom0 with qemu traditional
2010 Jun 06
3
Error: Device 768 (vbd) could not be connected. Path closed or removed during hotplug add: backend/vbd/9/768 state: 1
Hi! Please help me. # xm create win7.hvm Using config file "./win7.hvm". Error: Device 768 (vbd) could not be connected. Path closed or removed during hotplug add: backend/vbd/9/768 state: 1 grep -v ^# /etc/xen/win7.hvm | grep -vx '''' kernel = "/usr/lib/xen/boot/hvmloader" builder=''hvm'' memory = 2048 name = "win7" vif = [
2012 Feb 22
10
xen-unstable: Qemu upstream domUs not start on Wheezy
Dom0 is Wheezy 64 bit with kernel 3.2.0-1-amd64 version 3.2.4-1, xen from xen-unstable.hg changeset 24858:a88ba599add1 plus these patch for not fail build: http://xen.1045712.n5.nabble.com/PATCH-0-of-2-rename-libxl-yajl-gen-alloc-td5469362.html And also this change for lib patch modified with multiarch support: vi config/StdGNU.mk LIBLEAFDIR_x86_64 ?= lib DomUs PV working, domUs with
2011 Aug 28
1
Hanging boot of solaris 11 install image as HVM
Hello, It looks like xen 4.1.2* has some problems with solaris 11 iso images too (s. further below log messages) hvm-solaris11.born2b3.net.cfg # --- kernel = ''/usr/lib64/xen-default/boot/hvmloader'' builder = ''hvm'' device_model= ''/usr/lib64/xen-4.1/bin/qemu-dm'' name = ''solaris11hvm.born2b3.net'' acpi =
2013 Jun 27
20
SPICE with Upstream QEMU and qxl VGA cause Windows BSOD
Hi all, These days I installed xen 4.3 unstable from source and recompiled qemu upstream with spice support. After xl create , the windows domU started successfully and spice client can visit the VDI. However, it display blue screen before entering the windows welcome screen. Is it a bug in current upstream qemu support? My domU configuration file is: builder =
2009 Nov 20
3
Re: xm create: Error: Device 0 (vif) could not be connected. Hotplug scripts not working. One more question.
Next question:- eth0            8000.001c2596e32b       no              peth0 pan0            8000.000000000000       no virbr0          8000.000000000000       yes Presence virbr0 in report seems strange. Direct port  Xen 3.4.2  to F11 doesn''t install daemon libvirtd ( bridge virbr0 ) , unless you wrote xen-3.4.2-(x).fc12.src.rpm  yourself. So , from where bridge virbr0 comes 
2011 Nov 05
88
OpenSuse 11 hvm domU: screen resolution up to 640x480
Hello, I''ve recently installed a hvm domU opensuse 11 guest and I cannot set the screen resolution higher then 640x480. This seems very strange to me, because I don''t have any problem to set higher resolution on a windows 7 domU, using the following parameters in the configuration file: stdvga=1 videoram=16 What could the problem be? Is some video driver missing? -- Flavio
2011 Nov 05
88
OpenSuse 11 hvm domU: screen resolution up to 640x480
Hello, I''ve recently installed a hvm domU opensuse 11 guest and I cannot set the screen resolution higher then 640x480. This seems very strange to me, because I don''t have any problem to set higher resolution on a windows 7 domU, using the following parameters in the configuration file: stdvga=1 videoram=16 What could the problem be? Is some video driver missing? -- Flavio
2014 Jun 10
0
Re: [PATCH v16] libxl: Add qxl vga interface support for upstream qemu
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 >
2013 Jul 05
3
[PATCH] libxl: Add qxl vga interface support for upstream qemu
Usage: vga="qxl" Reposted for xen 4.4, require SSE support on hvm domU otherwise it works only as a standard vga. Signed-off-by: Fabio Fantoni <fabio.fantoni@m2r.biz> Signed-off-by: Zhou Peng <zpengxen@gmail.com> Acked-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com> --- docs/man/xl.cfg.pod.5 |
2011 Jan 11
0
[PATCH, v2]: xl: move domain struct init functions to libxl
Changes since v1: - Include nic,net2,vkb,vfb init functions --- This allows libxl users to get some sane default values for this complex set of structures. This is purely code movement and there are no functional changes except for a trivial error handling change in nic device init. Signed-off-by: Gianni Tedesco <gianni.tedesco@citrix.com> diff -r efe2d3ea22ae tools/libxl/libxl.c ---
2010 May 07
9
[PATCH] xl: Update memory info in xenstore when use ''xl mem-set''
''xl mem-set'' should update memory info in xenstore''s vm info. Signed-off-by: Yu Zhiguo <yuzg@cn.fujitsu.com> diff -r ccae861f52f7 -r 5847ce53f5dc tools/libxl/libxl.c --- a/tools/libxl/libxl.c Thu May 06 11:59:55 2010 +0100 +++ b/tools/libxl/libxl.c Sat May 08 01:38:51 2010 +0800 @@ -2290,11 +2290,22 @@ uint32_t videoram; char *videoram_s = NULL;
2009 Nov 19
3
xm create: Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
Hi All, I am new to xen community. I am trying to setup Xen3.4.2 +FC11 Dom0 environs for lennovo T400. I have installed all prerequisite component for running xen and booted it. while I am trying to create DomU I am getting following error. I tried doing googling but none of suggested solution is working for me. Please guide me through my first experience with xen.for more details please see
2009 Jul 28
0
Windows NT and stdvga
-----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
2008 Sep 03
5
Unable to start Xorg in dom0 (Linux kernel 6.1.18)
Hi, everyone, I installed the Xen3.1.0 based on Fedora8 and enter the Dom0 successfully. The kernel of dom0 is linux-2.6.18-xen0. But the Xorg could not start in the Dom0. When I use the "startx" command to start the X server, the error information is following: ......... (==) Using config file: "etc/X11/xorg.conf" (II) Module already built-in (II) Module already built-in
2008 May 16
0
[PATCH][HVM] stdvga: handle 64bit io operations
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
2010 Jun 22
0
Change stdvga on Windows 7 domU
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