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-users] Quirky Bug: "cat /dev/urandom"

To: William Schaller <wschalle@xxxxxxxxx>
Subject: Re: [Xen-users] Quirky Bug: "cat /dev/urandom"
From: aq <aquynh@xxxxxxxxx>
Date: Tue, 14 Jun 2005 06:58:05 -0700
Cc: Mark Williamson <mark.williamson@xxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 14 Jun 2005 13:57:18 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ghgr/RJlYf0u+naU0iq4noRSusf/hdZhhobcDP2I61xJckeYIbBmC9O0Ys9WU5nGGU4iEKRJYDZPP8WBDxAOI314l0zWEzHj/183wxzAd64lotJ8jkI9REK3ne0sgZxSC8weXzAqavIQhENWFirk8yIayeiKrugMXRIcZTgQ2jQ=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <435dea56050614053269d465e9@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <435dea5605061314392b16539@xxxxxxxxxxxxxx> <9cde8bff050614024560c9409a@xxxxxxxxxxxxxx> <200506141138.04716.mark.williamson@xxxxxxxxxxxx> <435dea56050614053269d465e9@xxxxxxxxxxxxxx>
Reply-to: aq <aquynh@xxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On 6/14/05, William Schaller <wschalle@xxxxxxxxx> wrote:
> Here's the scenario: I'm using two ssh windows to control the box.
> With one, I start xend, create the domain. With the other, I use xm
> console to log into the domain. Logged into the domain, I exec cat
> /dev/urandom. Predictably, the screen starts to fill with junk. At
> this point, ctrl-c, nor any other method of escaping either cat or
> this console will work. Attempting any command using xm or xend in the
> other window simply hangs until I ctrl-c. Stopping and restarting xend
> has no effect. I can kill the bash process the other window is
> running, but if I reconnect to the console, I get the same garbage
> dumping endlessly.

yes, it is very annoying not be able to even destroy the domain in
this case. i wonder what makes xend so unresponsive, and how to fix

i think ideally, xend should always be able to handle the requests
(from xm), no matter what is happening.


Xen-users mailing list