The Kronos page: http://wiki.xen.org/wiki/Project_Kronos includes these two entries: A couple of network-related notes + XAPI expects to run in a clean environment, and listens on ports 80 and 443. If you''re running anything else on these ports (typically Apache/Apache2), then you''re likely to have problems. + There is a known bug (which needs to be fixed) which means that in certain circumstances when you are using VPN software (e.g. when you have a tun0 interface listed in ifconfig), xapi will fail. Please ensure that you remove all such software before attempting to run xcp-xapi. Do these mean that Apache and VPN can not be run with Xen or possibly that they can be run from VMs? ray
On Tue, Jul 3, 2012 at 7:17 AM, <ray@aarden.us> wrote:> The Kronos page: > http://wiki.xen.org/wiki/Project_Kronos > includes these two entries: > A couple of network-related notes > + XAPI expects to run in a clean environment, > and listens on ports 80 and 443. If you''re > running anything else on these ports > (typically Apache/Apache2), then you''re > likely to have problems. > + There is a known bug (which needs to be > fixed) which means that in certain > circumstances when you are using VPN > software (e.g. when you have a tun0 > interface listed in ifconfig), xapi > will fail. Please ensure that you remove > all such software before attempting to > run xcp-xapi. > > Do these mean that Apache and VPN can not be run with Xen or possibly > that they can be run from VMs?Those notes should only apply to the system running xapi, which is the dom0. domUs (i.e. VMs) should be unaffected. And also note that it doesn''t specifically blacklist only apache; rather it says that you shouldn''t have anything on dom0 which listens on port 80 and 443. -- Fajar
On Tue, Jul 3, 2012 at 7:17 AM, <ray@aarden.us> wrote:> The Kronos page: > http://wiki.xen.org/wiki/Project_Kronos > includes these two entries: > A couple of network-related notes > + XAPI expects to run in a clean environment, > and listens on ports 80 and 443. If you''re > running anything else on these ports > (typically Apache/Apache2), then you''re > likely to have problems. > + There is a known bug (which needs to be > fixed) which means that in certain > circumstances when you are using VPN > software (e.g. when you have a tun0 > interface listed in ifconfig), xapi > will fail. Please ensure that you remove > all such software before attempting to > run xcp-xapi. > > Do these mean that Apache and VPN can not be run with Xen or possibly > that they can be run from VMs?Those notes should only apply to the system running xapi, which is the dom0. domUs (i.e. VMs) should be unaffected. And also note that it doesn''t specifically blacklist only apache; rather it says that you shouldn''t have anything on dom0 which listens on port 80 and 443. Fajar, Does this mean that one or more domUs can run Apache? Will they be on virtual ports 80 and 443? If so, what is it call where Xen translates ports? Thank you, ray -- Fajar
On Wed, Jul 4, 2012 at 9:17 AM, <ray@aarden.us> wrote:> Fajar, > Does this mean that one or more domUs can run Apache?Yes> Will they be on > virtual ports 80 and 443? If so, what is it call where Xen translates > ports?err ... you need to read more about xen networking. Start with the wiki. In short, with the default setup, domUs will have a DIFFERENT ip from dom0, but within the SAME network due to bridge networking setup. You CAN change that, of course. Again, the wiki should be able to tell you what kinds of networking setup are available for xen. -- Fajar