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: "aq" <aquynh@xxxxxxxxx>, "William Schaller" <wschalle@xxxxxxxxx>
Subject: RE: [Xen-users] Quirky Bug: "cat /dev/urandom"
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Tue, 14 Jun 2005 15:07:54 +0100
Cc: ian.pratt@xxxxxxxxxxxx, Mark Williamson <mark.williamson@xxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 14 Jun 2005 14:06:58 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcVw6S3oKY6/9OjYQcGMU4KGlCXJOgAABpXA
Thread-topic: [Xen-users] Quirky Bug: "cat /dev/urandom"
> > 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 it.
> i think ideally, xend should always be able to handle the 
> requests (from xm), no matter what is happening.

We need to move the console handling out of xend and into a separate
daemon, making them available as pty's (with controllable user/group
settings). We can then just use ssh wrappers to enable consoles to be
accessed over the network, potentially with an interposed screend. Not
sure how best to handle the pty naming, but this is a problem with the
current tcp port based scheme anyhow.

As soon as the xenbus patch goes in this will be the highest priority
xend work item. 


Xen-users mailing list