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


Re: [Xen-devel] Major BUG in xm restore command

To: Philippe Berthault <Philippe.Berthault@xxxxxxxx>
Subject: Re: [Xen-devel] Major BUG in xm restore command
From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Date: Thu, 6 Apr 2006 15:03:28 +0100
Cc: Xen-Devel <Xen-Devel@xxxxxxxxxxxxxxxxxxx>, Xen-Users <Xen-Users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 06 Apr 2006 07:07:12 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <4434EB70.5040106@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4434EB70.5040106@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Thu, Apr 06, 2006 at 12:20:32PM +0200, Philippe Berthault wrote:

> Xen release 3.0.0
> With 'xm rename' and 'xm restore' commands, it's possible to start several
> domains with the same properties (same config file).
> Example:
> - create a config file named 'A'
> - xm create A
> - xm rename A B
> - xm save B B.save
> - xm create A
> - xm restore B.save
> At this time, there is two domains A and B with the same properties
> (same hard disk, same IP address, etc..).
> The correct behavior would be to reject the "xm restore B.save".

The hotplug scripts should be protecting you from writing to the same disk by
two domains at the same time.  What does your config file look like -- how is
that not happening?


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>