search for: autoballoon

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

# 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. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> diff -r 541b0e1a36c8 -r 3174dc24e3ef docs/man/xl.conf.pod.5 --- a/docs/man/xl.conf.pod....

Hi all, this patch series adds some new memory management functions to libxl that are used by xl to autoballoon dom0 down by the amount of memory needed by the new domain build. In order to avoid conflicts with other xl instances during the memory accounting operation I am introducing a global filelock. I am also introducing a global configuration file for xl to enable/disable autoballooning. Cheers, Stefan...

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

...ng failed before), but it has obviously ripped off precious memory from Dom0. With around 55 guests Dom0 has about 500MB in use. The whole Dom0 is in trouble then, I get "fork: cannot allocate memory" messages for a simple "ls" and have to reboot the box. This is with xl.conf:autoballooning=1 (= the commented default) Setting it to 0 works, but is obviously not a real option as a default. I found the hardcoded 128MB limit in libxl_internal.h, I guess this is way too small for this type of machine. Either we change this to something higher (768 MB worked for me) or we make this...

Hi, I''ve tried to search the list archives but I didn''t found anything about this and I''m experiencing some problems I need to solve quickly so here follows my question and related doubts. * The configuration I''ve an 8GB equipped with 2 dual core xeon cpus server running CentOS 5.1 (x64) and xen 3.0.3-41.el5 on kernel 2.6.18-53 I''m running 4 DomU

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

Is there any reason why I would not want to set dom0-min-mem to 0 or to what I set dom0_mem on my kernel line? Setting to 0 or setting to the same value as dom0_mem disables memory balloon correct? I cant seem to think of a reason why I would want memory ballooning. Also setting dom0-min-mem should that be done in xend-config.sxp or on the kernel command line? -- Nick Anderson

...ors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlänge:0 RX bytes:37747530 (35.9 MiB) TX bytes:37747530 (35.9 MiB) xl.config: ## Global XL config file ## # automatically balloon down dom0 when xen doesn't have enough free # memory to create a domain #autoballoon=1 # full path of the lockfile used by xl during domain creation lockfile="/var/lock/xl" # default vif script vifscript="vif-bridge" # default output format used by "xl list -l" #output_format="json" # first block device to be used for temporary VM disk m...

Hi! i notice a serious regression with 3.5 as Dom0 kernel (3.4 was rock stable): 1st: only the GPU PCI Passthrough works, the PCI USB Controller is not recognized within the DomU (HVM Win7 64) Dom0 cmdline is: ro root=LABEL=dom0root xen-pciback.hide=(08:00.0)(08:00.1)(00:1d.0)(00:1d.1)(00:1d.2)(00:1d.7) security=apparmor noirqdebug nouveau.msi=1 Only 8:00.0 and 8:00.1 get passed through

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

...memory for that domain, rather than calling it once at start of day. In that context if it fails or returns less than the required amount of memory then that would be fatal for starting that domain. In xl we use this as part of the auto balloon of dom0, see xl_cmdimplg.c:freemem. Does libvirt do autoballooning or does it require dom0_mem? Perhaps this is handled at a higher level? Ian. > > Regards, > Jim > > > + > > if (!(libxl_driver->xmlconf = virDomainXMLConfNew(&libxlDomainXMLPrivateDataCallbacks, > >...

...['bridge=br0'] > disk = ['file:/home/zer0/xen/xenwin8.1.img,hda,w'] > acpi = 1 > apic = 1 > hpet=1 > device_model_version = 'qemu-xen' > boot="c" > opengl=1 > sdl=1 > vnc=0 > autoballoon=0 > > > Here the latest kernel with which I encounter the problem : > > zer0 at debian:~$ uname -a > Linux debian 4.0.0-1-amd64 #1 SMP Debian 4.0.2-1 (2015-05-11) x86_64 > GNU/Linux > > Or with > > zer0 at debian:~$ uname -a > Linux debian 3.16.0-4-amd64 #...

...me = "Windows8.1" vif = ['bridge=br0'] disk = ['file:/home/zer0/xen/xenwin8.1.img,hda,w'] acpi = 1 apic = 1 hpet=1 device_model_version = 'qemu-xen' boot="c" opengl=1 sdl=1 vnc=0 autoballoon=0 Here the latest kernel with which I encounter the problem : zer0 at debian:~$ uname -a Linux debian 4.0.0-1-amd64 #1 SMP Debian 4.0.2-1 (2015-05-11) x86_64 GNU/Linux Or with zer0 at debian:~$ uname -a Linux debian 3.16.0-4-amd64 #1 SMP Debian 4.0.2-1 (2015-05-11) x86_64 GNU/Linux Thanks -...

...AINS_RESTORE=false XENDOMAINS_AUTO=/etc/xen/auto XENDOMAINS_STOP_MAXWAIT=300 /etc/xen/xend-config.sxp changed: (#xend-unix-server yes) (vif-script vif-bridge) (dom0-min-mem 196) (enable-dom0-ballooning yes) (total_available_memory 0) (dom0-cpus 0) (vncpasswd '') /etc/xen/xl.conf changed: autoballoon=1 lockfile="/var/lock/xl" vifscript="vif-bridge" -- no debconf information

Hi, Here are three small but important libxl/xl memory management patches: - libxl: xl mem-max et consortes must update static-max in xenstore too, - xl: Allow user to configure xl mem-set behavior, - xl: Improve xl documentation in regards to guest memory management. Daniel

...echo "Usage: $0 {start|stop|restart|reload|force-reload}" exit 3 ;; esac exit 0 /etc/xen/xend-config.sxp changed: (vif-script vif-bridge) (dom0-min-mem 2048) (enable-dom0-ballooning no) (total_available_memory 0) (dom0-cpus 0) (vncpasswd '') /etc/xen/xl.conf changed: autoballoon=0 -- no debconf information

...--- a/tools/libxl/xl.c +++ b/tools/libxl/xl.c @@ -32,8 +32,11 @@ #include "libxlutil.h" #include "xl.h" +#define XEND_LOCK { "/var/lock/subsys/xend", "/var/lock/xend" } + xentoollog_logger_stdiostream *logger; int dryrun_only; +int force_execution; int autoballoon = 1; char *lockfile; char *default_vifscript = NULL; @@ -103,8 +106,9 @@ int main(int argc, char **argv) char *config_file; void *config_data = 0; int config_len = 0; + const char *locks[] = XEND_LOCK; - while ((opt = getopt(argc, argv, "+vN")) >= 0) { + whi...

...39;file:/home/zer0/xen/xenwin8.1.img,hda,w'] >> acpi = 1 >> apic = 1 >> hpet=1 >> device_model_version = 'qemu-xen' >> boot="c" >> opengl=1 >> sdl=1 >> vnc=0 >> autoballoon=0 >> >> >> Here the latest kernel with which I encounter the problem : >> >> zer0 at debian:~$ uname -a >> Linux debian 4.0.0-1-amd64 #1 SMP Debian 4.0.2-1 (2015-05-11) x86_64 >> GNU/Linux >> >> Or with >> >> zer0 at debian:~$ uname...

The contents are the wip.testme branch currently on salsa. I combined the wip.initscript and wip.oxenstored into this and added more things today. I think this is pretty gtg and it's smoke tested (in several cases by scping files around instead of doing package build), so it needs a final extra review and test round before putting it in master branch (which I don't want to force push). I