| Good idea. I'm compiling a new XCP RC now, and will post it later.
The config file is /etc/xensource/xapi_version_override which should contain a single line containing the required version number, and the version number to set it to for maximum XenCenter compatibility is '5.6.199'
Jon On 16 Feb 2011, at 16:58, Adrian Costin wrote: Hi,
Why don’t you move the version in some config file. This should be a simple hack and those who wish to change the version to take advantage of all the features in XenCenter would be able to do it without changing a binary file or recompiling.
It would also make it easier to change back in the future when XenCenter will (hopefully) enable features by other means then version checks. Best regards, Adrian Costin The problems with XenCenter are due to it doing explicit version checks to see whether to enable particular features. We toyed with the idea of internally pretending that XCP had the current XS version to work around this, but it was too gross a hack. It's effectively equivalent to the patch linked to by Tomoiaga (although using a more recent version number). One of the things I'm working on is to try to minimise the places where this version number gets baked in to both XenServer and XCP. I expect that by the release of XCP 1.1 (probably August sometime), XenCenter will be able to use most XCP features. For now, XenCenter kinda works, and if you're willing to do the patch below (or recompile xapi to use a different version number), it'll work better. Don't forget that XenCenter is *not* part of XCP currently, and the team that hack on it have no spare resource to commit to supporting XCP alongside XenServer, so there will not be any guarantees about how well it works. In particular, I suspect that they'll always be checking for licenses, having HA / work load balancing / whatever else dialogs, and various other things that don't make sense for XCP. Regarding using the xs-tools iso from XenServer, there should be no problems there. Hope this clarifies things, On 16 Feb 2011, at 09:54, Lars Seeliger wrote:
Thanks a million, Tomoiaga!
I'm still unable to configure VM Protection Policies but, other than that, I think everything works. Nice! http://www.xensemaking.com/misc/patchxcp.shWill change 1.0 with 5.6 in xapi, just run it on each of your XCP nodes and restart xapi. You will have to install the XenServer drivers in VMs after that, to be able to suspend, migrate a.s.o. To do that, you will need to download the xs-tools.iso from XenServer 5.6fp1 to your XCP nodes and replace the original xs-tools.iso and install the new drivers. Regarding the version change for XCP, that should not be an issue, but I am not sure about the XenServer drivers in XCP VMs. I am playing around with them for some time now and they work ok but an expert should answer if it’s ok to use them for production or not since XenServer and XCP are different products. From: xen-api-bounces@xxxxxxxxxxxxxxxxxxx [mailto: xen-api-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Lars Seeliger Sent: Tuesday, February 15, 2011 10:32 PM To: deshantm@xxxxxxxxxCc: xen-api@xxxxxxxxxxxxxxxxxxxSubject: Re: [Xen-API] Re: [Xen-users] XCP and XenCenter
I appreciate you getting back to me, Todd.
Right now XenCenter integration is severely limited, feature-wise. I sincerely hope improvements are made soon, or a workaround such as that alluded to by Tomoiaga is provided.
Thanks for your time. And for an otherwise incredible product.
On 15 February 2011 21:22, Todd Deshane <deshantm@xxxxxxxxx> wrote:
Hi Lars,
I'm pretty sure the XenCenter compatibility is in the works. We might
not have all the kinks out by 1.0, but Jon should be able to confirm.
Also, I don't see where the IRC logs are stored either. I asked in the
#xen-api channel and will reply back if I hear anything.
We are in the process of documenting differences between XCP and XenServer here:
http://wiki.xensource.com/xenwiki/XCP_Docs
Thanks for the feedback and if I hear any news I'll write back either
directly to you or this thread.
Thanks,
Todd
|
