similar to: How to test if a console session is active?

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

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

The debug log ends with this: 2013-07-12 16:43:31.740+0000: 21365: debug : virCgroupMakeGroup:708 : Make group /machine/dwj-hfax-dev.libvirt-lxc 2013-07-12 16:43:31.740+0000: 21365: debug : virCgroupMakeGroup:729 : Make controller /sys/fs/cgroup/cpu/machine/dwj-hfax-dev.libvirt-lxc/ 2013-07-12 16:43:31.740+0000: 21365: debug : virCgroupMakeGroup:729 : Make controller

Update: I am able to edit the XML in "dwj-hfax-dev" such that libvirtd no longer crashes, and edit the XML for "dwj-lnx-dev" such that it will crash. The presents of "<seclabel type='none'/>" near the bottom causes libvirtd to crash. I do not recall ever manually adding that to my domain. In any event, libvirtd should probably not crash due to the

Hello all, I have two issues: 1) I am unable to start a seemingly correct LXC domain (I cloned it from a working domain). 2) I am able to crash "libvirtd" by attempting to start the cloned domain, but starting the original works just fine. I humbly submit that item #2 is a bug - the "libvirtd" daemon should never crash due to anything the "libvirt" client

On Tue, Jul 30, 2013 at 05:49:28PM +0800, hzguanqiang wrote: > Hi Guys, > I started a lxc container with libvit in ubuntu Operating system, and succeed using lxc-enter-namespace to enter the namespaces and security context of the container. But when I do the same thing in debian OS, It reported an error, with details as following: > > root@debian:/etc# vir list > Id Name

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

Hi there I am using fedora21 for hosts and guests, using lxc containers, and was on vanilla 1.2.9 as exposed by the fedora yum repo The other day I was needing the ability to grant mknod capability to some guests, some chap on IRC kindly pointed me at the <capabilities> tag However I was told that needed 1.2.11 So I went and rebuilt from this download

Hi Guys, I started a lxc container with libvit in ubuntu Operating system, and succeed using lxc-enter-namespace to enter the namespaces and security context of the container. But when I do the same thing in debian OS, It reported an error, with details as following: root@debian:/etc# vir list Id Name State ---------------------------------------------------- 4424

Hello, First I apologize because I sent this email on the lxc-users mailing by error. So sorry for the double message. I'm trying to run an X server inside a container. I was able to achieve this with lxc-tools (and that is why I mixed myself between the 2 lists) by setting the option lxc.tty = 4 that allows access to 4 tty. Now I want to use libvirt because my final goal is to

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 process (systemd) /proc/1/status shows no pending signals. 4) Attaching gdb to

Hello. I am experimenting with LXC via libvirt on my Gentoo development system. I can start the LXC domain and connect to its console. However, I am unable to login as root. I've used "chroot" and "passwd" from the host system to explicitly set the root password. Still no luck. So I began debugging.... I ran "strace" on the container's

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

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

于 2013/7/15 17:32, Gao feng 写道: > On 07/15/2013 05:18 PM, hzguanqiang wrote: >> Hi, Gao Feng >> >> I've tried what you said, but still exists the problem: >> >> ubuntu@lxc:~$ vir attach-disk instance-0000002c /dev/dm-0 sdb >> error: Failed to attach disk >> error: Unable to create device /proc/10366/root/dev/sdb: Permission denied >>

Hello, I would like to set up sshd under an LXC application container and to be able to connect into it from the host. I was able to achieve that with LXC tools CLI after setting up a bridge via brctl and creating a proper lxc.conf file for lxc-execute to use. However, I am unable to do so via libvirt. I am using libvirt version 0.7.1 installed on fedora 12. I first verified that the default

Hi all, When I create a LXC guest(RHEL5.4) via libvirt, the guest could boot successfully. I could ping to guest, but can not ssh into the it. The secure log in the guest shows that this is due to lack of '/dev/tty' device: # tail /path/to/rootfs/of/container/var/log/secure Jul 27 04:25:25 xen2143v sshd[671]: Accepted password for zhangyufang from 10.0.0.1 port 34102 ssh2 Jul 27 04:25:25

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

On Mon, January 16, 2012 17:01, Dennis Jacobfeuerborn wrote: > On 01/16/2012 10:16 PM, James B. Byrne wrote: > > ... >> The xmldump for this guest instance contains this: > ... > > Please post the xmldumps of the original guest and cloned > guest right after > cloning and without any modifications. > > Regards, > Dennis Prototype dumpxml virsh # dumpxml

Hi, I'm using libvirt and qemu on Debian Wheezy. I'm having a strange behavior. Guests can't connect to each other when they're on the same host. On the host I'm using bonding (in active / backup mode) and vlan. It looks like this : eth0 \ / macvtap0 bond0 --- vlan222 eth1 / \ macvtap1 So I've got two guests, let's say A and B. When