On Wed, Dec 27, 2006 at 11:56:55AM -0500, Stefan Berger wrote:
> On my system I had quite a few problems when I copied the xm-config.xml
> file to /etc/xen. Probably you should change its contents so it does not
> use Xen-API by default, yet, since for example Fedora core installs don't
> come with a pyhton PAM module - at least I could not find it and many
> others might not have installed the package, either.
The version I've just committed keeps the config settings at their defaults,
yes.
For full authenticated access, you need Python-PAM, yes. As an
alternative, you can now set your Xen-API server up to use no
authentication, with something like this in xend-config.sxp:
(xen-api-server ((127.0.0.1:9363 none)))
This will open TCP port 9363, listening only on the local interface, using no
authentication.
> The patch I sent before was due to me trying to create a VM using the
> Xen_API and the ramdisk not becoming available. So I think there is a need
> for testing the
> raw Xen-API as well. I wrote a basic test case for this and put it into a
> new directory tests/xapi into the xm-test suite.
Certainly, I'd like to see tests that hit the raw API too. It's still a
moving target, of course, but things are starting to settle down a bit,
so comprehensive test suites, either through the Python bindings, or
even the C bindings or the CIM providers would all be good.
Cheers,
Ewan.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home
xen.org, 