Re: [Xen-API] XCP 1.5 BETA BUG

[<admin@xxxxxxxxxxx>]

Why does this solution need to be manually hacked into each XCP node?  Why
can't this issue be properly addressed once and for all in either XenCenter
or by shipping XCP with the equivalent XenServer version override already in
place?  Same question goes for the licensing quirks in XCP.  Why can't these
little quirks be permanently fixed before XCP 1.5 final ships?  There is no
sensible reason to leave these quirks in the code.  They confuse and annoy
new users.

-----Original Message-----
From: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-api-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Todd Deshane
Sent: Wednesday, February 15, 2012 7:14 PM
To: Shawn Henderson
Cc: xen-api@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-API] XCP 1.5 BETA BUG

On Wed, Feb 15, 2012 at 11:54 AM, Shawn Henderson
<shenderson@xxxxxxxxxxxxx> wrote:
> Normally this is fixed by using the xapi_version_override file and
applying
> the free xenserver license.  I have yet to get that to work on 1.5 but I
> noticed that the license server now says 1.4.90 and doesn?t expire now.
>

Some information was posted by a user:
http://wiki.xen.org/wiki/XenCenterXCP#For_those_experimenting_with_XCP_1.5be
ta_.281.4.90.29

Does that help?

Thanks,
Todd

-- 
Todd Deshane
http://www.linkedin.com/in/deshantm
http://blog.xen.org/
http://wiki.xen.org/

_______________________________________________
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