|
|
|
|
|
|
|
|
|
|
xen-api
Re: [Xen-API] XenCenter 6.0 and XCP1.1 RC
Hi,
From my personal experience, XenCenter for 6.x works flawlessly with
XCP 1.1 as long as you fake the XCP version to 5.6.100.
Having a higher version like 5.9 or 6 cause the xencenter to try to
setup the VM.suspend_SR field when you create a VM and
that is not supported by XCP 1.1.
my current setup that works with latest XenCenter:
[root~]# cat /etc/xensource/xapi_version_override
5.6.100
I also stripped PRODUCT_BRAND from the xapi binary.
[root~]# /usr/bin/perl -pi -e 's/XCP/\ \ \ /g' /opt/xensource/bin/xapi
and set BUILD_NUMBER to 0 in /etc/xensource-inventory
BUILD_NUMBER='0'
result:
[root~]# xapi -version
hg_id=
hostname=kiffu-2
date=2011-09-19
PRODUCT_VERSION=5.6.100
PRODUCT_BRAND=
BUILD_NUMBER=0
If you try this, backup your xapi binary first, it's a dirty hack and I
dont want to be
responsible if you break anything :)
Cheers,
Sébastien
On 15.11.2011 18:23, Corey Hemminger wrote:
Thanks. That's exactly what I did. Thought there might be a work around to fix
it. Would think xencenter 6.0 would be backward compatible.
Corey
On Nov 15, 2011, at 7:03 AM, Mike McClurg<mike.mcclurg@xxxxxxxxxx> wrote:
On 09/10/11 18:37, Corey Hemminger wrote:
When trying to create new VM's using xencenter 6.0 the new release I get an
error:
"You tried to call a method that does not exist. The method name that you used is
VM.set_suspend_SR."
I'm using XCP 1.1 RC on a server with local storage for the VMs.
Any ideas how to fix this?
Sorry to leave you hanging for a few days. The problem here is that the
VM.suspend_SR field is new to the API, and isn't present in XCP 1.1. The
version of XenCenter you're using is for XenServer 6.0, which has the
new API field. Here is a mapping of XCP/XenServer version numbers:
XCP | XenServer | Codename
----------------------------------
1.0 | 5.6.1 "FP1" | Cowley
1.1 | 5.6.1 "SP2" | Oxford
1.5* | 6.0.0 | Boston
1.6* | 6.1.0* "SP1" | Tampa*
* Unreleased version; names and numbers may change
(Note to self: this should probably be on the wiki somewhere...)
I think that your best bet is to install the XenCenter that corresponds
to XenServer 5.6.1 SP2 and use that with XCP 1.1. Or you can use
OpenXenManager[1][2], though I admit that it's nowhere near as polished
as XenCenter.
Mike
[1] http://sourceforge.net/projects/openxenmanager/
[2] https://launchpad.net/~mike-mcclurg/+archive/openxenmanager
_______________________________________________
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
|
|
|
|
|