[Xen-users] xm block-attach from dom0 and exception looking up device number for /dev/xvda1 - why ?

["Ian Brown" <ianbrn@xxxxxxxxx>]

Hello,

I am trying to perform "xm block-attach" from dom0 according to the
Xen blktap README.

What I am trying to do is :

xm block-attach 0 tap:aio:/var/lib/xen/images/guest2/guest2File /dev/xvda1 w 0

whereas "/var/lib/xen/images/guest2/guest2File" is the image which appears
in the domU cofig file:
disk = [ 'tap:aio:/var/lib/xen/images/guest2/guest2File,xvda,w', ...]

I see the following error message in /var/log/xen/xend.log: (of dom0
of course)

[2007-04-11 10:51:24 xend 3123] DEBUG (blkif:24) exception
looking up device number for /dev/xvda1:
[Errno 2] No such file or directory: '/dev/xvda1'

Indeed, ls -al /dev/xvda1 in dom0 gives:
 ls: /dev/xvda1: No such file or directory
and also  running "cat /proc/partitions |grep xvd" from dom0
gives nothing.  
        

I want to add that tring mounting from dom0 onto domU succeeds:
xm block-attach 1 tap:aio:/var/lib/xen/images/guest2/guest2File /dev/xvda1 w
(where 1 is the number of domU).
Also mounting /dev/xvda1 from domU succeeds.

Any idea ? what should I do so that it will succeed ? is this readme
not valid anynmore ??


Ian

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