search for: meminfo

meminfo.c32: Remove unneeded 'x' characters from output. Commit 5932f124 ("com32: change '%llx' to use PRIx64", committed on 2015-01-06) adds 1 "x" character per each of the 3 hex output columns for the 'INT 15h e820' value(s) in meminfo.c32. These 3 extra &quo...

...on why the lack of ABI headers screw us up. */ #ifndef TMPFS_MAGIC # define TMPFS_MAGIC 0x01021994 #endif #ifndef RAMFS_MAGIC # define RAMFS_MAGIC 0x858458f6 #endif #ifndef MS_MOVE # define MS_MOVE 8192 #endif #define NEWROOT "/newroot" #define CMDLINE "/proc/cmdline" #define MEMINFO "/proc/meminfo" static const char *program; // argv[0] static char newroot[512]; // where newroot will be static char **initargs; // argv static struct stat root_st; // stat of / static char meminfo[1024]; // contents of /proc/meminfo, after getprocinfo static char cmdline[2048]; // con...

On 03/23/2016 09:19 AM, Cole Robinson wrote: > On 03/23/2016 12:10 PM, Peter Steele wrote: >> Has anyone seen this issue? We're running containers under CentOS 7.2 and some >> of these containers are reporting incorrect memory allocation in >> /proc/meminfo. The output below comes from a system with 32G of memory and >> 84GB of swap. The values reported are completely wrong. >> > There was a meminfo bug here: > > https://bugzilla.redhat.com/show_bug.cgi?id=1300781 > > The initial report is fixed in git, however the reporter...

I have to collect cpuinfo and meminfo from hundreds of machines in preparation of updating our inventory and Xen version. Since we pin cpu and ram for dom0, this mangles the info. Is there way to get the real information? I know that xm top will give me the true RAM, but I need a non-interactive method. Specifically, I need the follow...

On 03/23/2016 12:10 PM, Peter Steele wrote: > Has anyone seen this issue? We're running containers under CentOS 7.2 and some > of these containers are reporting incorrect memory allocation in > /proc/meminfo. The output below comes from a system with 32G of memory and > 84GB of swap. The values reported are completely wrong. > There was a meminfo bug here: https://bugzilla.redhat.com/show_bug.cgi?id=1300781 The initial report is fixed in git, however the reporter also mentioned the issue you...

Has anyone seen this issue? We're running containers under CentOS 7.2 and some of these containers are reporting incorrect memory allocation in /proc/meminfo. The output below comes from a system with 32G of memory and 84GB of swap. The values reported are completely wrong. # cat /proc/meminfo MemTotal: 9007199254740991 kB MemFree: 9007199224543267 kB MemAvailable: 12985680 kB Buffers: 0 kB Cached: 119744 kB Swap...

...te: > On 03/23/2016 09:19 AM, Cole Robinson wrote: >> On 03/23/2016 12:10 PM, Peter Steele wrote: >>> Has anyone seen this issue? We're running containers under CentOS 7.2 and some >>> of these containers are reporting incorrect memory allocation in >>> /proc/meminfo. The output below comes from a system with 32G of memory and >>> 84GB of swap. The values reported are completely wrong. >>> >> There was a meminfo bug here: >> >> https://bugzilla.redhat.com/show_bug.cgi?id=1300781 >> >> The initial report is fixed i...

