[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: FW: [Xen-users] Problem with Dell Poweredge 1850

  • To: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
  • From: David H <davidh.davidh@xxxxxxxxx>
  • Date: Fri, 27 May 2005 08:55:39 -0700
  • Cc: "Gino LV. Ledesma" <gledesma@xxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 27 May 2005 15:55:01 +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=QdbF9YlAFLxh5gPNc++6LPRLOYIET9Y5oMQt/DCiW+Jaux4RTVkb/rrZXAylO03fD1v0iwAmtGYKiK/T0+EpWuYFcNDhoxFrHUPVqL6CRpBK+wjFi1/LRVyKdMtNhBMksEm0zVhyaDVUZcu8rL2K+RB7Fsa4+uR1TU5GLDA1s4Y=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

> It would be particularly interesting to know what the unstable tree does
> on these systems, as the code is quite different.

I may not have been clear; I have been testing with "unstable".  If I
build unstable with the default configuration and boot dom0 with the
following grub entry I can make dom0 hang using a number of IO
intensive commands.  Tar, cp, mkfs, all can cause the problem and
using scp to copy a large file to another machine will hang the domain
in no time.  Xen still responds on the serial console.

title Xen 2.0.6 / XenLinux 2.6.11
        root (hd0,0)
        kernel /xen.gz dom0_mem=131072 console=com1 watchdog com1=115200,8n1
        module /vmlinuz-2.6.11-xen0 root=/dev/VolGroup00/LogVol00 ro
        module /initrd-xen-2.0.img   

Add "nousb"
module /vmlinuz-2.6.11-xen0 root=/dev/VolGroup00/LogVol00 ro console=tty0 nousb
and the problem goes away.


On 5/27/05, Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx> wrote:
> > After a few day of off and on testing it would appear that
> > adding "nousb" to the 2.6 kernel boot options in the grub
> > config fixes this problem.  I have tested with the last few
> > days of unstable builds without a hang.  I have no idea why
> > this works but, so far it does.  I have not had a chance to
> > test much with 2.0.6 so I can't say for sure if the same
> > holds true there.
> Interesting. This might turn out just to be a differnce in kernel config
> between the xen and native kernels you've tried. It might be interesting
> to compile up a stock native kernel with a config as close as
> possible to the xen0 one, and see if the same problem is exhibited.
> Also, if there are any USB options in the BIOS (e.g. legacy support) it
> might be interesting to know if they have any effect.
> It would be particularly interesting to know what the unstable tree does
> on these systems, as the code is quite different.
> Best,
> Ian

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.