Displaying 3 results from an estimated 3 matches for "nveths".
Did you mean:
veths
2013 Jul 15
0
Re: libvrtd-1.1.0 crashes when attempting to start some (but not all) LXC containers
...=VIR_DOMAIN_RUNNING_BOOTED) at lxc/lxc_process.c:1144
rc = -1
r = <optimized out>
nttyFDs = 1
ttyFDs = 0x7fe458001790
i = <optimized out>
logfile = 0x7fe458000ad0 "/var/log/libvirt/lxc/dwj-hfax-dev.log"
logfd = -1
nveths = 0
veths = 0x0
handshakefds = {-1, -1}
pos = -1
ebuf =
"\000\000\000\000\344\177\000\000\020\000\000\000\000\000\000\000\376\377\377\377\377\377\377\377\000\000\000\000\000\000\000\000\377\377\377\377",
'\000' <repeats 12 times>"\364,
\3...
2014 Sep 16
2
1.2.7 and 1.2.8 fail to start container: libvirt_lxc[4904]: segfault at 0 ip ...error 4 in libc-2.17.so[
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 Jul 15
3
Re: libvrtd-1.1.0 crashes when attempting to start some (but not all) LXC containers
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