All of lore.kernel.org
 help / color / mirror / Atom feed
From: M A Young <m.a.young@durham.ac.uk>
To: Jim Fehlig <jfehlig@suse.com>
Cc: virt <virt@lists.fedoraproject.org>,
	xen-devel <xen-devel@lists.xen.org>,
	Dario Faggioli <raistlin@linux.it>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Cole Robinson <crobinso@redhat.com>
Subject: Re: libxl and libvirt in Fedora (rawhide)
Date: Tue, 22 Jan 2013 20:19:21 +0000 (GMT)	[thread overview]
Message-ID: <alpine.DEB.2.00.1301221951220.32543__46610.5261737995$1358886122$gmane$org@procyon.dur.ac.uk> (raw)
In-Reply-To: <50FDE388.8080604@suse.com>

On Tue, 22 Jan 2013, Jim Fehlig wrote:

> For those not following in the bug, the libxl driver executes
> '/usr/sbin/xend status' and refuses to load it xend is running.  The
> problem here is that the status check causes xend to start!  I can't
> reproduce the issue, so perhaps it is specific to the fedora packages.

It is specific to the Fedora package. I traced it to the 
xen-initscript.patch file in the Fedora source. From xen-3.1.0-2.fc8 
onwards Fedora xend ignores the option passed to it and just does a start. 
It was from before I started doing things on the package, but idea seems 
to have been to strip out functions like stop, reload etc. and do them 
directly in the init script.

I don't think it is worth changing this much, but I think I will put back 
the status option to keep libvirt happy.

 	Michael Young

  parent reply	other threads:[~2013-01-22 20:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1358419891.16718.146.camel@Abyss>
2013-01-17 16:00 ` libxl and libvirt in Fedora (rawhide) Jim Fehlig
2013-01-18 23:10   ` Dario Faggioli
     [not found]   ` <1358550647.16718.250.camel@Abyss>
2013-01-22  0:55     ` Jim Fehlig
2013-01-22 15:22       ` Dario Faggioli
2013-01-22 20:19       ` M A Young [this message]
     [not found]       ` <alpine.DEB.2.00.1301221951220.32543@procyon.dur.ac.uk>
2013-01-23  8:59         ` Dario Faggioli
2013-01-23 11:19         ` George Dunlap
2013-01-17 10:51 Dario Faggioli

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='alpine.DEB.2.00.1301221951220.32543__46610.5261737995$1358886122$gmane$org@procyon.dur.ac.uk' \
    --to=m.a.young@durham.ac.uk \
    --cc=crobinso@redhat.com \
    --cc=jfehlig@suse.com \
    --cc=konrad.wilk@oracle.com \
    --cc=raistlin@linux.it \
    --cc=virt@lists.fedoraproject.org \
    --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.