From: Andrew Warfield <andrew.warfield@gmail.com>
To: Michael Alexander <malexand@wu-wien.ac.at>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: xcs not running
Date: Fri, 25 Feb 2005 08:47:54 +0000 [thread overview]
Message-ID: <eacc82a4050225004765a78567@mail.gmail.com> (raw)
In-Reply-To: <200502242203.j1OM3pwD102922@isis.wu-wien.ac.at>
Hi Michael,
take a peek at /var/log/xcs.log and see if there is a more verbose
error message there. Does /usr/sbin/xcs exist on your system? Maybe
there is a conflict on the xcs port on your system...
a.
On Thu, 24 Feb 2005 23:03:50 +0100, Michael Alexander
<malexand@wu-wien.ac.at> wrote:
> I've installed xen on fc3 2 machines using the current fedora development rpms
>
> - xen-2-20050219.i386.rpm
> - kernel-xen0-2.6.10-1.1149_FC4.i686.rpm
> - python 2.4 from source Python-2.4.tar
> - mkinitrd from rpm mkinitrd-4.2.0.3-1.i386.rpm
> - python-twisted from src rpm python-2.4-4.src.rpm
>
> Yet I keep getting a hanging xend with a "xcs not running" message:
>
> # xend start
>
> **********************************************************************
> *** Failed to start the control interface switch.
> **********************************************************************
> Traceback (most recent call last):
> File "/usr/sbin/xend", line 164, in ?
> sys.exit(main())
> File "/usr/sbin/xend", line 141, in main
> raise CheckError("xcs not running")
> __main__.CheckError: xcs not running
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_ide95&alloc_id\x14396&opclick
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
next prev parent reply other threads:[~2005-02-25 8:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AcUavLjYnhFHGoscTKq2l0zbu4gXZg==>
2005-02-24 22:03 ` xcs not running Michael Alexander
2005-02-25 8:47 ` Andrew Warfield [this message]
2005-02-25 9:23 ` Andrew Warfield
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=eacc82a4050225004765a78567@mail.gmail.com \
--to=andrew.warfield@gmail.com \
--cc=andrew.warfield@cl.cam.ac.uk \
--cc=malexand@wu-wien.ac.at \
--cc=xen-devel@lists.sourceforge.net \
/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.