similar to: Block device caching causes out of memory in dom0

I just about have my PV block device drivers booting, except just before the login screen appears I get a message that the registry couldn''t be written out. I''m pretty sure that this is because some data from the int13 interface provided by the qemu intel ide driver that has been written, hasn''t actually made it to the block device (lvm volume in my case). I''ve

Hi List, I used samba-4.1.18 as domain controller and tried to use romaing profile. I got memory leak when every account with profile path setting logout. Every account with profile path setting eat almost 10mB memory so my samba machine crash if there are many hundred account with profile setting in domain. Any option in smb.conf or operation can help ? This is my reproduce setps: 1. create

Hello all, I have some DomU''s with root and swap images on files under Xen 3.0.0 Investigating some cases of boot failure of domUs, I stumbled upon the fact that when a domU is shutdown via xm shutdown, not all of its images are released from their /dev/loopX - devices. That is, for i in /dev/loop*; do losetup $i; done still shows output for that image. It seems to me that the

Hello, I was using a bunch of cpios in initramfs as a working system, and wondering why the unused files weren't being paged out to swap. So I reread ramfs-rootfs-initramfs.txt and now I know. So I wrote the attached utility. It creates a tmpfs, moves all files on the initramfs, moves / and executes the real init. It works, even with hardlinks, but it isn't the correct approach. Have

Are you running with DHCP IP adress? ( not adviced ) i see, .. >dns forwarder = 127.0.1.1 run : hostname -i hostname -I if you see anything with 127.0.x.x Then your setup is not correct and can have problems. ( for example with authentication. ) please make sure your /etc/hosts file does not contain 127.0.1.1 of sorts. like : 127.0.0.1 localhost localhost.localdomain 192.168.0.1

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 "x" characters are not really needed in this context, and they can make the resulting

On Thu, Jul 16, 2020 at 10:41:50AM +0800, Hui Zhu wrote: > The first, second and third version are in [1], [2] and [3]. > Code of current version for Linux and qemu is available in [4] and [5]. > Update of this version: > 1. Report continuous pages will increase the speed. So added deflate > continuous pages. > 2. According to the comments from David in [6], added 2 new vqs

On Thu, Jul 16, 2020 at 03:01:18PM +0800, teawater wrote: > > > > 2020?7?16? 14:38?Michael S. Tsirkin <mst at redhat.com> ??? > > > > On Thu, Jul 16, 2020 at 10:41:50AM +0800, Hui Zhu wrote: > >> The first, second and third version are in [1], [2] and [3]. > >> Code of current version for Linux and qemu is available in [4] and [5]. > >>

I've seen several posts over the past 2-3 weeks about memory issues. I've tried to carefully follow the suggestions, but remain baffled as to why I can't load data into R. I hope that in revisiting this issue that I don't exasperate the list. The setting: 1 gig RAM , Linux machine 10 Stata files of approximately 14megs each File contents appear at the end of this boorishly long

I've seen several posts over the past 2-3 weeks about memory issues. I've tried to carefully follow the suggestions, but remain baffled as to why I can't load data into R. I hope that in revisiting this issue that I don't exasperate the list. The setting: 1 gig RAM , Linux machine 10 Stata files of approximately 14megs each File contents appear at the end of this boorishly long

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:

On Thu, Mar 12, 2020 at 03:49:54PM +0800, Hui Zhu wrote: > If the guest kernel has many fragmentation pages, use virtio_balloon > will split THP of QEMU when it calls MADV_DONTNEED madvise to release > the balloon pages. > This is an example in a VM with 1G memory 1CPU: > cat /proc/meminfo | grep AnonHugePages: > AnonHugePages: 0 kB > > usemem --punch-holes -s -1

Ok, I''ve been chasing this for many days .. I have a server running 10 instances that periodically freezes .. then sometimes "comes back." I tried many things to try to spot the problem and finally found it by accident. It''s a little frustrating as typically the Dom0 and One (or two) instances "go" and the rest carry on .. and there is diddley squat when it

Now reporduced with 100% 1) create contrainer with memory limit 1Gb 2) run inside simple memory test allocator: #include <malloc.h> #include <unistd.h> #include <memory.h> #define MB 1024 * 1024 int main() { int total = 0; while (1) { void *p = malloc( 100*MB ); memset(p,0, 100*MB ); total = total + 100; printf("Alloc %d Mb\n",total); sleep(1);

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

On 03/23/2016 01:41 PM, Peter Steele wrote: > 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

On 12.03.20 08:49, Hui Zhu wrote: > If the guest kernel has many fragmentation pages, use virtio_balloon > will split THP of QEMU when it calls MADV_DONTNEED madvise to release > the balloon pages. > This is an example in a VM with 1G memory 1CPU: > cat /proc/meminfo | grep AnonHugePages: > AnonHugePages: 0 kB > > usemem --punch-holes -s -1 800m & > >

On 12.03.20 08:49, Hui Zhu wrote: > If the guest kernel has many fragmentation pages, use virtio_balloon > will split THP of QEMU when it calls MADV_DONTNEED madvise to release > the balloon pages. > This is an example in a VM with 1G memory 1CPU: > cat /proc/meminfo | grep AnonHugePages: > AnonHugePages: 0 kB > > usemem --punch-holes -s -1 800m & > >

Im trying to use newer simple-menu features, and have found that the following config-file (closely based on wiki pxelinux example) - fails for 3.62-pre11, - works for 3.62-pre10 where 'working' is successive reloads such that re-edits of file are seen on next reload and broken is issuing this error: Initial menu has no LABEL entries! boot: #>

I have recently noticed an unusual side-effect of running Wine. When I first start up my system, /proc/meminfo reports MemTotal as 256892 kb. After running Wine for awhile, /proc/meminfo reports MemTotal as 32680 kb. The system performs as if it only had 32 MB of RAM. A reboot of the system resets total memory to the proper value. My question is: 1) Has anybody else encountered this? 2)