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/
Home Products Support Community News


Re: [Xen-devel] Domains blocked

To: tcranbrook@xxxxxxxxxxxxx
Subject: Re: [Xen-devel] Domains blocked
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Mon, 27 Sep 2004 15:55:57 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 27 Sep 2004 16:08:51 +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
> Hello,
> 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.
> What is a blocked state and how do I unblock them?

Blocked means 'not runnable - waiting for an I/O event'. So a
quiescent domain will pretty much continuously be blocked, but
incoming network packets, timer events, disc responses, etc. will all
make it runnable again.

The problem here is almost certainly that you have misconfigured the
network for those domains in some way, or are failing to start sshd.

Do you have console output? Either use the '-c' option to 'xm create'
or use 'xm console <VM name>'. Make sure you have 'console=tty0' on
the new domain's kernel command line.

 -- Keir

> ANd if that not the likely cause of the ssh failures, what else should I
> look at?

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

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