From: Tom Wilkie <tw275@cam.ac.uk>
To: "Johnson, Michael" <mjohnson@verisign.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: xen configuration
Date: Fri, 09 Sep 2005 10:05:00 +0100 [thread overview]
Message-ID: <4321503C.6060502@cam.ac.uk> (raw)
In-Reply-To: <A313262806CD3341AC59AB108137FC8F3BC74C@dul1wnexmb01.vcorp.ad.vrsn.com>
Right now, XenSV is in a state of flux, so this will probably all change
soon...
You need to install apache and mod_python, copy the files from /tools/sv
/ in the reopository to somewhere under you web root (typically
/var/www/), and add the following lines to you apache config file:
LoadModule python_module modules/mod_python.so
AddHandler mod_python .psp
PythonHandler mod_python.psp
And optionally:
PythonDebug On
Then it should work if you point you browser at the index.psp page! I
did some work on it about a month ago, but my guess is it will need a
little more to work smootly again.
Cheers
Tom
Johnson, Michael wrote:
> Could you point me to documentation on how to get the xen web interface
> working? The only documentation I've found says start xensv then open
> up a browser. I'm get an exception error "no such file or directory"
> /var/lib/xen/sv. True, it doesn't exist.
>
> Also, I'm looking for more detailed documentation on how to install a
> guest O/S.
>
> thanks,
> Mike
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2005-09-09 9:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 15:58 xen configuration Johnson, Michael
2005-09-09 9:05 ` Tom Wilkie [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-10-07 23:23 Stephen Mack
2014-10-08 8:07 ` Razvan Cojocaru
2014-10-08 13:19 ` Stephen Mack
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4321503C.6060502@cam.ac.uk \
--to=tw275@cam.ac.uk \
--cc=mjohnson@verisign.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.