similar to: [PATCH] libxl: fix rtc_timeoffset setting

Implement "rtc_timeoffset" and "localtime" options compatible as xm. rtc_timeoffset is the offset between host time and guest time. localtime means to specify whether the emulted RTC appears as UTC or is offset by the host. Acked-by: Ian Campbell <ian.campbell@citrix.com> Signed-off-by: Lin Ming <mlin@ss.pku.edu.cn> --- docs/man/xl.cfg.pod.5 | 8 ++++++++

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

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

Add qxl vga interface support. Usage: qxl=1 qxlvram=64 qxlram=64 Signed-off-by: Zhou Peng <ailvpeng25@gmail.com> diff -r c6641e3fe158 tools/libxl/libxl_dm.c --- a/tools/libxl/libxl_dm.c Mon May 28 16:25:59 2012 +0800 +++ b/tools/libxl/libxl_dm.c Wed May 30 17:48:38 2012 +0800 @@ -181,6 +181,8 @@ static char ** libxl__build_device_model flexarray_append(dm_args,

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

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1320922479 0 # Node ID bc79b560aafa1e4dc42af00e6a326dc651b5636a # Parent 460b507e15f864dd6712f5040e36538d6e076ae4 libxl: use named options for tsc_mode. It seems that this knob is expoerted from the hypervisor as a raw integer (no symbolic names) documented in xen/include/asm-x86. Propagating that all the way to the

Usage: usbversion=1|2|3 (default=0, no usb controller defined) Specifies the type of an emulated USB bus in the guest. 1 for usb1, 2 for usb2 and 3 for usb3, it is available only with upstream qemu. The old usb and usbdevice parameters cannot be used with this. Changes from v6: - now usbversion cannot be used with usb and usbdevice parameters - now default is 0 (no usb controller defined) Will be

Hello techs, We used XL toolkit for Xen hypervisor for starting Windows hvm VMs and the option rtc_timeoffset worked perfectly with XL. It helped us to set correct Timezone time/offset for Windows HVM VMs from inside virtual_machine xen config. For example: Below option WORKS perfectly with XL toolkit. [root@hw12xen ~]# cat goillltawdlssq.xl.cfg | grep offset rtc_timeoffset = "7200"

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1337273492 -3600 # Node ID cdb947baea102aa6a1d53472f8a3e5f2d6cc485e # Parent ac45608496cd85b0bf1aed6e5b869b4a86ca672f libxl: do not overwrite user supplied config when running bootloader. Currently when running the bootloader libxl will update b_info->u.pv.kernel, .ramdisk, .cmdline and .bootloader. This can

The xen_platform_pci xl configuration parameter currently has no effect on upstream QEMU; creation of the platform device is hardcoded. I have created a patch to QEMU to remove this hardcoded creation. This patch specifies the appropriate -device argument on the QEMU command line (and hence creates the device) only when xen_platform_pci is true. Signed-off-by: Paul Durrant

On 02/16/2018 08:37 AM, Volo M. wrote: > Hello techs, > > We used XL toolkit for Xen hypervisor for starting Windows hvm VMs and the > option rtc_timeoffset worked perfectly with XL. It helped us to set correct > Timezone time/offset for Windows HVM VMs from inside virtual_machine xen config. > > For example: > Below option WORKS perfectly with XL toolkit. >

Jim, Thanks a lot for your confirmation. Could you also please explain if the issue can be ever fixed, if it's possible to make some patch to fix it? Is it libvirt-specific bug or Libvirt development team rely on some other developers of libxl code...etc? I'm asking because XL tools works fine and I wonder if XL uses the same libxl libraries , doesn't it? Lastly is the issue is going

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 >

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

I just built 4.3.0 in order to get > 2GB of RAM in domU with GPU passthrough without crashes. Unfortunately, the same crashes still happen. Massive frame buffer corruption on domU before it locks up solid. It seems the PCI memory stomp is still happening. I am using qemu-dm, as I did on Xen 4.2.x. So whatever fix for this went into 4.3.0 didn''t fix it for me. Passing less than 2GB

# HG changeset patch # User Ian Campbell <ijc@hellion.org.uk> # Date 1353432141 0 # Node ID 72376896ba08bb7035ad4b7ed5a91c2c1b45b905 # Parent 41f0137955f4a1a5a76ad34a5a6440e32d0090ef libxl: ocaml: add bindings for libxl_domain_create_new ** NOT TO BE APPLIED ** Add a simple stub thing which should build a domain. Except it is incomplete and doesn''t actually build. Hence RFC.

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 |

Changes since v1: - Removed libxl vncviewer related dependencies - The vncviewer function was modified to accept a domid instead of domspec; - main_vncviewer was updated to reflect the new use. - A domain_create structure is now passed to the parse_config_data where required/feasible (NULL otherwise) - xl restore now have long options for vncviewer/vncviewer-autopass; docs updated. - Updated

Hi, I''ve installed xen-unstable 4.2 from actual git (last commit was 4dc7dbef5400f0608321d579aebb57f933e8f707). When I start a domU with xm all is fine include the cpu_weight I configured in my domU config. When I start the domU with xl then all my domU have the default cpu_weight of 256 instead of the configured one. Was the name of cpu_weight being changed for xl command ? My domU

Hi, I''ve installed xen-unstable 4.2 from actual git (last commit was 4dc7dbef5400f0608321d579aebb57f933e8f707). When I start a domU with xm all is fine include the cpu_weight I configured in my domU config. When I start the domU with xl then all my domU have the default cpu_weight of 256 instead of the configured one. Was the name of cpu_weight being changed for xl command ? My domU