Re: [Xen-API] Problem using managed domains

To:	"Dube, Lutz" <Lutz.Dube@xxxxxxxxxxxxxxxxxxx>
Subject:	Re: [Xen-API] Problem using managed domains
From:	Tom Wilkie <tom.wilkie@xxxxxxxxx>
Date:	Fri, 27 Apr 2007 11:06:29 +0100
Cc:	xen-api@xxxxxxxxxxxxxxxxxxx
Delivery-date:	Fri, 27 Apr 2007 03:04:54 -0700
Dkim-signature:	a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:in-reply-to:references:mime-version:content-type:message-id:cc:from:subject:date:to:x-mailer; b=BIIijsdMX4GBvhv3kCqcDGvRER65+OPb9i56DIe7kyNJhunUZTWqTp1oAhaib61Gi6dWbSmlG6F8KuJgVOkCp68/QZlMQLKl4+A+JtNA56IXw/AShAHda7G3xjs+fHIQlQLEYvfRHzqgv6LVY7KBG8h0wXkNF4bl4LpE+KqX9J4=
Domainkey-signature:	a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:in-reply-to:references:mime-version:content-type:message-id:cc:from:subject:date:to:x-mailer; b=cquJT0nhDfYfTgoU3CW7Bborrz3wY6YxXlEPSb+1QF1NIiYeraEQC4H+jVMuSESl4Jt+AEEXn5x+fwm9wt/DhYAT0JJ3A6tmH/CcXyHRPWxdjpv3sB8dN6oMuKtWp8lQigT61cNBXazqPrEQeK43B6SXU5cemLWE5lG1TudkSBM=
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
In-reply-to:	<DE26E293539224499409D3E333E3367F05E55242@xxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References:	<DE26E293539224499409D3E333E3367F05E55242@xxxxxxxxxxxxxxxxxxxx>
Sender:	xen-api-bounces@xxxxxxxxxxxxxxxxxxx

Hi Lutz

I've changed the os.rename call to a shutil.move call to cope with this.

Its in cset 14967, which should be in staging soon.

Cheers

Tom

On 24 Apr 2007, at 14:50, Dube, Lutz wrote:

Hello!
I have a problem using managed domains.
I'm trying to to create a new VM object using the method VM.create. In this case xend should
create a config.sxp file for the new managed domain, but I get an error in xend.log
(s. below). The creation of the VM object itself is OK.
API call:
newvm = xen.VM.create(session,{ 'name_label':'testdom',
                                'memory_static_max' : '10240000',
                                'memory_dynamic_max' : '10240000'})

Resulting error log:
[2007-04-24 13:35:33 24434] DEBUG (XendDomain:728) Creating new managed domain: dube: af845f26-ed19-fab1-c4ff-05a27c41046d
[2007-04-24 13:35:33 24434] ERROR (XendDomain:302) Renaming /tmp/tmp0PfFzy
Traceback (most recent call last):
File "/usr/lib/python2.4/xen/xend/XendDomain.py", line 300, in managed_config_save
    os.rename(fn, self._managed_config_path(dom_uuid))
OSError: [Errno 18] Invalid cross-device link
In my system the default path for managed domains (/var/lib/xend/domains) is used and the
directories /var and /tmp are on different file systems, so the system call os.rename must fail.
My workaround is to set xend-domains-path in xend-config.sxp to a directory on the same file system.
Will this restriction be removed in a later version of xend ?

Cheers
Lutz

_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-api

_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-api