All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: John Levon <levon@movementarian.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: purpose of /var/lib/xend/state
Date: Fri, 7 Dec 2007 15:56:45 +0000	[thread overview]
Message-ID: <20071207155645.GQ31006@redhat.com> (raw)
In-Reply-To: <20071207154848.GA15943@totally.trollied.org.uk>

On Fri, Dec 07, 2007 at 03:48:48PM +0000, John Levon wrote:
> 
> What are these XML files actually for? I don't understand why this
> information needs to persist - can somebody explain the reason?
> 
> When these files become corrupted for whatever reason, xend fails to
> start altogether. At the very least, this needs to be made more robust
> (I may work on a patch for this once I understand this stuff better).

Its a serious pain wrt to networking. At startup XenD scans all active
network interfaces and saves a record of them. Next-time you start XenD
it will re-create any that it previously saw.

This is exceedingly bad for interfaces/bridges managed by the distro
init scripts. eg, if I had a bridge configured and then remove its
config, XenD will now happily re-create this bridge itself.  I've got
a patch pending to make XenD leave any externally managed PIFs alone
only touching one it created itself via XenAPI

Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

      parent reply	other threads:[~2007-12-07 15:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-07 15:48 purpose of /var/lib/xend/state John Levon
2007-12-07 15:51 ` John Levon
2007-12-07 15:56 ` Daniel P. Berrange [this message]

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=20071207155645.GQ31006@redhat.com \
    --to=berrange@redhat.com \
    --cc=levon@movementarian.org \
    --cc=xen-devel@lists.xensource.com \
    /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.