From mboxrd@z Thu Jan  1 00:00:00 1970
From: Olaf Hering <olaf@aepfle.de>
Subject: xenstore root node change
Date: Thu, 16 Dec 2010 15:02:25 +0100
Message-ID: <20101216140225.GA28320@aepfle.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

On Wed, Dec 15, Olaf Hering wrote:

> Current xen-unstable does not have backend/vbd/1/768/params for some

It seems the root handling in xenstore-read has changed, it does not
operate in node /local/domain/0 anymore.

In 4.0, a 'xenstore-read name' returns 'Domain-0', but in xen-unstable
it gives an error now: 'xenstore-read: couldn't read path name'.

Using the absolute path 'xenstore-read /local/domain/0/name' works.

Was this change intentional? If so, the hotplug scripts need an update.


Olaf