WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

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

Attached is one of the qemu-dm-*.log files from an attempt to start a Windows HVM.


-Nick

>>> On Sat, May 10, 2008 at  9:33 AM, "Todd Deshane" <deshantm@xxxxxxxxx> wrote:



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?
 

 

-Nick





This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.

Attachment: qemu-dm-6.log
Description: Binary data

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>