similar to: How to add spice build with qemu-xen

- Enable vdagent on upstream qemu if spice is used. Signed-off-by: Fabio Fantoni <fabio.fantoni@m2r.biz> --- tools/libxl/libxl_dm.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/tools/libxl/libxl_dm.c b/tools/libxl/libxl_dm.c index a8a36d7..110f1dc 100644 --- a/tools/libxl/libxl_dm.c +++ b/tools/libxl/libxl_dm.c @@ -427,6 +427,10 @@ static char **

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 >

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 |

I''ve been trying to have all spice features working on xen domUs since the end of 2011. Basic functions were already working. Adding qemu parameters manually for vdagent and usbredirection was and is also working (I made the patches to support them directly on xl). Qxl was never working: one bug on xen and one on qemu about qxl are fixed, the other xen bug found months ago on the

Usage: spicevdagent=1|0 (default=0) Enables spice vdagent. The Spice vdagent is an optional component for enhancing user experience and performing guest-oriented management tasks. Its features includes: client mouse mode (no need to grab mouse by client, no mouse lag), automatic adjustment of screen resolution, copy and paste (text and image) between client and domU. It also requires vdagent

Usage: spiceusbredirection=NUMBER (default=0) Enables spice usbredirection. It requires an usb controller and creates NUMBER usbredirection channels for redirection of up to 4 usb devices from spice client to domU''s qemu. The default is disabled (0). Signed-off-by: Fabio Fantoni <fabio.fantoni@m2r.biz> --- docs/man/xl.cfg.pod.5 | 6 ++++++ tools/libxl/libxl.h |

Usage: spiceusbredirection=NUMBER (default=0) Enables spice usbredirection. Creates NUMBER usbredirection channels for redirection of up to 4 usb devices from spice client to domU''s qemu. It requires an usb controller and if not defined will automatically adds an usb2 controller. Changes from v2: - updated for usbversion patch v7 - now usbredirection cannot be used with usb and

Dom0: Wheezy 64 bit with kernel from package linux-image-3.2.0-2-amd64 version 3.2.12-1, package blktap-dkms and all dependency packages for xen, spice and usb redirection. ------------------------- /etc/modules ------------ loop max_loop=64 xenfs xen-evtchn blktap ------------------------- hg clone http://xenbits.xen.org/xen-unstable.hg (in this build changeset is 25194:6b72eb3b40cf) # Qemu

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

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

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. > > > >

On Thu, Oct 1, 2015 at 12:27 PM, Christoph <mangel at gmx.de> wrote: > Am 2015-10-01 12:33, schrieb Fabio Fantoni: >> >> Should be something like /var/log/xen/qemu-dm-marax.log > > oh ok: > > qemu-system-i386: -spice > port=6000,tls-port=0,addr=0.0.0.0,password=test,agent-mouse=on: There is no > option group 'spice' > spice is not supported by this

Dom0: Wheezy 64 bit with kernel from package linux-image-3.2.0-4-amd64 version 3.2.41-2+deb7u2, package blktap-dkms and all dependency packages for xen, spice and usb redirection. Seabios 1.7.2-3 and latest spice and usbredir compiled from debian unstable sources. ------------------------- /etc/modules ------------ loop max_loop=64 xenfs xen-evtchn blktap ------------------------- git clone

Am 2015-10-01 12:24, schrieb Fabio Fantoni: > > Qemu seems crashed, can you post qemu log of this domU for see the > exact problem? > Also domU's xl cfg can be useful and/or backtrace of qemu crash with > gdb depending on the error of qemu crash. > thats the config of domU: builder = 'hvm' memory = 2048 vcpus=8 boot="c" name = "marax"

Am 2015-10-01 12:33, schrieb Fabio Fantoni: > Should be something like /var/log/xen/qemu-dm-marax.log oh ok: qemu-system-i386: -spice port=6000,tls-port=0,addr=0.0.0.0,password=test,agent-mouse=on: There is no option group 'spice' spice is not supported by this qemu build. qemu-system-i386: -spice port=6000,tls-port=0,addr=0.0.0.0,disable-ticketing,agent-mouse=on: There is no

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 =

On Thu, Dec 06, 2018 at 05:59:25AM -0500, Frediano Ziglio wrote: > > > > Just use qxl_num_crtc directly everywhere instead of using > > qdev->monitors_config->max_allowed. Drops pointless indirection > > and also is less confusing. > > > > To me is MORE confusing, why comparing number of something with > another number? Previously code was comparing

On Thu, Dec 06, 2018 at 07:53:10AM -0500, Frediano Ziglio wrote: > > > > On Thu, Dec 06, 2018 at 05:59:25AM -0500, Frediano Ziglio wrote: > > > > > > > > Just use qxl_num_crtc directly everywhere instead of using > > > > qdev->monitors_config->max_allowed. Drops pointless indirection > > > > and also is less confusing. > >