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

[Xen-users] xm block-attach and qcow image - why does it fail ? second try


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Xu Nakajima <xunakaj@xxxxxxxxx>
  • Date: Tue, 13 Mar 2007 02:13:58 -0700 (PDT)
  • Delivery-date: Tue, 13 Mar 2007 02:13:41 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=eOD5yjjRPcJGmRiPBHCcVrwgrz8hgNt5gKOSUh2Z5PKBKbwXZDAKu+U19O034y/dUz1hC5N+0QDDuBrCmC7SvkzIJ+b6qr2nXNIbi07/x9PIPtYFt69Xvf9zh3Z7sKsRShbZDdLPXbIsbu0Ug+8zy8RZhttUFbUpKF83FA6/osc=;
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hello, 

This is a second post, with a trial which is different
from the first one , in order to  solve my
blcok-attach problem.

I tried the following two actions, according to the
blktap readme:

qcow-create 1000 qcowFile.img 
Creating file size 1048576000
Created cksum: 1813725440
then 
xm block-attach 0 tap:qcow:qcowFile.img /dev/xvda1 w 0

I see in the /var/log/xen/xend.log: 
[2007-03-13 11:03:32 xend 2423] DEBUG (blkif:24)
exception looking up device 
  number for /dev/xvda1: [Errno 2] No such file or
directory: '/dev/xvda1'

Running:
 mount /dev/xvda1 /mnt/disk
mount: special device /dev/xvda1 does not exist
 
ls /dev/xvda*
ls: No match.

houldn't this qcow-create and xm block-attach work ? 
 should I run before "mknod /dev/xvda1"?  which
parameters should I pass? 
 
 Can somebody please try this ? 
 
I hope that this mystery will be solved ! 
Regards,
Xu




 
____________________________________________________________________________________
Never miss an email again!
Yahoo! Toolbar alerts you the instant new Mail arrives.
http://tools.search.yahoo.com/toolbar/features/mail/

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

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