search for: target_kb

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

...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 -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/cento...

...;'/proc/xen/balloon'' f = file(PROC_XEN_BALLOON, ''r'') try: for line in f: @@ -61,6 +63,29 @@ return None finally: f.close() + +def _linux_balloon_stat_sysfs(label): + sysfiles = { ''target'' : ''target_kb'', + ''current'' : ''info/current_kb'', + ''low-balloon'' : ''info/low_kb'', + ''high-balloon'' : ''info/high_kb'', + '...

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

...et" }; @@ -460,8 +459,8 @@ BALLOON_SHOW(low_kb, "%lu\n", PAGES2KB(balloon_stats.balloon_low)); BALLOON_SHOW(high_kb, "%lu\n", PAGES2KB(balloon_stats.balloon_high)); BALLOON_SHOW(driver_kb, "%lu\n", PAGES2KB(balloon_stats.driver_pages)); -static ssize_t show_target_kb(struct sys_device *dev, struct sysdev_attribute *attr, - char *buf) +static ssize_t show_target_kb(struct sys_device *dev, + struct sysdev_attribute *attr, char *buf) { return sprintf(buf, "%lu\n", PAGES2KB(balloon_stats.target_pages)); } @@ -488,8 +487,8 @@ static SYS...

...et" }; @@ -460,8 +459,8 @@ BALLOON_SHOW(low_kb, "%lu\n", PAGES2KB(balloon_stats.balloon_low)); BALLOON_SHOW(high_kb, "%lu\n", PAGES2KB(balloon_stats.balloon_high)); BALLOON_SHOW(driver_kb, "%lu\n", PAGES2KB(balloon_stats.driver_pages)); -static ssize_t show_target_kb(struct sys_device *dev, struct sysdev_attribute *attr, - char *buf) +static ssize_t show_target_kb(struct sys_device *dev, + struct sysdev_attribute *attr, char *buf) { return sprintf(buf, "%lu\n", PAGES2KB(balloon_stats.target_pages)); } @@ -488,8 +487,8 @@ static SYS...

...et" }; @@ -460,8 +459,8 @@ BALLOON_SHOW(low_kb, "%lu\n", PAGES2KB(balloon_stats.balloon_low)); BALLOON_SHOW(high_kb, "%lu\n", PAGES2KB(balloon_stats.balloon_high)); BALLOON_SHOW(driver_kb, "%lu\n", PAGES2KB(balloon_stats.driver_pages)); -static ssize_t show_target_kb(struct sys_device *dev, struct sysdev_attribute *attr, - char *buf) +static ssize_t show_target_kb(struct sys_device *dev, + struct sysdev_attribute *attr, char *buf) { return sprintf(buf, "%lu\n", PAGES2KB(balloon_stats.target_pages)); } @@ -488,8 +487,8 @@ static SYS...

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

...emory 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_hotplug.c maintainers ??? - PV on...