This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-API] [PATCH 1 of 2] CA-36086: interface-reconfigure: only bring dev

To: xen-api@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-API] [PATCH 1 of 2] CA-36086: interface-reconfigure: only bring devices up after they have been correctly renamed
From: Ian Campbell <ian.campbell@xxxxxxxxxx>
Date: Tue, 12 Jan 2010 14:15:10 +0000
Cc: Ian Campbell <ian.campbell@xxxxxxxxxx>
Delivery-date: Tue, 12 Jan 2010 06:15:22 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <patchbomb.1263305709@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
The vswitch backend was bringing up the physical devices in the
preconfigure method which runs before devices have been renamed
etc. This was incorrect since preconfigure is not intended to modify
state. Bring up the physical devices in the configure method instead.

Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx>

Attachment: interface-reconfigure-vswitch-bring-up-after-rename.patch
Description: Text Data

xen-api mailing list
<Prev in Thread] Current Thread [Next in Thread>