similar to: [PATCH 0 of 8] xl/libxl autoballooning

From: David Vrabel <david.vrabel@citrix.com> autoballoon=1 is not recommened if dom0_mem was used to reduce the amount of dom0 memory. Instead of requiring users to change xl.conf if they do this, extend the autoballoon option with a new choice: "auto". With autoballoon="auto", autoballooning will be disabled if dom0_mem was used on the Xen command line. For

# HG changeset patch # User Ian Campbell <ijc@hellion.org.uk> # Date 1354011148 0 # Node ID 3174dc24e3efb0c5b964c244dbfb0218a03a38cf # Parent 541b0e1a36c86db5df04988dd4ade5430776a7f2 xl: xl.conf(5): correct advice re autoballooning vs. dom0_mem. The advice was backwards, you should really disable autoballoon if you use dom0_mem. Also add a reference to the command-line docs.

Hi Ian (and all), I recently came across a bug in xl autoballooning in Xen 4.2.2 that I found mentioned way back in May 2012. In a nutshell, I tried to create a new DomU with 1024M of memory. The Dom0 had 3100M free: # xl info | grep memory total_memory : 20479 free_memory : 3100 The guest template is very simple: # cat /etc/xen/template.vm name =

When xl is called to create a domU and there is not enough memory available, then the autoballooning is called to extract memory from dom0. During the ballooning a loop in libxl_wait_for_free_memory() waits unless enough memory is available to create the domU. But because of a variable-underflow the loop can finish too soon and xl finally aborts with the message: xc: error: panic:

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 |

Fix a xl/libxl segfault when assigning a device to the guest (bug http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1713). Signed-off-by: Gianni Tedesco <gianni.tedesco@citrix.com> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> diff -r b05892ff0fce tools/libxl/libxl_pci.c --- a/tools/libxl/libxl_pci.c Tue Jan 25 15:14:52 2011 +0000 +++

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 >

Prevent xl from doing any operation if xend daemon is running. That prevents bugs that happened when xl and xend raced to close a domain. Changes since v1: * Add documentation to xl man page. * Permit the execution of commands that don''t modify anything. * Indent error message. Cc: george.dunlap@eu.citrix.com Cc: ian.jackson@eu.citrix.com Signed-off-by: Roger Pau Monne

xl: parse the maxvcpus config file parameter Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> diff -r 6d605ec6bcd8 tools/libxl/xl_cmdimpl.c --- a/tools/libxl/xl_cmdimpl.c Thu Sep 02 12:38:13 2010 +0100 +++ b/tools/libxl/xl_cmdimpl.c Thu Sep 02 14:15:08 2010 +0100 @@ -687,6 +687,9 @@ static void parse_config_data(const char b_info->cur_vcpus = (1 << l)

flight 5665 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/5665/ Regressions :-( Tests which did not succeed and are blocking: build-amd64-oldkern 4 xen-build fail REGR. vs. 5640 build-amd64 4 xen-build fail REGR. vs. 5640 build-i386-oldkern 4 xen-build fail REGR. vs. 5640

Add "xl domid" command, a clone of "xm domid". Signed-off-by: Yang Hongyang <yanghy@cn.fujitsu.com> diff -r ccae861f52f7 -r 1d00cee69621 tools/libxl/xl_cmdimpl.c --- a/tools/libxl/xl_cmdimpl.c Thu May 06 11:59:55 2010 +0100 +++ b/tools/libxl/xl_cmdimpl.c Fri May 07 19:35:40 2010 +0800 @@ -1221,6 +1221,9 @@ printf(" -d DOMAIN, --domain=DOMAIN Domain to

This adds a backend_domname field in libxl devices that contain a backend_domid field, allowing either a domid or a domain name to be specified in the configuration structures. The domain name is resolved into a domain ID in the _setdefault function when adding the device. This change allows the backend of the block devices to be specified (which previously required passing the libxl_ctx down

xend uses rtl8139, and we want xl to be compatible with xm. Some older operating systems don''t have e1000 drivers, and we want widest compatibility rather than best performance (people who want good performance are best advised to use PV-on-HVM drivers). We''ll probably switch to a new default when switching to upstream qemu, in the Xen 4.2 release cycle. Signed-off-by: Ian

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1346428441 -3600 # Node ID ddde6c2c45de8e60518aafa077f0f3867ff68e17 # Parent ccbee5bcb31b72706497725381f4e6836b9df657 libxl/xl: implement support for guest iooprt and irq permissions. This is useful for passing legacy ISA devices (e.g. com ports, parallel ports) to guests. Supported syntax is as described in

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

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

Hello, As discussed on the last Virt SIG meeting I promised to do some libvirt + libxl testing using the latest Xen 4.4 rpms. Versions used: xen-libs-4.4.1-5.el6.x86_64 xen-licenses-4.4.1-5.el6.x86_64 xen-hypervisor-4.4.1-5.el6.x86_64 xen-4.4.1-5.el6.x86_64 xen-runtime-4.4.1-5.el6.x86_64 kernel-3.10.63-11.el6.centos.alt.x86_64 libvirt-daemon-driver-nwfilter-1.2.10-3.el6.x86_64

Hi As we will use xl in xen 4.1. I had try use xl to do something. And I find some command is fails. For config file, when give "disk=" too args, it will show segment fault if we use xl create to start guest. Is there any change for xl''s config file? Following command can not work: xl migrate: when I use xl migrate domain localhost to do migrate, it shows error:

Hello, I recently swapped some components, and rebuilt my system. Changes to the configuration: - Wheezy Beta 1 > Wheezy Beta 2 - Kernel 3.4.9 > Kernel 3.4.11 I have tested the new Xen 4.2 stable, and Xen unstable revision 25777, both are giving me the same error so I do not believe it is related to a change in Xen. The first attempt to pass a PCI device after booting the system

On 01/17/2015 08:46 AM, Pasi K?rkk?inen wrote: > On Fri, Jan 16, 2015 at 09:16:05PM +0200, Pasi K?rkk?inen wrote: >> Hello, >> >> As discussed on the last Virt SIG meeting I promised to do some libvirt + libxl testing using the latest Xen 4.4 rpms. >> >> Versions used: >> >> xen-libs-4.4.1-5.el6.x86_64 >> xen-licenses-4.4.1-5.el6.x86_64 >>