search for: kolomax

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

> And all was fine, before I accidentally upgraded Centos to 7.1.1503 > After upgrade LXC can't start with diagnostic: > [root@node14 ~]# virsh start test1 > error: Failed to start domain test1 > error: internal error: guest failed to start: internal error: Child > process (ip link set macvlan0 netns 25263) unexpected exit status 2: > RTNETLINK answers: Invalid argument

Additioanl info. after start automount inside LXC, in /etc/mtab added string: /etc/auto.nfs /host autofs rw,relatime,fd=6,pgrp=679,timeout=10,minproto=5,maxproto=5,indirect 0 0 And autmount hang on lstat('/host/SOMETHING') If comment lstat() in code, automount would try make directory inside /host/ and mkdir in such case return -1: 126 int ret = mkdir(path, mode);

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

>> 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. What kind problem ? Network ? b.r. Maxim Kozin

>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 \ --without xen \ --without openvz \ --without vmware \ --without

Hi all We run LXC contrainers in macvlan bridge mode, i.e.; <interface type='direct'> <mac address='02:00:00:da:e1:b9'/> <source dev='eno1.502' mode='bridge'/> </interface> In process list: 5339 ? Sl 0:03 /usr/libexec/libvirt_lxc --name t2.infra --console 21 --security=none --handshake 24 --veth macvlan6 28645 ?

Greetings Has libvirt dedicated page cache area for guest ? If not - what is the difference between cache='none' and cache='directsync' ? >The optional cache attribute controls the cache mechanism, possible >values are "default", "none", "writethrough", "writeback", "directsync" >(like "writethrough", but it

Hi all We use libvirt 3.0.0 + lxc, disk for container described with <filesystem/> tag, example: <filesystem type='block' accessmode='passthrough'> <source dev='/dev/data/lvm-part1'/> <target dir='/'/> </filesystem> Now we start use ssd disk and think how to provide additional options for mount root FS in container:

> Centos 7.6 with libvirt build from base "virt" repository: > libvirt-daemon-driver-lxc-5.0.0-1.el7.x86_64 > libvirt-client-5.0.0-1.el7.x86_64 > libvirt-daemon-5.0.0-1.el7.x86_64 > libvirt-daemon-driver-network-5.0.0-1.el7.x86_64 > libvirt-libs-5.0.0-1.el7.x86_64 > + > systemd-219-62.el7_6.2.x86_64 > > Now lxc containers with type='direct' can be

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

> 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

HI all >After unpredictable time passed (1-5 day ?), cgroups inside LXC >magicaly removed. virsh dumpxml config look like this: <domain type='lxc' id='3566'> <name>puppet</name> <uuid>6d49b280-5686-4e3c-b048-1b5d362fb137</uuid> <memory unit='KiB'>8388608</memory> <currentMemory

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

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

Hello. Centos 7.6 with libvirt build from base "virt" repository: libvirt-daemon-driver-lxc-5.0.0-1.el7.x86_64 libvirt-client-5.0.0-1.el7.x86_64 libvirt-daemon-5.0.0-1.el7.x86_64 libvirt-daemon-driver-network-5.0.0-1.el7.x86_64 libvirt-libs-5.0.0-1.el7.x86_64 + systemd-219-62.el7_6.2.x86_64 Now lxc containers with type='direct' can be started, but can't be stopped :)

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

We run unprivileged lxc containers (libvirt based) with next config: ... <idmap> <uid start='0' target='65535' count='65535'/> <gid start='0' target='65535' count='65535'/> </idmap> ... <devices> <emulator>/usr/libexec/libvirt_lxc</emulator> <filesystem type='mount'

Hi all After upgrade from Centos 7.5 to Centos 7.6, our test environment geted new version of libvirt 4.5.0 In which our old containers have broken config and can't start: 2018-12-05 10:38:32.634+0000: 18010: debug : virLXCControllerGetNICIndexes:368 : Getting nic indexes 2018-12-05 10:38:32.634+0000: 18010: error : virLXCControllerGetNICIndexes:400 : unsupported configuration: Unsupported