[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Installing XAPI on Debian Wheezy with Xen 4.2-unstable?

On 6/1/2012 2:40 AM, Ian Campbell wrote:
Questions about XCP and XAPI are best addressed to the xen-api@ list.
I've CCd it for you.

Thank you for writing responding Ian. I know it is best suited in xen-xapi BUT have already asked several questions on the Xen-api list regarding XAPI and only received back a couple responses WHICH didn't really help with all questions.
SO, i asked it here on Xen-users to see if any Xen users have messed around with installing XAPI on Debian and see what their experiences where.

On Thu, 2012-05-31 at 14:47 +0100, cyberhawk001@xxxxxxxxx wrote:
I have not had any luck getting the XAPI to install or even work in
Debian Wheezy 64bit SO figured i ask anyone out there:

1.) Has any Xen user(s) have successfully installed the XAPI Toolstack
on Xen 4.2-unstable and how were you able to do it?
XAPI needs to be built against the specific hypervisor version it is
going to run against. The XAPI packages in Wheezy are built against the
4.1 packages in Wheezy.

Why don't you just use the packaged version of both Xen (i.e. 4.1) and
xcp-xapi from Wheezy, this is sure to bethe quickest way to getting an
XCP system up and running. Unless you have a really strong reason to
build the Xen yourself this is something which is best left to the

In the past xapi has needed actual porting effort when moving between
Xen versions. I don't know if this will be the case for moving 4.1->4.2
but I would suggest that unless you

AHH ok, well the last time i asked if XAPI would work or was compatible with Xen 4.2-unstable, on the list Xen-api, the responses i got back was:

"I don't know, but I hope so If you find out, please let us know. The latest trunk build of xapi should work with xen-unstable, but we haven't released that version of xapi yet, either for XenServer, XCP, or Debian/Ubuntu. "

SO, i was wondering if i couldn't get it to work never the less.... :) AND no one has ever remotely mentioned on the Xen-api list that you have to build XAPI based on what version of Xen it is going to be used with.

PLUS i really like and have gotten used to using the XL toolstack in Xen 4.2-unstable as well as not having to do several file modifications or editing that Xen 4.1.2 seems to always need. Plus, i already have a few DomU config files formatted using the XL toolstack and well since that is going to be the standard coming up soon here, might as well start learning and getting used to the latest tools as some things are different in XM vs XL.

2.) Has anyone been able to compile the XAPI Toolstack from source and
again how to do that?
This I don't know. Have you checked the wiki pages? Also you could just
rebuild the Debian packages in the normal way.

The ONLY Wiki there is about this is http://wiki.xen.org/wiki/Compile_the_XCP_toolstack_from_source AND it is using the xapi-autobuilder.git which again will build the XAPI tools and dependencies AS well as the Xen 4.1 hypgervisor and its dependencies as well. I have already asked about this several times and the only thing i got back was:

"Yes, you can download the xapi source from http://github.com/xen-org/xen-api, check out the debian branch, and build from there. Or you can do apt-get source xen-api, and rebuild it. You might be able to use dpkg to install the binary deb package, without installing dependencies, but I don't know. "

WHICH i have done that, i can download the the Debian Branch of the above git and have even downloaded it using "apt-get source xen-api" BUT the Readme file in there is virtually none existent unlike how it is with Xen, and just simply running "MAKE" doesn't do anything nor compiles; it just gives and error "make: omake: Command not found". Again, these i have asked about on Xen-api list BUT are too much of a NOOB question(s) for anyone to answer so never got anywhere with it yet... :).

Also, just like with Xen you need to have a list of dependency packages installed before you can even compile Xen, WELL such things are virtually not documented at all so pretty tough to even know where to start with that. I know XAPI and Project Kronos is still very new and just being developed, but some  people out there have gotten it to compile and work and etc SO there is a way, i am just too new at this to go poking around some code to figure out how it works and than figure out how to compile or use...hehe

- I had Xen 4.2-unstable installed, removed it and ran sudo apt-get
xcp-xapi, which installs Xen 4.1.2. I was able to boot into Xen, the
XE toolstack i just can't get to load or run, even the XM toolstack
doesn't work either. Following the Wiki guides don't quite help yet.
The /etc/init.d folder only contains xendomains, xen and all of the
xcp-* daemons.

- I would be nice to know how to just remove/uninstall
xen-hypervisor-4.1-amd64, xen-utils-4.1, xen-utils-common, and
xenstore-utils, so than one can install Xen 4.2-unstable instead.
Why do you want to do this? Why not run 4.1 which is what the XCP
packages are built against and what people have been testing in the
context of Wheezy?

- On the flip-side, it would be nice if it was easy to install JUST
the XAPI Toolstack as a standalone package on top of an existing Xen
Dom0... :)
I don't understand this. If you have an existing Xen dom0 can't you just
apt-get install xcp-xapi?

Well, NO you can't. I have already tried this. The XAPI toolstack does not come desperately. If you lets say already have Xen 4.2-unstable running or just installed and than you run "apt-get install xcp-xapi", it installs the xcp-xapi, stunnel, xcp-eliloader, xcp-fe, xcp-networkd, xcp-squeezed, xcp-storage-managers, xcp-v6d, xcp-xe, libxenstore3.0, AND other dependecnies, BUT it will also try to install xen-hypervisor-4.1-amd64, xen-utils-4.1 and any additional dependencies it needs WHICH will fail with errors not able to install and etc. SO, it never gets installed and could not get it all to work.

SO, what i am saying that EVEN if i had my own compiled Xen 4.1.2 installed, the apt-get install xcp-xapi" seems to me has NO way of checking to see if you already have Xen 4.1.2 installed and it won't try to re-download and install it form the repository, let alone check if Xen 4.2-Unstable is installed. HENCE what i was saying is that it would be REALLY nice if the XAPI toolstack came as a standalone package, just like most anything, and installs its own dependencies (as it needs several to make it work) BUT not the hypervisor. I am sure it will eventually get there BUT just find it soo puzzling why the XAPI was packaged specifically to include a hypervisor at every turn.

However, if what you said at the beginning that "XAPI needs to be built against the specific hypervisor version" is how it works, than that would make perfect sense as to why XAPI needs to come with its partnered Xen version. BUT, none of that has every been said or stated on xen-api forum SO again, people there are MOSTLY all XAPI developers and rarely have time to answer simple NOOB questions such as these and focus more on bugs or developer issues.... :). On top of that all of the Project Kronos Wiki pages are pretty outdated and need massive updating which no one as done yet.

Thank you for any input from anyone who has experimented with XAPI
installation on  Debian.
I've not run XAPI on Debian but it seems to me that by trying to use
4.2-unstable you are making life much more difficult for yourself than
it needs to be. Just use the existing packages in Debian and I think
things will go much smoother.

Even if you do have a good reason for running 4.2 I'd suggest following
the guides with 4.1 first so you get a feel for things before striking
off and blazing a new trail to 4.2.


Well thanks again Ian, you are always helpful in answering questions on here or helping out. I guess i will mess with XAPI some more, the last time i installed xcp-xapi from debian repo, it installed and booted to Xen 4.1, but could not get any toolstack to load or work. But, i will try again........ :)
Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.