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

Re: [Xen-users] tap:aio not working...

  • To: "Nick Couchman" <Nick.Couchman@xxxxxxxxx>
  • From: "Todd Deshane" <deshantm@xxxxxxxxx>
  • Date: Sat, 10 May 2008 11:33:08 -0400
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Sat, 10 May 2008 08:33:40 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references; b=QE5nrXIBeFp9VXxnWQ17wPpqBA/aZLwNtK1ZiPMSG8k9KlDdOm2iR3I4OEw+r2L4A5eb2nsEcryOteXkwEAdr7m1WDsVL/LEou/phExGSFkBNNMTfO3Z00UmZOA3MI8ds2SvVar0hkK4JdVncDQhrp4Ao7sSEs6UxcSXfUamrM0=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On Sat, May 10, 2008 at 11:25 AM, Nick Couchman <Nick.Couchman@xxxxxxxxx> wrote:
My SLES10 install also does not have a block-tap script.  I traced this down, though, and this is a standard line in the block script (I think) that just looks for any custom script for a particular device type.  If uses a variable that has the device type and looks for block-$DEVICE just in case there are customer scripts.  Don't think this is the issue.
Not sure about what script is generating that output, but I'll try to track it down.
I have another issue, now, after upgrading to SLES10 SP2 GMC (Beta, just before release) and that's that my Windows HVM domUs hang at boot time, now.  That, and they've changed the OCFS2 version from 1.2.8 to 1.4.0, which means that I have to upgrade ALL Of my servers to get them to see my SAN volume.  -Sigh- how annoying...

What messages do you see in the /var/log/xen/qemu* log file when the domU hangs at boot?

Xen-users mailing list



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