Displaying 6 results from an estimated 6 matches for "xen_memori".
Did you mean:
xen_memory
2013 Aug 01
1
messages logs flooded with xen_balloon: reserve_additional_memory: add_memory() failed
My /var/log/messages log is being flooded with kernel messages showing the following messages
Aug 1 11:22:52 host43 kernel: System RAM resource 48000000 - 4fffffff cannot be added
Aug 1 11:22:52 host43 kernel: xen_balloon: reserve_additional_memory: add_memory() failed: ?17
Doing a search I found a thread from xen-devel that talks a bit about it. I?m not sure if this is related to the same
2014 Jan 03
3
xen_balloon: reserve_additional_memory: add_memory() Errors
Hi All
Back in August there was a report of these errors popping up in dmesg, and as far as I can tell it's still unresolved even in the latest kernel.
System RAM resource [mem 0xc8000000-0xcfffffff] cannot be added
xen_balloon: reserve_additional_memory: add_memory() failed: -17
On this example its running 3.10.20-11.el6.centos.alt.x86_64
To replicate this just disable Dom0 memory
2012 Dec 19
9
kernel log flooded with: xen_balloon: reserve_additional_memory: add_memory() failed: -17
Hi,
I have encountered an apparently benign error on two systems where the
dom0 kernel log is flooded with messages like:
[52482.163855] System RAM resource [mem 0x1b8000000-0x1bfffffff] cannot
be added
[52482.163860] xen_balloon: reserve_additional_memory: add_memory()
failed: -17
The first line is from drivers/xen/xen-balloon.c, the second from
mm/memory_hotplug.c
The trigger for the
2008 Nov 14
0
[PATCH] tools: use sysfs interface to balloon driver if present
The pvops dom0 kernel does not expose the balloon driver via /proc/xen,
so use the sysfs interface.
Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
diff -r 1944c39d0007 tools/python/xen/xend/osdep.py
--- a/tools/python/xen/xend/osdep.py Fri Nov 14 09:57:33 2008 -0800
+++ b/tools/python/xen/xend/osdep.py Fri Nov 14 12:26:51 2008 -0800
@@ -38,7 +38,10 @@
2010 Aug 06
5
[PATCH] GSoC 2010 - Memory hotplug support for Xen guests - second fully working version - once again
Hi,
I am sending this e-mail once again because it probably
has been lost in abyss of Xen-devel/LKLM list.
Here is the second version of memory hotplug support
for Xen guests patch. This one cleanly applies to
git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
repository, xen/memory-hotplug head.
Changes:
- /sys/devices/system/memory/probe interface has been removed;
2012 Jan 12
9
linux 3.3-pre-rc1: Starting domU fails with Error: Failed to query current memory allocation of dom0.
Hi Konrad,
Today i tried linuses tree of today (last commit is 4c4d285ad5665bfbd983b95fde8d7a477d24a361).
It boots dom0 fine, but it fails to start any domU with: "Error: Failed to query current memory allocation of dom0."
With my previous 3.1.5 kernel everything is fine, nothing else changed in config in between.
dmesg and xm dmesg attached
--
Sander
Dom0 shows:
total