From: AL13N <alien@rmail.be>
To: xen-devel@lists.xen.org
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
Dario Faggioli <dario.faggioli@citrix.com>,
Jim Fehlig <jfehlig@suse.com>,
Marek Marczykowski <marmarek@invisiblethingslab.com>
Subject: Re: OT: xen libvirt issue
Date: Mon, 08 Apr 2013 08:26:15 +0200 [thread overview]
Message-ID: <7659328.YPt9AoC338@localhost> (raw)
In-Reply-To: <51624619.2050100@invisiblethingslab.com>
Op maandag 8 april 2013 06:22:49 schreef Marek Marczykowski:
> On 05.04.2013 13:13, George Dunlap wrote:
> > On Fri, Apr 5, 2013 at 9:21 AM, Dario Faggioli
> >
> > <dario.faggioli@citrix.com> wrote:
> >> On gio, 2013-04-04 at 21:49 +0200, AL13N wrote:
> >>> i realise this is completely off-topic, but if someone on this list has
> >>> some knowledge on this, see:
> >>>
> >>> https://www.redhat.com/archives/libvir-list/2013-April/msg00189.html
> >>>
> >>> the issue is that shutting down xen domains, segfaults libvirtd... which
> >>> is
> >>> annoying
> >>
> >> I don't have any clue on this... But, perhaps, Jim does (Cc-ing him)?
> >
> > The e-mail that AL13N linked to was actually from Jim, saying he would
> > be really busy for a while and unable to look at it.
> >
> > The question isn't off-topic, as libxl and xend have to work closely
> > with libvirt. Unfortunately, I don't think any of the active
> > developers on this list has much familiarity with libvirt. It Would
> > Be Good if someone could step up and learn, but with our feature
> > freeze next week, we're also kind of heads-down getting stuff
> > implemented...
>
> I believe it is already fixed in unstable by this commit:
> 5f5ef65babc2ca15f43b775c4b47b0102fa2a632 "libxl: fix stale timeout event
> callback race"
>
> Sadly backport to 4.2 isn't trivial.
Looking at the patch i totally agree that it isn't trivial...
i'll hold off for now. and will work more towards libvirt integration for
Mageia 4 (our release freeze is now in effect for Mageia 3).
thanks for all the help!
next prev parent reply other threads:[~2013-04-08 6:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 19:49 OT: xen libvirt issue AL13N
2013-04-05 8:21 ` Dario Faggioli
2013-04-05 11:13 ` George Dunlap
2013-04-08 4:22 ` Marek Marczykowski
2013-04-08 6:26 ` AL13N [this message]
2013-04-08 15:36 ` Jim Fehlig
2013-04-08 17:22 ` Stefano Stabellini
2013-04-08 17:57 ` AL13N
2013-04-08 15:46 ` Jim Fehlig
2013-04-08 16:09 ` Ian Jackson
2013-04-08 17:53 ` AL13N
2013-04-09 12:39 ` Ian Jackson
2013-04-09 12:52 ` AL13N
2013-04-09 14:41 ` Jim Fehlig
2013-04-09 21:50 ` AL13N
2013-04-10 0:42 ` Jim Fehlig
2013-04-10 10:23 ` AL13N
2013-04-09 14:15 ` Jim Fehlig
2013-04-09 14:18 ` Ian Jackson
2013-04-09 21:48 ` AL13N
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=7659328.YPt9AoC338@localhost \
--to=alien@rmail.be \
--cc=George.Dunlap@eu.citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=jfehlig@suse.com \
--cc=marmarek@invisiblethingslab.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.