similar to: [PATCH] xl: extend autoballoon xl.conf option with an "auto" option

Displaying 20 results from an estimated 1000 matches similar to: "[PATCH] xl: extend autoballoon xl.conf option with an "auto" option"

2012 Nov 27
3
[PATCH] xl: xl.conf(5): correct advice re autoballooning vs. dom0_mem
# 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.
2013 Jul 06
0
xl and autoballooning
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 =
2010 Aug 27
0
[PATCH 0 of 8] xl/libxl autoballooning
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.
2012 Aug 24
4
Network with xen 4.2
Hallo Mailinglist:), i used xen 4.1 with xend xm a while. I compiled the unstable 4.2 today and most thinks run fine :). I have only one big problem, the network for my guestsystems. It don't want to work. Hopefully somebody can help me. In Xen 4.1 i only wrote the following line in my questconfig: vif = [ "bridge=eth0,script=vif-bridge" ] And everything works fine. This does not
2012 Aug 14
4
[PATCH] libxl: fix usage of backend parameter and run_hotplug_scripts
vif interfaces allows the user to specify the domain that should run the backend (also known as driver domain) using the ''backend'' parameter. This is not compatible with run_hotplug_scripts=1, since libxl can only run the hotplug scripts from the Domain 0. Signed-off-by: Roger Pau Monne <roger.pau@citrix.com> --- docs/misc/xl-network-configuration.markdown | 6 ++++--
2012 Aug 02
2
auto-ballooning crashing Dom0?
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
2013 Jun 18
3
Bug#712661: xen-utils-common: xl start HVM domU instead of PV if disk placed on file
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
2013 Apr 04
28
[PATCH v3 0/3] libxl: memory management patches
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
2012 Nov 23
1
[PATCH] libxl - fix a variable underflow in libxl_wait_for_free_memory
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:
2012 Sep 21
6
xl create bug on first-attempt with passthrough
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
2008 May 06
7
Disable memory balloon in dom0
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
2006 Jun 02
3
Where are the best AJAX examples?
Googling for this has not solved my problems. Is there a particular site that is recommened for its examples and tutorials on Rails'' AJAX capabilities? I know exactly what I want to do, just not how to do it, and am looking for some code to pore over. 1) I have a dropdown that represents the name of an image in a library. When the dropdown value is changed, I would like to refresh
2013 Jun 19
14
[PATCH 2/4] time: add a notifier chain for when the system time is stepped
From: David Vrabel <david.vrabel@citrix.com> The high resolution timer code gets notified of step changes to the system time with clock_was_set() or clock_was_set_delayed() calls. If other parts of the kernel require similar notification there is no clear place to hook into. Add a clock_was_set atomic notifier chain (clock_was_set_notifier_list) and call this in place of clock_was_set().
2013 Nov 20
6
[PATCH] xen/gnttab: leave lazy MMU mode in the case of a m2p override failure
From: Matt Wilson <msw@amazon.com> Commit f62805f1 introduced a bug where lazy MMU mode isn''t exited if a m2p_add/remove_override call fails. Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com> Cc: David Vrabel <david.vrabel@citrix.com> Cc: Anthony
2013 Sep 19
3
[PATCH] xen/balloon: don't alloc page while non-preemptible
From: David Vrabel <david.vrabel@citrix.com> get_balloon_scratch_page() disables preemption so we cannot call alloc_page() in between get/put_balloon_scratch_page(). Shuffle bits around in decrease_reservation() to avoid this. Signed-off-by: David Vrabel <david.vrabel@citrix.com> --- drivers/xen/balloon.c | 23 +++++++++++------------ 1 files changed, 11 insertions(+), 12
2005 Jul 03
3
Use of ogg vorbis for real time audio streaming?
Hi list! I am currently investigating the possibility of allowing musicians to collaborate over the internet -- Musician A -------> internet --------> Musician B This diagram obscures quite a lot of detail. In reality, the datapath would look more like this: Musician A ADC Compression algorithm UTP (or perhaps RTP?) IP ADSL the Internet ....<snip>..... Clearly, this link would
2013 Jun 27
1
[PATCH 2/5] time: pass flags instead of multiple bools to timekeeping_update()
From: David Vrabel <david.vrabel@citrix.com> Instead of passing multiple bools to timekeeping_updated(), define flags and use a single ''action'' parameter. It is then more obvious what each timekeeping_update() call does. Signed-off-by: David Vrabel <david.vrabel@citrix.com> --- kernel/time/timekeeping.c | 21 ++++++++++++--------- 1 files changed, 12
2012 Mar 19
24
[PATCHv2 00/11] arm: pass a device tree to dom0
This series of patches makes Xen pass a (somewhat) valid device tree to dom0. The device tree for dom0 is the same as the one supplied to Xen except the memory and chosen nodes are adjusted appropriately. We don''t yet make use of the device tree to map MMIO regions or setup interrupts for the guest and we still include the UART used for Xen''s console. Note that loading Linux
2010 Oct 13
3
Why deliver+usercheck? deliver+MTA?
Hi, I successfully configured dovecot using virtual users (and LDAP/AD). deliver is the LDA and verifies if the user exists (as recommended in the WIKI). However, the howtos in the Wiki say *nothing* about the case that the recipients should be verified *before* receiving the messages (prevent backscatter, ...). All configurations in the dovecot-Wiki (postfix and exim) just accept the mails
2013 Nov 18
9
[PATCH RESEND v2 2/2] xen: enable vnuma for PV guest
Enables numa if vnuma topology hypercall is supported and it is domU. Signed-off-by: Elena Ufimtseva <ufimtseva@gmail.com> --- arch/x86/xen/setup.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/arch/x86/xen/setup.c b/arch/x86/xen/setup.c index 68c054f..0aab799 100644 --- a/arch/x86/xen/setup.c +++ b/arch/x86/xen/setup.c @@ -20,6 +20,7 @@ #include