All of lore.kernel.org
 help / color / mirror / Atom feed
From: AL13N <alien@rmail.be>
To: xen-devel@lists.xen.org
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
	Marek Marczykowski <marmarek@invisiblethingslab.com>,
	Jim Fehlig <jfehlig@suse.com>,
	Dario Faggioli <dario.faggioli@citrix.com>,
	Bamvor Jian Zhang <bjzhang@suse.com>
Subject: Re: OT: xen libvirt issue
Date: Mon, 08 Apr 2013 19:57:33 +0200	[thread overview]
Message-ID: <5916915.BW6Y7MboP6@localhost> (raw)
In-Reply-To: <5162E3EF.80803@suse.com>

Op maandag 8 april 2013 09:36:15 schreef Jim Fehlig:
> AL13N wrote:
> > 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...
> 
> It will certainly help, but I've heard reports there are still problems
> even with that patch.  IIRC, Bamvor has seen a similar segfault using
> git master of libvirt and xen-unstable, although it is a bit harder to
> trigger.
> 
> I think we need to rework the code for handling shutdown events.  The
> current code worked with libxl in Xen 4.1, but has proven to be racy
> with libxl in Xen 4.2.  I plan to work on this, but unfortunately not
> for a few weeks.  I'm busy with another project this week and will be
> traveling the week of April 15.
> 
> > 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).
> 
> FYI, although it is deprecated, the xm/xend toolstack works well with
> Xen 4.2, and the legacy libvirt xen driver is quite stable.  It was the
> first hypervisor driver in libvirt  :).

i'm aware of that, and kudos to you for this...

It's just that xm/xend is deprecated as you say... and xl looks quite nice... 
:-)

  parent reply	other threads:[~2013-04-08 17:57 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
2013-04-08 15:36         ` Jim Fehlig
2013-04-08 17:22           ` Stefano Stabellini
2013-04-08 17:57           ` AL13N [this message]
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=5916915.BW6Y7MboP6@localhost \
    --to=alien@rmail.be \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=bjzhang@suse.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.