similar to: Has libvirt guest pagecache level ?

Hi all. Has someone success story with using autofs + nfs inside libvirt LXC container ? In my case nfs client and server in lxc work just fine, but with autofs hang on system call state(). I use CE7_64 on nodes and inside container with libvirt 1.2.18 May be I must set some of capabilities in <feature> (http://man7.org/linux/man-pages/man7/capabilities.7.html) ? I try only CAP_SYS_ADMIN

On 04/26/2016 07:44 AM, mxs kolo wrote: > 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 ); >

I'm running libvirt 0.10.2 and qemu-kvm-1.2.0, both compiled from source, on CentOS 6. I've got a working blkio cgroup hierarchy which I'm attaching guests to using the following XML guest configs: VM1 (foreground): <cputune> <shares>2048</shares> </cputune> <blkiotune> <weight>1000</weight> </blkiotune>

Hi All, I've been chasing down an issue in recent weeks (my own lab, so no prod here) and I'm reaching out in case someone might have some guidance to share. I'm running fairly large VMs (RHOSP underclouds - 8vcpu, 32gb ram, about 200gb single disk as a growable qcow2) on some RHEL7.6 hypervisors (kernel 3.10.0-927.2x.y, libvirt 4.5.0, qemu-kvm-1.5.3) on top of SSD/NVMe drives

On 04/26/2016 10:01 AM, mxs kolo wrote: >> Cool, thanks for the info! Does this still affect libvirt 1.3.2 as well? You >> mentioned elsewhere that you weren't hitting this issue with that version > Sorry, I miss version and another details. > Test make on CentOS Linux release 7.2.1511 (Core) > and libvirt 1.3.2, build from sources with next options: > --without qemu \

>> 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

On Fri, May 24, 2013 at 02:59:05AM +0000, Gonglei (Arei) wrote: > Hi, > > > > > On Thu, 23 May 2013, Gonglei (Arei) wrote: > > > Hi, all > > > > > > I use O_DIRECT to open disk images for IDE, but I'm failed. After debug, I get > > the below logs: > > > [2013-05-22 23:25:46] ide: CMD=c8 > > > [2013-05-22 23:25:46] bmdma:

> So maybe we have a bug where the build depends on pre-installed files, > rather than building properly from the tarball. Good thing it's easy to > make a virgin VM to test this theory. Like I said, I'll try and > reproduce and fix this, but it may be a couple days. Some news. I get libvirt-1.2.8-rc1.tar.gz and successfully build it on my "problem" node, without

https://bugzilla.redhat.com/show_bug.cgi?id=1681180 b.r. Maxim Kozin

Hi all. I use LXC on Centos 7 x86-64, with libvirt version 1.2.6 and 1.2.12 My container has bridged network: # virsh dumpxml test1 <domain type='lxc'> <name>test1</name> <uuid>518539ab-7491-45ab-bb1d-3d7f11bfb0b1</uuid> <memory unit='KiB'>1048576</memory> <currentMemory unit='KiB'>1048576</currentMemory>

Hi. I need to use /dev/ppp inside the lxc container, for very ancient software. Problem solved this way: 1) virsh edit container name and add section: <features> <capabilities policy='default'> <mknod state='on'/> </capabilities> </features> 2) start container 3) attach or ssh container, be root: #mknod /dev/ppp c 108 0 4) inside

HI all Centos 7, 3.10.0-123.6.3.el7.x86_64 libvirt 1.27, libvirt 1.2.8 builded from source with ./configure --prefix=/usr make && make install LXC with direct network failed to start: Sep 16 19:19:38 node01 kernel: device br502 entered promiscuous mode Sep 16 19:19:39 node01 kernel: device br502 left promiscuous mode Sep 16 19:19:39 node01 avahi-daemon[1532]: Withdrawing workstation

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

> Thanks for the report. That is disabling quite a lot of drivers (what > is still left, lxc?), so it's a combination that has not gotten a lot of > testing. I'll definitely look at fixing it before 1.2.8 is released, > although it may miss release candidate 0. It's no problem of configure options. Simple ./configure result: configure: configure: Configuration summary

Hi all Centos 7.0.1406, 3.10.0-123.el7.x86_64 Configure libvirt-1.2.7 as: ./configure --prefix=/usr --with-xen=no --with-qemu=no --with-openvz=no --with-vmware=no --with-esx=no --with-parallels=no --with-bhyve=no --with-uml=no --with-vbox=no --with-selinux=no make ... make[3]: Entering directory `/usr/local/src/libvirt-1.2.7/daemon' CC libvirtd-remote.o CCLD libvirtd

On Sat, Aug 08, 2020 at 01:24:02AM +0300, Nir Soffer wrote: > The new cache=none mode is misleading since it does not avoid usage of > the page cache. When using shared storage, we may get stale data from > the page cache. When writing, we flush after every write which is > inefficient and unneeded. > Hmm. This isn't actually what the cache=none parameter is currently doing.

Hi all Each lxc container on node have mounted tmpfs for cgroups tree: [root-inside-lxc@tst1 ~]# mount | grep cgroups cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on

On Sun, Aug 9, 2020 at 12:28 AM Richard W.M. Jones <rjones@redhat.com> wrote: > > On Sat, Aug 08, 2020 at 01:24:02AM +0300, Nir Soffer wrote: > > The new cache=none mode is misleading since it does not avoid usage of > > the page cache. When using shared storage, we may get stale data from > > the page cache. When writing, we flush after every write which is > >

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

Commit-ID: 3fefc6a404a970a911417d0345618a7e9abfef70 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=3fefc6a404a970a911417d0345618a7e9abfef70 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Wed, 6 Jan 2016 00:43:25 +0000 Committer: H. Peter Anvin <hpa at linux.intel.com> CommitDate: Tue, 5 Jan 2016 17:45:36 -0800 [klibc] MIPS: Update archfcntl.h