similar to: xl and autoballooning

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

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

Hi guys, I recently turned on IMAP zlib compression for Maildir and noticed that I've started getting these errors in the maillog. Error: Cached message size larger than expected (1627 > 1548) Error: Maildir filename has wrong S value, renamed the file from /home/crc.id.au/netwiz/.System Generated.Cron Jobs/cur/1392224150.M52270P1073.mail.crc.id.au,S=1627:2,S,Z to /home/crc.

Hi all, I''m trying to update my RPMs of 4.1.3 to work with 4.2.0, but I''m having some interesting problems with the packaging side of things. in 4.1.3, xenpaging was being built as /usr/sbin/xenpaging, however in 4.2.0 it is being built as /usr/lib/xen/bin/xenpaging. I''m currently using the following configure options in my .spec: ./configure --libdir=/%{_libdir}

Dear James, Thank you for being quick to help. Yes, I could see all of them: # vgs # lvs # pvs Regards, Khem On Sat, February 28, 2015 7:37 am, James A. Peltier wrote: > > > ----- Original Message ----- > | Dear All, > | > | I am in desperate need for LVM data rescue for my server. > | I have an VG call vg_hosting consisting of 4 PVs each contained in a > | separate

----- Original Message ----- | Dear All, | | I am in desperate need for LVM data rescue for my server. | I have an VG call vg_hosting consisting of 4 PVs each contained in a | separate hard drive (/dev/sda1, /dev/sdb1, /dev/sdc1, and /dev/sdd1). | And this LV: lv_home was created to use all the space of the 4 PVs. | | Right now, the third hard drive is damaged; and therefore the third PV |

Hi all, I've just migrated my mail system from procmail to managesieve/sieve and I'm having trouble trying to duplicate a could of rules I used to use in my procmail config. One particular rule would be this: :0 Wfh * ^Sender: owner-scientific-linux-devel at LISTSERV.FNAL.GOV | (sed -e '/^Subject:/ s/\[SCIENTIFIC-LINUX-DEVEL\] *//g'| sed ':a;N;$!ba;s/Precedence:

Dear All, I am in desperate need for LVM data rescue for my server. I have an VG call vg_hosting consisting of 4 PVs each contained in a separate hard drive (/dev/sda1, /dev/sdb1, /dev/sdc1, and /dev/sdd1). And this LV: lv_home was created to use all the space of the 4 PVs. Right now, the third hard drive is damaged; and therefore the third PV (/dev/sdc1) cannot be accessed anymore. I would like

Package: xen-utils-common Version: 4.1.4-3+deb7u1 Severity: normal Dear Maintainer, i changed toolkit to xl, after that i observe that my domU started as HVM domains. I found same problem here: http://mail-index.netbsd.org/port-xen/2012/04/11/msg007216.html When i manualy setup loop devices and specify it as disks in my VM conf file, domU started as PV. -- System Information: Debian Release: 7.1

libxenlight exports a function libxl_uuid2string which is used internally in several places but has one external caller in xl. The function mainly implements policy so should not be part of the libxenlight API. The extent to which it can be considered mechanism it is not a xen mechanism since UUID''s are not a concept exlusive to xen. The one caller in xl seems to be an

The current libxl_set_memory_target function subtracts a negative amount from an uint32_t variable without checking if the operation wraps around. This patch fixes this bug (that I previously believed to be an hypervisor issue): http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1729 Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> diff -r a69965e61ae9

''xl mem-set'' should update memory info in xenstore''s vm info. Signed-off-by: Yu Zhiguo <yuzg@cn.fujitsu.com> diff -r ccae861f52f7 -r 5847ce53f5dc tools/libxl/libxl.c --- a/tools/libxl/libxl.c Thu May 06 11:59:55 2010 +0100 +++ b/tools/libxl/libxl.c Sat May 08 01:38:51 2010 +0800 @@ -2290,11 +2290,22 @@ uint32_t videoram; char *videoram_s = NULL;

Hi all, I''ve had a report of a host starting to give this output: Oct 7 19:36:37 kernel: INFO: rcu_sched self-detected stall on CPU { 2} (t=273561 jiffies g=17919 c=17918 q=9688) Oct 7 19:36:37 kernel: sending NMI to all CPUs: Oct 7 19:36:37 kernel: xen: vector 0x2 is not implemented Kernel is 3.11.2. Xen is 4.2.3. I''ve seen various random reports of this, but never a follow

Hi, during some experiments with many guests I get crashing Dom0s because of too less memory. Actually the OOM killer goes ''round and kills random things, preferably qemu-dm''s ;-) The box in question has 128GB of memory, I start with dom0_mem=8192M (or 16384M, doesn''t matter). I also used "dom0_mem=8192M,min:1536M", but that didn''t make any

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:

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

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

Hi all, I'm seeing a random issue with my procmail filters (only on email from this list) where once every so often, it will fail to filter a message. I am sorting by the to/cc email address, and this rule works on 99.9% of posts, however every now and again, I see something like this happen: From centos-bounces at centos.org Sat Jan 5 01:57:28 2008 Subject: Re: [CentOS]

On Thu, 2013-04-11 at 05:09 +0100, Jim Fehlig wrote: > > + /* This will fill xenstore info about free and dom0 memory - if missing, > > + * should be called before starting first domain */ > > + if (libxl_get_free_memory(libxl_driver->ctx, &free_mem)) { > > + VIR_ERROR(_("cannot get free memory info")); > > + goto error; >