...in lxc container just >> showing the same thing as the lxc host? If I want to monitor the >> realtime resource usage inside the lxc container, What should I do? >At this time, the only files in /proc that are virtualized are >the /proc/$PID/* files for each process, and the /proc/meminfo >global file. All the other files reflect global host state. >Are there particular files in /proc/NNNN that you want to see >virtualized in the future ? Well, I used to monitor a kvm vm by a script reading info from files such as /proc/stat, /proc/loadavg, /proc/meminfo, /proc/diskstats,...

Dear All As far as I know , to check for the amount of installed RAM on my centos server I checked it as: #more /proc/meminfo Can you please let me know how can I check for the instantaneous occupied amount of my RAM the similar way the task manager shows it on my Win server ? Thank you in advance

...host. > Following is an example in a VM with 1G memory 1CPU. This test setups an > environment that has a lot of fragmentation pages. Then inflate balloon will > split the THPs. > // This is the THP number before VM execution in the host. > // None use THP. > cat /proc/meminfo | grep AnonHugePages: > AnonHugePages: 0 kB > // After VM start, use usemem > // (https://git.kernel.org/pub/scm/linux/kernel/git/wfg/vm-scalability.git) > // punch-holes function generates 400m fragmentation pages in the guest > // kernel. > usemem --punch-holes -s -1 800...

...0:00 /usr/libexec/libvirt_lxc --name tst-mxs2.test --console 21 --security=none --handshake 24 --veth macvlan5 [root@node01]# virsh list Id Name State ---------------------------------------------------- 7445 tst-mxs2.test running 5) Now broke /proc/meminfo inside container. prepare simple systemd service: # cat /usr/lib/systemd/system/true.service [Unit] Description=simple test [Service] Type=simple ExecStart=/bin/true [Install] WantedBy=multi-user.target Enable service first time, disable and start: [root@node01]# systemctl enable /usr/lib/s...

Hi all > Has anyone seen this issue? We're running containers under CentOS 7.2 > and some of these containers are reporting incorrect memory allocation > in /proc/meminfo. The output below comes from a system with 32G of > memory and 84GB of swap. The values reported are completely wrong. yes, it's occured time to time on our installations. Centos 7.2 + libvirt 1.2.18 and probably on 1.3.2 We have workaround for fix it without reboot LXC container. 1) check t...

>> The latest version available for CentOS/RHEL is version 1.2.17. What >> site are you using to get the rpm for version 1.3.2? build from source rpm's > I found a download for this version and tried it out but we ran into a > different set of problems when running our software in containers under > this environment. Unfortunately we're out of time to address these

...nd with VIRTIO_BALLOON_F_DEFLATE_ON_OOM configuration flag set). The bad thing is that end-user does not know this. Balloon by default reduce the amount of memory exposed to the end-user each time when the page is stolen from guest or returned back by using adjust_managed_page_count and thus /proc/meminfo shows reduced amount of memory. Fortunately the solution is simple, we should just avoid to call adjust_managed_page_count with VIRTIO_BALLOON_F_DEFLATE_ON_OOM set. Please note that neither VMWare ballon nor HyperV balloon do not care about proper handling of adjust_managed_page_count at all. Si...

...nd with VIRTIO_BALLOON_F_DEFLATE_ON_OOM configuration flag set). The bad thing is that end-user does not know this. Balloon by default reduce the amount of memory exposed to the end-user each time when the page is stolen from guest or returned back by using adjust_managed_page_count and thus /proc/meminfo shows reduced amount of memory. Fortunately the solution is simple, we should just avoid to call adjust_managed_page_count with VIRTIO_BALLOON_F_DEFLATE_ON_OOM set. Please note that neither VMWare ballon nor HyperV balloon do not care about proper handling of adjust_managed_page_count at all. Si...

...memory 1CPU. This test setups an > >> environment that has a lot of fragmentation pages. Then inflate balloon will > >> split the THPs. > > > >> // This is the THP number before VM execution in the host. > >> // None use THP. > >> cat /proc/meminfo | grep AnonHugePages: > >> AnonHugePages: 0 kB > These lines are from host. > > >> // After VM start, use usemem > >> // (https://git.kernel.org/pub/scm/linux/kernel/git/wfg/vm-scalability.git) > >> // punch-holes function generates 400m fragmentat...

Add a new field, VIRTIO_BALLOON_S_AVAIL, to virtio_balloon memory statistics protocol, corresponding to 'Available' in /proc/meminfo. It indicates to the hypervisor how big the balloon can be inflated without pushing the guest system to swap. This metric would be very useful in VM orchestration software to improve memory management of different VMs under overcommit. Signed-off-by: Igor Redko <redkoi at virtuozzo.com> Rev...

Add a new field, VIRTIO_BALLOON_S_AVAIL, to virtio_balloon memory statistics protocol, corresponding to 'Available' in /proc/meminfo. It indicates to the hypervisor how big the balloon can be inflated without pushing the guest system to swap. This metric would be very useful in VM orchestration software to improve memory management of different VMs under overcommit. Signed-off-by: Igor Redko <redkoi at virtuozzo.com> Rev...

On 03/24/2016 02:26 AM, mxs kolo wrote: > use libvirt 1.3.2, it's more stable and never show negative values > for memory and swap inside container > The latest version available for CentOS/RHEL is version 1.2.17. What site are you using to get the rpm for version 1.3.2? Peter

On 03/24/2016 05:48 AM, Peter Steele wrote: > On 03/24/2016 02:26 AM, mxs kolo wrote: >> use libvirt 1.3.2, it's more stable and never show negative values >> for memory and swap inside container >> > The latest version available for CentOS/RHEL is version 1.2.17. What > site are you using to get the rpm for version 1.3.2? > > Peter > I found a download for