similar to: How to see the console output of an EXE session?

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:

We are trying to create RHEL6.1 container and having trouble getting a proper console to the container. I have used lxc containers in the past and lxc has a script (lxc-fedora) to setup a basic Fedora container. Is there something similar or docs with virtmgr ? We started out making a copy of the root fs and using that copy as the root for the container. I made a couple of tweaks to the

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

On 01/29/2016 05:08 AM, Peter Steele wrote: > We have been researching stuck zombie processes in our libvirt lxc > containers. What we found was: > > 1) Each zombie’s parent was pid 1. init which symlinks to systemd. > 2) In some cases, the zombies were launched by systemd, in others the > zombie was inherited. > 3) While the child is in the zombie state, the parent

Hi, I am creating containers using libvirt-lxc. My problem is that a process at bootup gets stuck at some point. My usecase is Puppet, but I can reproduce with a loop in bash. I noticed it is stuck until I connect to the console of the container (virsh -c lxc:/// console id). Then after disconnecting the console, waiting some times, the process gets stuck again. The more the process outputs

> 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

On Fri, Jan 29, 2016 at 10:25:08AM -0800, Peter Steele wrote: >On 01/29/2016 05:08 AM, Peter Steele wrote: >> We have been researching stuck zombie processes in our libvirt lxc >> containers. What we found was: >> >> 1) Each zombie’s parent was pid 1. init which symlinks to systemd. >> 2) In some cases, the zombies were launched by systemd, in others the >>

I use libvirt to manage a container based environment. Is there an efficient method for testing if someone has a console session open for a given container? The approach I'm using at the moment is to use lsof and check if there is an entry for the container's console pts device. For example, I can determine a container's console device from its xml definition: # virsh dumpxml

Hi all, I am trying to init lxc by libvirt instead of using lxc tools. I have several questions as following: software platform: integrating libvirt-0.10.1 to yocto based on sdk1.3 hardwatre platform: p4080ds steps: root at p4080ds:~# cat > container.xml <<EOF <domain type='lxc'> <name>container</name>

On Mon, Aug 10, 2015 at 09:50:04PM +0100, Mark Clarkson wrote: >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

Dear all, In my applications, the real-time performance is very important, so I used 4 containers, with only one application running in each container and a physical CPU core is only dedicated to one lxc. and I must know which container is hosted by which CPU core. That is, I need to pin a specific lxc to a specific CPU core. I can achieve this in a native linux system by the following xml

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

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

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

Hi, I am trying to run containers on rhel 6.2 using libvirt-lxc. I want to migrate my containers from sf.net lxc to libvirt-lxc. So, I am using the same root file system for libvirt-lxc, which I used for sf.netlxc. After starting the container, and getting console for it, I can see the boot log for the container, it shows all the services started successfully. I get ping reply from the IP assigned

Hello, I am starting the system container without "/" directory So that it can share the host /bin /sbin /lib and /lib64 and i have sepeartely mounted /var, /etc and /usr directory for the container Below is xml file <domain type='lxc'> <name>test6</name> <memory>102400</memory> <os> <type>exe</type>

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 Wed, Jul 31, 2013 at 12:46:58PM +0530, Aarti Sawant wrote: > 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>

On Mon, Aug 10, 2015 at 09:50:04PM +0100, Mark Clarkson wrote: > 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

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