WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-api

Re: [Xen-API] [XCP] XCP 1.1 and xapi version override

To: Eugene Chupriyanov <e.chupriyanov@xxxxxx>
Subject: Re: [Xen-API] [XCP] XCP 1.1 and xapi version override
From: Sergey Melnik <admin.sa@xxxxxxxxx>
Date: Wed, 13 Jul 2011 17:28:30 +0400
Cc: xen-api@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 13 Jul 2011 06:28:42 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=8D4VAl/EIL6dUWbY3JU6NVT6K8qdIhFriHBYjlXwtso=; b=lJUt1K8ZOQ+O+uAgn1gwxXTR1/ZGNzt7vXqGRCODiOQVR7Avl3lCKcCdqPLUsJ4/6O uW9fIPLJK5JFNVGZgTp4As+/8I0aOst2UNHOf46Jw5r0/ASyWIZgq/5gT+rCLF8sDjTT 5isCPdJAFVxP00ZBX43TDRqjWrD22EDJ7EPoE=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4E1D6E69.7040806@xxxxxx>
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>
References: <4E1C6199.3080306@xxxxxx> <CAMrPLWK1se5B_p3m7YZZ2DnHNZA8qVGFyDGDZre+O9OHKYOF6A@xxxxxxxxxxxxxx> <4E1D6E69.7040806@xxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
Hello, Eugene.
You can fix the version in the same ( '/var/xapi/state.db') file,
right before the expiry date.

Best regards,
Sergey Melnik.

2011/7/13 Eugene Chupriyanov <e.chupriyanov@xxxxxx>:
> 13.07.2011 6:51, Todd Deshane пишет:
>
> Was this a fresh install or an upgrade? For upgrades, there is currently a
> known issue that requires the state.db workaround. You need to first stop
> xapi Then modify /var/xapi/state.db' - search for 'expiry' and replace the
> date with a much later one. For more details see:
> http://xen.markmail.org/search/?q=state.db+%22from%3Ajonathan+ludlam%22#query:state.db%20%22from%3Ajonathan%20ludlam%22+page:1+mid:pepibjrn2r3mztoc+state:results
> If this is fresh install do make sure that you have the latest version of
> XenCenter. Let us know if either of those fix your problem. Thanks, Todd
>
> It was fresh install (I run XCP 1.0 on another server without problems).
> The message you referring to tells how to fix expiry date issue, but I'm
> talking about XAPI version.
>
> In docs for XCP 1.0 we can find following:
>
> XenCenter Compatibility
>
> Although XenCenter in principle works with XCP, the fact that XCP uses a
> different versioning scheme makes XenCenter assume it is working with
> an ancientversion of XAPI. From XCP 1.0 RC3 (build number > 40948) you can
> trick CenCenter by modifying the config
> file /etc/xensource/xapi_version_override which contains a single line
> containing the required version number. The version number to set it to for
> maximum XenCenter compatibility is 5.6.199.
>
> UNfortunately, it doesn't work for XCP 1.1 - XenCenter detects freshly
> installed XCP1.1 as XenServer 1.1.0
>
>
> _______________________________________________
> xen-api mailing list
> xen-api@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/mailman/listinfo/xen-api
>
>

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