search for: xen_memory

Displaying 6 results from an estimated 6 matches for "xen_memory".

Did you mean: xen_memory0
2013 Aug 01
1
messages logs flooded with xen_balloon: reserve_additional_memory: add_memory() failed
...e if this is related to the same issue or if that issue was ever fixed. When I cat current_kb and target_kb the values don?t match, they are just barely off. I have not tried setting them to match yet. http://marc.info/?t=135601508900004&r=1&w=3 [root at host ~]# cat /sys/devices/system/xen_memory/xen_memory0/info/current_kb 1048532 [root at host ~]# cat /sys/devices/system/xen_memory/xen_memory0/target_kb 1048576 Any ideas? -- Shaun Reitan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20130801/...
2014 Jan 03
3
xen_balloon: reserve_additional_memory: add_memory() Errors
...this example its running 3.10.20-11.el6.centos.alt.x86_64 To replicate this just disable Dom0 memory ballooning in /etc/xen/xend-config.sxp and these errors will over time completely fill up dmesg. This is because the amount of memory within these two sys files is different: /sys/devices/system/xen_memory/xen_memory0/info/current_kb /sys/devices/system/xen_memory/xen_memory0/target_kb We can manually edit to work around the problem and stop the error but its not ideal, I would help with making a patch but don't really know where to start! Thanks Chris -------------- next part -------------- A...
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
...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 @@ "SunOS": "vif-vnic" } -def _linux_balloon_stat(label): +PROC_XEN_BALLOON = ''/proc/xen/balloon'' +SYSFS_XEN_MEMORY = ''/sys/devices/system/xen_memory/xen_memory0'' + +def _linux_balloon_stat_proc(label): """Returns the value for the named label, or None if an error occurs.""" xend2linux_labels = { ''current'' : ''Current allo...
2010 Aug 06
5
[PATCH] GSoC 2010 - Memory hotplug support for Xen guests - second fully working version - once again
...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; /sys/devices/system/xen_memory/xen_memory0/{target,target_kb} are much better (I forgot about them), - most of the code have been moved to drivers/xen/balloon.c, - this changes forced me to export hotadd_new_pgdat and rollback_node_hotadd function from mm/memory_hotplug.c; could it be accepted by mm/memory_hotplu...
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