similar to: Linux Guest in KVM - Best Display Resolution

Adam Jackson (1): Use pci_io_write8 instead of outb Christophe Fergeau (16): Remove unused variables Remove stray blank comment line Use <> for system-includes Fix compilation with newer Xorg versions Add missing licence header Add note about deprecated setting of mm_time Xspice: Fix 'erorr' typo in error message xspice:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 24/02/15 04:15 PM, Robert Nichols wrote: > On 02/23/2015 10:53 PM, Digimer wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> >> On 23/02/15 11:11 PM, Robert Nichols wrote: >>> Would someone please point me to some reasonably current >>> instructions for getting greater than 1024x768 video resolution

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 23/02/15 11:11 PM, Robert Nichols wrote: > Would someone please point me to some reasonably current > instructions for getting greater than 1024x768 video resolution for > a CentOS 6 guest on a CentOS 6 KVM/qemu host? When I search online > I find stuff from 2009 and 2010 saying, "For details see ...," and > linking to a

On 02/23/2015 10:53 PM, Digimer wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 23/02/15 11:11 PM, Robert Nichols wrote: >> Would someone please point me to some reasonably current >> instructions for getting greater than 1024x768 video resolution for >> a CentOS 6 guest on a CentOS 6 KVM/qemu host? When I search online >> I find stuff from 2009

Setting spice display if we know the libvirt guest doesn't have QXL capabilities will only make the guest slower for the user. Fallback to VNC in such a case. A typical use case is when v2v-ing a windows guest without having the windows QXL driver at hand. --- v2v/output_libvirt.ml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/v2v/output_libvirt.ml

Setting spice display if we know the libvirt guest doesn't have QXL capabilities will only make the guest slower for the user. Fallback to VNC in such a case. A typical use case is when v2v-ing a windows guest without having the windows QXL driver at hand. --- v2v/output_libvirt.ml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/v2v/output_libvirt.ml

Hi Everyone, How do I change the console resolution of CentOS 6 KVMs to be 1024x768 or more? I have the spice server and qxl card selected for the KVM. I assumed it would be enough to put the text console into high res, but I was wrong. :/ Regards, Ranbir

Anyone managed to get a Windows 10 guest running well under qemu/kvm? I can get it up and running, but there is a major issue with losing use of the mouse, plus my display resolution is stuck at 1024x768. The mouse will work for a short time (a few seconds to a few minutes), but then stops responding. That's with the mouse coming in as the recommended QEMU tablet device. I can assign a USB

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 >

Would someone please point me to some reasonably current instructions for getting greater than 1024x768 video resolution for a CentOS 6 guest on a CentOS 6 KVM/qemu host? When I search online I find stuff from 2009 and 2010 saying, "For details see ...," and linking to a URL that no longer exists, or pages that say, "You need to switch from VNC to Spice," and giving a long

On Thu, Dec 06, 2018 at 09:39:54AM -0500, Frediano Ziglio wrote: > > > > On Thu, Dec 06, 2018 at 05:55:58AM -0500, Frediano Ziglio wrote: > > > > > > > qxl surfaces (used for framebuffers and gem objects) can live in both > > > > VRAM and PRIV ttm domains. Update placement setup to include both. Put > > > > PRIV first in the list so it

On Thu, Feb 21, 2019 at 8:00 PM Warren Young <warren at etr-usa.com> wrote: > We had a complaint recently from a customer that received a server we > shipped out that their monitor just showed a black screen. It turns out > that they?d hooked it up to an ancient POS with 800x600 as its best > resolution, and gdm in CentOS 7 apparently assumes at least 1024x768. It > was

On Thu, Dec 06, 2018 at 05:55:58AM -0500, Frediano Ziglio wrote: > > > qxl surfaces (used for framebuffers and gem objects) can live in both > > VRAM and PRIV ttm domains. Update placement setup to include both. Put > > PRIV first in the list so it is preferred, so VRAM will have more room > > for objects which must be allocated there. > > > >

From: Peter Wu <peter at lekensteyn.nl> [ Upstream commit 7948a2b15873319d1bff4d37c09b9f2bf87b9021 ] "crtc->helper_private" is not initialized by the QXL driver and thus the "crtc_funcs->disable" call would crash (resulting in suspend failure). Fix this by converting the suspend/resume functions to use the drm_mode_config_helper_* helpers. Tested system sleep

On Tue, Sep 04, 2018 at 10:27:47PM +0200, Peter Wu wrote: > "crtc->helper_private" is not initialized by the QXL driver and thus the This is still initialized, it's the ->disable that goes boom. At least the call to drm_crtc_helper_add is still there. The ->disable was removed in: commit 64581714b58bc3e16ede8dc37a025c3aa0e0eef1 Author: Laurent Pinchart

On 06/29/2015 02:04 PM, Kanwar Ranbir Sandhu wrote: > On Mon, 2015-06-29 at 13:47 -0700, Greg Bailey wrote: >> I've installed it on a KVM guest on a CentOS 7 host. > > I was hoping it wasn't going to come to that. That is, I hope it's not a > CentOS 6 issue. > >> I've always had more success using the drivers obtained from running the >> spice guest

I am trying QXL but similarly windows guest says device is not working. (haven't tried connect to spice yet) On 09/10/14 11:42, lejeczek wrote: > in case I wasn't clear I'll only add that that "Standard > VGA" in guest gets exclaimed ONLY when that second VGA is > passed through. > Otherwise it works and VNC display works too. > > On 08/10/14 15:15,

Dear all, After "yum update" and reboot on a CentOS 7 server running kvm, all VM guests fail to receive keyboard input. Even sending ctrl-alt-delete from the virt-manager "Send Key" menu is inoperative. Most guests are set up as spice + QXL, and viewed on remote X sessions using virt-manager. Extensive browsing for a solution has turned up only dead ends. I tried reverting to

This is just a refactoring and doesn't change the meaning of the code. --- v2v/output_libvirt.ml | 60 +++++++++++++++++++++++++-------------------------- 1 file changed, 29 insertions(+), 31 deletions(-) diff --git a/v2v/output_libvirt.ml b/v2v/output_libvirt.ml index 68af3de..d1cbaa1 100644 --- a/v2v/output_libvirt.ml +++ b/v2v/output_libvirt.ml @@ -222,46 +222,44 @@ let create_libvirt_xml

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 |