public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: New Addon Libvirt
Date: Wed, 26 Nov 2014 21:37:28 +0100	[thread overview]
Message-ID: <1417034248.1417.314.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <C355D9EE29884B118366C2162E5476CE@Severus>

[-- Attachment #1: Type: text/plain, Size: 1906 bytes --]

Hi Jonatan,

On Wed, 2014-11-26 at 20:19 +0100, Jonatan Schlag wrote:
> Hi at all
>  
> At first sorry for my awful English, I hope you can understand me.

It's okay. You are doing fine.
 
> Now to the topic. I would use my Ipfire as a host for some virtual
> machines. Qemu is as a package available but I would like to manage my
> virtual machines about libvirt.  
> So libvirt is not available for Ipfire. So I try to compile it for
> Ipfire and I managed it. 

Good.

> The libvirt daemon run on my Ipfire! I must build 4 dependencies
> (libyajl, libpciaccess, lipdevmapper and util-macros). 

libdevmapper should be available in the development branch. The rest is
not.

> But now I get a Segmention fault when I type “libvirtd”.
> This is the error ( I find it in the kernel log files):
>  
> libvirtd[31422]: segfault at 0 ip a19fe6a1 sp 9bfc4f0c error 4 in
> libc-2.12.so[a 1983000+174000]
>  
> This file is part of glibc. I do not know how I can solve this error,
> but I will do what  I can do to help you, say what  I must do and will
> try it.

It is a bit hard to tell what went wrong here just by the information I
have. Could you please upload the binary packages to somewhere so that I
can run it with some debugging tools and see what I can find out?

Basically something is trying to access memory that is either not there
or does not belong to the application. Check if you have the latest
version and maybe there is something in the libvirtd bugtracker.

> Best Regards Jonatan 
>  
> PS:  I am called Yassen in the forum.
> PSS: Is there a reason why the qemu version is so old ?

No, you can update that as well if you want. I guess that you will
require a recent version to work with libvirtd any way.

-Michael

> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

           reply	other threads:[~2014-11-26 20:37 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <C355D9EE29884B118366C2162E5476CE@Severus>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1417034248.1417.314.camel@rice-oxley.tremer.info \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox