similar to: LXC containers - systemd takes a long time to start

Hi folks I use libvirt to programmatically spawn lxc containers I am facing an issue when migrating from fedora23 to fedora24 I use the stock kernel and libvirt version on both deployments, i.e.: f23: libvirt-1.2.18.3-2.fc23.x86_64 - kernel 4.5.7-202.fc23.x86_64 f24: libvirt-1.3.3.1-4.fc24.x86_64 - kernel 4.6.3-300.fc24.x86_64 First off, I need to outline that the host installation is done

On 09/11/2013 04:44 PM, Daniel P. Berrange wrote: > On Tue, Sep 10, 2013 at 09:09:44AM -0500, Dennis Jenkins wrote: >> I recently upgraded "libvirt" on Gentoo to 1.2.2-r1 (latest available). I >> have not used LXC containers for a few weeks, so I don't recall what >> version of libvirt I was using when my container last booted successfully. >> >>

Hi, after 2 years of "pure" LXC usage, I'm trying now to administrate our LXC containers with libvirt No problem with a LXC container I create "from Scratch" (lxc-create), but with our existing containers, I've a strange behavior with the console: vsonde43 login: Debian GNU/Linux 5.0 vsonde43 console vsonde43 login: Debian GNU/Linux 5.0 vsonde43 tty1 vsonde43 login:

I recently upgraded "libvirt" on Gentoo to 1.2.2-r1 (latest available). I have not used LXC containers for a few weeks, so I don't recall what version of libvirt I was using when my container last booted successfully. Unfortunately, Gentoo's portage tree does not offer any previous versions of libvirt that I could downgrade to. TL;DR: My container is configured to use

Hello Is there a way to set custom environment variables for LXC containers so that it is available for all processes within the container? The libvirt-lxc driver seems to be setting up only the below variables (as per the docs), but there doesn't seem to be a way customize it. containerThe fixed string libvirt-lxc to identify libvirt as the creator container_uuidThe UUID assigned to the

I'm using libvirt_lxc and that has an XML based configuration. Based on what I've read, I think I need to add this to the ctdb container's config: <features> <capabilities policy='default'> <sys_nice state='on'/> </capabilities> </features> That didn't do the trick though. I need to figure out how to turn on all caps to

I've created an EC2 AMI for AWS that essentially represents a CentOS 7 "hypervisor" image. I deploy instances of these in AWS and create an number of libvirt based lxc containers on each of these instances. The containers run fine within a single host and have no problem communicating with themselves as well as with their host, and vice versa. However, containers hosted in one

We're transitioning from a VM based environment to one that uses LXC based containers running under CentOS 7. CTDB runs fine under our CentOS 7 VMs. The same packages running under LXC however seem to have issues: # systemctl start ctdb.service Job for ctdb.service failed. See 'systemctl status ctdb.service' and 'journalctl -xn' for details. # systemctl status ctdb.service

Hello, I've encountered the following error, trying to start a domain: error: internal error Child process (PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin LIBVIRT_DEBUG=2 LIBVIRT_LOG_OUTPUTS=2:syslog:libvirtd /usr/libexec/libvirt_lxc --name vm_14 --console 18 --handshake 21 --background --veth veth1) status unexpected: exit status 1 I see nothing relevant

On 2015-08-04 at 19:27 +0200, Ralph Böhme wrote: > Hi Peter, > > On Tue, Aug 04, 2015 at 10:11:56AM -0700, Peter Steele wrote: > > We're transitioning from a VM based environment to one that uses LXC based > > containers running under CentOS 7. CTDB runs fine under our CentOS 7 VMs. > > The same packages running under LXC however seem to have issues: > > >

hello, i am new to lxc, i have created a lxc container on fedora 19 i created a container rootfs of fedora 19 by using yum --installroot=/containers/test1 --releasever=19 install openssh test1.xml file for container test1 <domain type="lxc"> <name>test1</name> <vcpu placement="static">1</vcpu> <cputune>

On 04/01/2016 02:07 PM, Laine Stump wrote: > On 03/31/2016 06:43 PM, Peter Steele wrote: >> I've created an EC2 AMI for AWS that essentially represents a CentOS >> 7 "hypervisor" image. I deploy instances of these in AWS and create >> an number of libvirt based lxc containers on each of these instances. >> The containers run fine within a single host and

Hi all I have CentOS Linux release 7.0.1406, libvirt 1.2.7 installed. Just after create and start inside LXC container present cgroups. Example for memory: [root@ce7-t1 /]# ls -la /sys/fs/cgroup/memory/ total 0 drwxr-xr-x 2 root root 0 Sep 15 17:14 . drwxr-xr-x 12 root root 280 Sep 15 17:14 .. -rw-r--r-- 1 root root 0 Sep 15 17:14 cgroup.clone_children --w--w--w- 1 root root 0 Sep 15

Hi there I’m not quite proficient with libvirt yet, and have been using it so far primarily to manage lxc containers I was hoping to find a means to configure the set of capabilities that guests should drop, but came across a few web pages suggesting these were set in stone in the code is this correct, or is there a means to tweak this set from the host via the xml config or a virsh command ?

I'm setting up a system to run LXC containers with ZFS on Linux (Ubuntu 14.04). I intend to set up a base image which I'd like to clone to create other containers from. virt-sysprep and virt-customize seem ideal for the task: I obviously could mount and work with the rootfs from each container directly, but the libguestfs tools have a bunch of pre-existing recipes that would surely be much

Warning - I'm fairly new to libvirt, lxc and systemd so there is a good chance I'm doing something terribly wrong here. However, instead of continuing to struggle, I figured I would mail the list for some advice. What I'm trying to accomplish is a libvirt-lxc, systemd-based container running on my system (Fedora 19). I've read that sharing the underlying OS filesystem with

Hi, I noticed that libvirt-lxc will be deprecated for RedHat: "Future development on the Linux containers framework is now based on the docker command-line interface. libvirt-lxc tooling may be removed in a future release of Red Hat Enterprise Linux (including Red Hat Enterprise Linux 7) and should not be relied upon for developing custom container management applications." -

Hello. I use libvirtd on my Gentoo development system to manage both QEMU and LXC. When 1.0.3 came out, I updated to it from 1.0.3-r2, but 1.0.4 failed to start my LXC containers. I did not research the issue at the time, so I revert to 1.0.3-r2. Today I updated to 1.0.5 and my LXC containers still fail to start. I have not changed my domain XML at all. I am looking for suggestions on

Hello everyone, I am running multiple nodes each having multiple LXC containers. On those nodes I am using Tinc to share the subnet 10.20.0.0. The LXC containers may migrate between nodes and should keep the same configuration. On all nodes traffic from the external interfaces (connected to the internet) is forwarded to the bridge interfaces and masqueraded. The LXC containers are using 10.20.0.1

Thanks for the feedback I take it from your answer that there is no current plan in the direction of adding this as a feature, right ? In this case, how would you welcome pull requests if we managed to add this on our side ? Many thanks — Thierry On 29 Jan 2014, at 14:27, Daniel P. Berrange <berrange@redhat.com> wrote: > On Wed, Jan 29, 2014 at 09:43:25AM +0100, Thierry Parmentelat