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] QLogic Fibre Channel HBA Support

To: Steve Traugott <stevegt@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] QLogic Fibre Channel HBA Support
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Tue, 06 Jul 2004 07:22:51 +0100
Cc: Brian Wolfe <brianw@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 06 Jul 2004 07:24:16 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Mon, 05 Jul 2004 22:06:26 PDT." <20040706050626.GM18863@pathfinder>
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
> On Tue, Jul 06, 2004 at 03:23:47AM +0000, Brian Wolfe wrote:
> > Well, after having to restart another of the domains on that xen
> > server I discovered that the last in the list is the one that would
> > lock up once every 24 hours. (not certain fo the exact timeframe since
> > it locks during the night.)
> > 
> > I've disabled the cron entries that generate high workload to
> > eliminate that as a possible cause. 
> This may do it -- once I told my beta users that high workloads and/or
> lots of entropy use could cause hangs, they started nice'ing and
> --bwlimit'ing their ssh rsyncs, and there hasn't been a hang for a few
> weeks.  No proof whether I was hitting another entropy bug or just
> workload.  (Reminder to lurkers -- I'm running 1.2 with /dev/random
> major,minor set to 1,9 -- same as /dev/urandom.)
> > Next is to try running the virtual server on another xen host that is
> > running an older version of xen and xenolinux, see if that still hangs
> > it.
> I think it should get worse if it changes at all.  Your /dev/random is
> 1,8, right?

If you use /dev/urandom (1,9) then you will never block while reading
entropy. The /only/ time anything can block while extracting entropy is
when a user application reads from /dev/random (1,8).

If you've linked /dev/random -> /dev/urandom then any lockups must be
due to bugs elsewhere. 

 while [ true ] ; do dd if=/dev/urandom of=/dev/null bs=512 count=1024 
2>/dev/null && echo -n "." ; done
 while [ true ] ; do dd if=/dev/random of=/dev/null bs=512 count=1024 
2>/dev/null && echo -n "." ; done

 -- Keir

This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
Xen-devel mailing list