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/t
On Thu, Sep 12, 2013 at 7:57 AM, Osier Yang wrote:
> Before posting it to WIKI or somewhere, I want to see if there is any
> suggestions on it, or if I missed something.
>
>
>
I suggest putting a small paragraph at the top of the article explaining
what NPIV is, and why someone would want to use
On Wed, Sep 11, 2013 at 3:52 AM, Gao feng wrote:
> 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
> >>
> ostara ~ # ebuild
> /usr/portage/app-emulation/libvirt/libvirt-1.1.2-r1.ebuild setup clean
> * libvirt-1.1.2.tar.gz SHA256 SHA512 WHIRLPOOL size ;-)
> ... [ ok ]
> * libvirt-1.1.2-e89bdf01.tar.xz SHA256 SHA512 WHIRLPOOL size ;-)
> ...
On Tue, Sep 10, 2013 at 2:20 PM, Dennis Jenkins wrote:
> On Tue, Sep 10, 2013 at 1:34 PM, Doug Goldstein 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/
On Tue, Sep 10, 2013 at 1:34 PM, Doug Goldstein wrote:
> On Tue, Sep 10, 2013 at 9:09 AM, Dennis Jenkins
> wrote:
>
> Yeah our security people got a bit over zealous. That's being rectified.
>
> :)
> >
> > TL;DR: My container is configured to use "br
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 li
priv = 0x7fe464022500
err = 0x0
__FUNCTION__ = "virLXCProcessStart"
__func__ = "virLXCProcessStart"
---Type to continue, or q to quit---
#3 0x7fe46aa9736e in lxcDomainCreateWithFlags (dom=0x7fe4580008c0,
flags=) at lxc/lxc_driver.c:1054
On Mon, Jul 15, 2013 at 7:37 AM, Dennis Jenkins wrote:
> 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
On Mon, Jul 15, 2013 at 3:18 AM, Michal Privoznik 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 i
On Mon, Jul 15, 2013 at 7:53 AM, Dennis Jenkins wrote:
>
>
>
> TL;DR: "vm->seclabels[i]->model" is NULL.
>
>
>
It probably would have been helpful had I posted everything in the struct:
(gdb) print vm->seclabels[i]
$6 = (virSecurityLabelDefPtr) 0x7fffd000
omain.
In any event, libvirtd should probably not crash due to the XML element
(which seems valid - or at least "virsh edit" allows it).
On Fri, Jul 12, 2013 at 11:44 AM, Dennis Jenkins <
dennis.jenkins...@gmail.com> wrote:
> The debug log ends with this:
>
>
> 2013-07-1
0x7fe47508d99d in clone () from /lib64/libc.so.6
(gdb)
On Fri, Jul 12, 2013 at 11:40 AM, Dennis Jenkins <
dennis.jenkins...@gmail.com> wrote:
> Hello all,
>
> I have two issues:
>
> 1) I am unable to start a seemingly correct LXC domain (I cloned it from a
> work
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 "li
On Tue, May 14, 2013 at 9:27 AM, Daniel P. Berrange wrote:
> On Tue, May 14, 2013 at 09:19:51AM -0500, Dennis Jenkins wrote:
> > On Tue, May 14, 2013 at 9:12 AM, Daniel P. Berrange >wrote:
> > > On Tue, May 14, 2013 at 09:06:36AM -0500, Dennis Jenkins wrote:
> > >
On Tue, May 14, 2013 at 9:12 AM, Daniel P. Berrange wrote:
> On Tue, May 14, 2013 at 09:06:36AM -0500, Dennis Jenkins wrote:
> > The log is large to place inline in an email (32K), so I posted it (no
> > expiration) to pastebin. But below are the juicy bits. If you want the
&g
Hello Daniel,
Thank you for your quick response. The logs you requested are below.
On Tue, May 14, 2013 at 8:55 AM, Daniel P. Berrange wrote:
> On Tue, May 14, 2013 at 08:28:48AM -0500, Dennis Jenkins wrote:We need to
> get more debug info from this file. Stop libvirtd and edit
>
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 containe
On Tue, Mar 5, 2013 at 9:33 PM, Doug Goldstein wrote:
>
> grep FUSE_FS /usr/src/linux/.config
>
> if, =m then: lsmod | grep fuse
>
> lastly, check if you have sys-fs/fuse installed.
> --
> Doug Goldstein
Hello Doug, Libvirt list,
This morning I noticed that Doug pushed out a new Gentoo ebuil
On Tue, Mar 5, 2013 at 9:33 PM, Doug Goldstein wrote:
> On Tue, Mar 5, 2013 at 4:13 PM, Dennis Jenkins
> wrote:
>>
>> Update: 1.0.3 still fails to boot an LXC container on Gentoo Linux.
>>
>> Libvirt 1.0.3 appeared in Gentoo Portage this morning. I updated my
On Mon, Feb 11, 2013 at 3:57 AM, Michal Privoznik wrote:
> On 08.02.2013 21:46, Dennis Jenkins wrote:
>> On Fri, Feb 8, 2013 at 12:38 PM, Dennis Jenkins
>> wrote:
>>> Hello.
>>>
>>> tl;dr = v1.0.0 can boot my LXC containers, v.1.0.1 and v.
On Fri, Feb 8, 2013 at 12:38 PM, Dennis Jenkins
wrote:
> 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 kno
22 matches
Mail list logo
