Re: [Xen-API] [Xen-devel] [Vote] Proposal: Moving XCP binaries to XenServer.org
On Tue, 2014-02-18 at 19:23 +, Lars Kurth wrote: > Hi all, > > I wanted to propose to move the legacy XCP binaries from > XenProject.org to XenServer.org. With XenServer being fully open > source and XCP basically being a variant of XenServer, it would make a > lot more sense to keep all these binaries with XenServer.org. The fact > that we have XCP and XenServer.org in two different places has led to: > > * fragmentation of the XCP user community > * it is also a constant source of confusion in the user community > > In a nutshell many people don't know whether they should go to > XenServer.org to ask XCP related questions or whether to ask them on > XenProject.org. As a result many questions remain unanswered. Russell > and me spend a lot of our time, pointing people to the right place > and/or cross-posting. As do I, from xen-users@ -> xen-api@xenproject/xs-devel@xenserver. > I was hoping things would get better over time, but they have not > improved. > > When the Xen Project was created, there was no real alternative but to > keep XCP as part of the Xen Project. With XenServer being fully open > source, and being established, there is no reason why we can't clean > up some of the confusion. In my opinion we really should do this. > > This proposal does *not* affect the XAPI project : the XAPI project > would continue to develop the XAPI toolstack as part of the Xen > Project (and deliver source "releases"). In fact, I would also propose > to make the xapi mailing list a developer mailing list. This fits much > better with how the Hypervisor and MirageOS projects are run and > creates an overall cleaner and easier to understand model for the Xen > Project. If xen-api@ becomes a devel focused list then what would be the appropriate place to redirect user requests to? xs-de...@xenserver.org? What about for xapi users who are not based on xenserver? > == Who and how to vote? == > > As this is not an entirely project local decision, I propose that > according to http://xenproject.org/governance.html > - Members of all developer mailing lists (including the user lists) on > Xenproject.org can review the proposal and voice an opinion > - Maintainers of all mature projects and the Xenproject.org community > manager are allowed to vote : these are maintainers of xen-devel and > xen-api > > You would vote by replying "+1" +1 > If you don't care vote "0" > If you object, vote "-1", which must include an alternative proposal > or a detailed explanation of the reasons for the negative vote. > > Please vote by Feb 25th > > Best Regards > Lars > ___ > Xen-devel mailing list > xen-de...@lists.xen.org > http://lists.xen.org/xen-devel ___ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
[Xen-API] (no subject)
Hi , Regards, Shafi, Vembu Technologies. ___ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
[Xen-API] CBT support for XEN ????
HI , Do we have CBT (changed block tracking ) support for Xen Enterprise Edition Servers ? Thanks Regards, Shafi, Vembu Technologies. ___ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
Re: [Xen-API] [Xen-devel] [Vote] Proposal: Moving XCP binaries to XenServer.org
On 19/02/2014 10:41, Ian Campbell wrote: On Tue, 2014-02-18 at 19:23 +, Lars Kurth wrote: Hi all, ... This proposal does *not* affect the XAPI project : the XAPI project would continue to develop the XAPI toolstack as part of the Xen Project (and deliver source "releases"). In fact, I would also propose to make the xapi mailing list a developer mailing list. This fits much better with how the Hypervisor and MirageOS projects are run and creates an overall cleaner and easier to understand model for the Xen Project. If xen-api@ becomes a devel focused list then what would be the appropriate place to redirect user requests to? xs-de...@xenserver.org? What about for xapi users who are not based on xenserver? Good point. This was just a side-topic that is not really part of this proposal. Lars ___ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
Re: [Xen-API] Building XAPI as a 32-bit binary
Hello all I got this to compile by changing the code in lib/xenguest_stubs.c to comply with what is defined in the .h file. The XAPI toolstack contains multiple components like the XAPI daemon, xcp-networkd, xenopsd, etc. In github, I don't see release tags for all the components. For example, if I am based out of 6.2 SP1, then what is the baseline code I should use for the different components so that I can build from source for 6.2SP1 without hitting run time issues. -Ranjeet -Original Message- From: Ranjeet R Sent: Friday, February 14, 2014 1:34 PM To: David Scott; xen-api@lists.xen.org Cc: xs-de...@lists.xenserver.org Subject: RE: [Xen-API] Building XAPI as a 32-bit binary Hi Dave Thanks for the pointers. I have installed a XenServer 6.2SP1 DDK VM and going through with the build. However, when I try to build xenctrl, I get the following compilation errors # lib/xenguest_stubs.c: In function 'get_flags': # lib/xenguest_stubs.c:233: warning: format '%ld' expects type 'long int', but argument 13 has type 'uint64_t' # lib/xenguest_stubs.c: In function 'stub_xc_linux_build_native': # lib/xenguest_stubs.c:374: warning: implicit declaration of function 'xc_dom_loginit' # lib/xenguest_stubs.c:404: warning: implicit declaration of function 'xc_dom_release' # lib/xenguest_stubs.c: In function 'stub_xc_domain_save': # lib/xenguest_stubs.c:606: error: too few arguments to function 'xc_domain_save' # lib/xenguest_stubs.c: In function 'stub_xc_domain_restore': # lib/xenguest_stubs.c:682: error: too few arguments to function 'xc_domain_restore' # Command exited with code 2. Looking into the header files in xen-compat.h, I see that the macro __XEN_LATEST_INTERFACE_VERSION__ is defined as 0x0003020a, however the code in xenctrl expects the version to be __XEN_INTERFACE_VERSION__ >= 0x00040200 so that it will provide the relevant arguments to functions xc_domain_save. Question - I would expect the __XEN_INTERFACE_VERSION__ to be defined as 0x00040200 in 6.2 SP1 DDK VM, but it still has 0x0003020a. I am assuming just modifying the version will not work. How can I get around this issue. Any pointers to help me compile the code is really appreciated. -Ranjeet -Original Message- From: David Scott [mailto:dave.sc...@eu.citrix.com] Sent: Thursday, February 13, 2014 3:56 AM To: xen-api@lists.xen.org Cc: Ranjeet R; xs-de...@lists.xenserver.org Subject: Re: [Xen-API] Building XAPI as a 32-bit binary Hi, [cross-posted to xs-devel] On 10/02/14 18:27, Ranjeet R wrote: > Hello > I am trying to build a 32-bit XAPI in a CentOS 6.3 environment. > However, the xen rpms (like xen-devel) are only available as 64-bit > binaries (like > _http://dev.centos.org/centos/6/xen-c6-RC1/x86_64/RPMS/_) and not > available in 32-bit because of which I am not able to compile the > 32-bit XAPI binaries. I can try to compile Xen 32-bit RPMs from the > SRPMs but I was wondering how a 32-bit RPMs are not available publicly > given that > dom0 is a 32-bit. > Any pointers to building a 32-bit XAPI are really appreciated. I assume you're interested in 32-bit because that's what currently shipping in XenServer -- is that correct? In that case I recommend trying to build xapi inside a XenServer "DDK VM": this should have all the necessary xen RPMs pre-installed. If you base yourself on XenServer 6.2, then try building one of the xapi "clearwater" branches: https://github.com/xapi-project/xen-api/tree/clearwater-sp1-lcm Good luck! Dave ___ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
