WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Domains blocked

To: tcranbrook@xxxxxxxxxxxxx
Subject: Re: [Xen-devel] Domains blocked
From: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Date: Mon, 27 Sep 2004 16:15:46 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx, Ian.Pratt@xxxxxxxxxxxx
Delivery-date: Mon, 27 Sep 2004 16:28:07 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Mon, 27 Sep 2004 09:41:36 EDT." <4158f35c.8b2.0@xxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> I have been tinkering with Xen lately.  Very nice, so far.  I have compiled
> the latest tarball on a debian Sarge distro, and have a Dom0 partition
> running OK.  Biggest problem is with starting addional domains.  I've tried
> with several distros on seperate partitions, even a clone of the dom0 file
> tree that seems to run ok.  All new domains are marked as blocked in a xm
> list.  They appear on a ping, but all ssh attemps fail with connection
> refused.  I am assuming that this has something to do with being in a
> blocked state, but I can find no info about this in the docs.

Try firing up a console to the domain, either putting '-c' on the
xm create command line, or connecting with 'xm console
<dom_name>'

You should be able to see the startup messages, and hence deduce
what's wrong. This kind of problem is often due to a duff
/etc/fstab or suchlike.

Ian


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

<Prev in Thread] Current Thread [Next in Thread>