From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Daniel P. Berrange" Subject: Re: purpose of /var/lib/xend/state Date: Fri, 7 Dec 2007 15:56:45 +0000 Message-ID: <20071207155645.GQ31006@redhat.com> References: <20071207154848.GA15943@totally.trollied.org.uk> Reply-To: "Daniel P. Berrange" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20071207154848.GA15943@totally.trollied.org.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: John Levon Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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 -=|