similar to: libvirt-1.2.2-r1 (Gentoo) fails to start LXC containers

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

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, Sep 10, 2013 at 1:34 PM, Doug Goldstein <cardoe@gentoo.org> wrote: > On Tue, Sep 10, 2013 at 9:09 AM, Dennis Jenkins > <dennis.jenkins.75@gmail.com> wrote: > > Yeah our security people got a bit over zealous. That's being rectified. > > :) > > > > TL;DR: My container is configured to use "br0" for its networking. "br0"

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. > > ostara ~ # tail /var/log/libvirt/lxc/dwj-hfax-dev.log > 2013-09-10

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

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

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. tl;dr = v1.0.0 can boot my LXC containers, v.1.0.1 and v.1.0.2 fails. Paraphrased error message: "lxcContainerMountProcFuse:616 : Failed to mount ..../meminfo" I'd like to know if my host is misconfigured, or my domains, or ... why 1.0.2 and 1.0.1 are not working for me. I've been using libvirt for a while to manage QEMU instances. I have experimented with lxc.

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

Hello again, TL;DR: Today I noticed that my LXC container was out of space in "/dev". It took me a few minutes to figure out why. There were only 23 files there. The "/dev" fs quota was 64K, and all was taken up. The problem was that "syslog-ng" was writing "console" messages to "/dev/tty12". But "/dev/tty12" was not a device

Ah ha! I just learned about "gdb bt full". The existing core dump might have what you need: Line #442. However, the line numbers for the source code in the source tree that my Gentoo system is building from does not match exactly what you listed. Line #442 for me is the one containing the "STREQ" macro: virObjectLock(mgr); for (i = 0; i < vm->nseclabels; i++)

On Mon, Jul 15, 2013 at 3:18 AM, Michal Privoznik <mprivozn@redhat.com>wrote: > > Interesting. If you are still able to reproduce the crash, can you try to > get the line number within virSecurityManagerGenLabel where the crash > happened? I think it's the STREQ line (440 linenr). Question is whether > model or name is NULL. > > I'll try. I'm not sure why

On 12.07.2013 20:32, Dennis Jenkins wrote: > 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

On Tue, Sep 10, 2013 at 2:20 PM, Dennis Jenkins <dennis.jenkins.75@gmail.com > wrote: > On Tue, Sep 10, 2013 at 1:34 PM, Doug Goldstein <cardoe@gentoo.org>wrote: > >> A suggestion would be to make sure that you have all the necessary >> kernel options enabled. You can check with: ebuild >> /usr/portage/app-emulation/libvirt/libvirt-1.1.2-r1.ebuild setup clean

Hello Samba friends, sometimes i have this messages in my Samba Log (2.06). Then, i have a problem to connect me to the share. Can anyone tell me what the problem is ? 305513 (193.101.245.125) couldn't find service d3n [2001/03/16 12:47:17, 0] lib/util_sock.c:(474) read_socket_data: recv failure for 4. Error = Connection reset by peer [2001/03/16 12:51:54, 0] smbd/service.c:(209)

(oops accidentally sent to -owners) Hi, i'm trying to start a LXC guest on a F14 computer .. followed the examples in http://libvirt.org/drvlxc.html, but got stuck when starting it .. 03:07:23.706: debug : virCgroupNew:542 : New group / 03:07:23.707: debug : lxcControllerRun:563 : Setting up private /dev/pts 03:07:23.711: debug : lxcControllerRun:589 : Mouting 'devpts' on

When we create an L2 loop on a bridge in netns, we will see packets storm even if STP is enabled. # unshare -n # ip link add br0 type bridge # ip link add veth0 type veth peer name veth1 # ip link set veth0 master br0 up # ip link set veth1 master br0 up # ip link set br0 type bridge stp_state 1 # ip link set br0 up # sleep 30 # ip -s link show br0 2: br0:

hi fellow XEN-users: I have been trying hard to get this problem fixed, hope I can get some help here. Thanks in advance for your time. I have a typical dom0 + domU XEN setup. after I start xend and network-bridge, I get the default network setup, , peth0 -------- bridge ------------------------------------------------------- |

Hello, Since my last update of xen, I am having problems with bridges and xen. When I want to start a bridge on the dom0 (to run a domU in a different vlan than the default) I run /etc/xen/scripts/network-bridge start netdev=eth0.302 bridge=xen-br302 antispoof=no where eth0.302 is an interface associated with my vlan 302 (it tags with this vlan identifier). The problem I have is that it

On 12/07/2023 02:54, Kuniyuki Iwashima wrote: > When we create an L2 loop on a bridge in netns, we will see packets storm > even if STP is enabled. > > # unshare -n > # ip link add br0 type bridge > # ip link add veth0 type veth peer name veth1 > # ip link set veth0 master br0 up > # ip link set veth1 master br0 up > # ip link set br0 type bridge stp_state 1