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] xm block-attach from dom0 and exception looking up devic

To: "trilok nuwal" <tc.nuwal@xxxxxxxxx>
Subject: Re: [Xen-users] xm block-attach from dom0 and exception looking up device number for /dev/xvda1 - why ?
From: "Ian Brown" <ianbrn@xxxxxxxxx>
Date: Sun, 15 Apr 2007 15:40:28 +0300
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 15 Apr 2007 05:39:17 -0700
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=cqCVR9A+PNBh3sI9L9CcQqRZ/qSKUqJlReQjyLNSpVbldhULbIhlVwOKVORcugolFp2bfmUVrkZ4YzmQNFcgaApECCuY0PKWOpSxyu1pUz3yc9/GgWtt9QoGloNT5kqVRp/WVxbsQCaFpnbncAhKz1DdjC330J1bSp34GtgtiVo=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=C1X9pRLMYS0mZw0bXGWOcj/Yrn2CLsxu+oWgs1lCMQD9cBEVYBL7OyJNk3HgZqj2yfdra32v/zw9RvZZ0Xa5dG/6dcL6Zdwdrjo7KEmKCfuz9VDCeQC2kZviK/OXbWUSly1xbxXGTe16UQ3K55bbmR3Tar9mAaqRbHm7weeg0ZQ=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <f58fc26d0704130040m2daf7fc0ka42616de2a53acec@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <d0383f90704110251y65a76aecn6d6879f91af723b5@xxxxxxxxxxxxxx> <f58fc26d0704122329p34e5521cu9425941cd0773b97@xxxxxxxxxxxxxx> <d0383f90704130002u1916558cofc4958ccb44d841f@xxxxxxxxxxxxxx> <f58fc26d0704130040m2daf7fc0ka42616de2a53acec@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hello,
Sorry. This does not solve my problem.

I tried:

mknod /dev/xvda  b 202 0
mknod /dev/xvda1 b 202 1
xm block-attach 0 tap:aio:/var/lib/xen/images/guest2/guest2File /dev/xvda1 w 0
no errors in xend.log file (the output of xend.log is in the end)

then:

mount /dev/xvda1 /mnt/xvda1/
gives the following error:
mount: /dev/xvda1 is not a valid block device

and mount fails !

cat /proc/devices | grep 202
gives
202 cpu/msr

is the xvd driver missing here ? what should I do ?

the output of xend.log after xm block-attach 0...:
...
[2007-04-15 15:33:31 xend 3123] DEBUG (DevController:110)
DevController: writing {'backend-id': '0', 'virtual-device': '51713',
'device-type': 'disk', 'state': '1', 'backend':
'/local/domain/0/backend/tap/0/51713'} to
/local/domain/0/device/vbd/51713.
[2007-04-15 15:33:31 xend 3123] DEBUG (DevController:112)
DevController: writing {'domain': 'Domain-0', 'frontend':
'/local/domain/0/device/vbd/51713', 'dev': '/dev/xvda1', 'state': '1',
'params': 'aio:/var/lib/xen/images/guest2/guest2File', 'mode': 'w',
'online': '1', 'frontend-id': '0', 'type': 'tap'} to
/local/domain/0/backend/tap/0/51713.
[2007-04-15 15:33:31 xend 3123] DEBUG (DevController:149) Waiting for 51713.
[2007-04-15 15:33:31 xend 3123] DEBUG (DevController:464)
hotplugStatusCallback
/local/domain/0/backend/tap/0/51713/hotplug-status.
[2007-04-15 15:33:31 xend 3123] DEBUG (DevController:464)
hotplugStatusCallback
/local/domain/0/backend/tap/0/51713/hotplug-status.
[2007-04-15 15:33:31 xend 3123] DEBUG (DevController:478)
hotplugStatusCallback 1.
...
...


Any ideas?
Regards,
Ian


On 4/13/07, trilok nuwal <tc.nuwal@xxxxxxxxx> wrote:


On 4/13/07, Ian Brown <ianbrn@xxxxxxxxx> wrote:
> Hello,
> I want to mounting an image in Dom0 using the blktap driver.
> I of course can access the raw image, but I
>
> There is **exactly** such an example in the blktap readme:

  You can try onething,  create /dev/xvda1 using mknod then try this.


> xm block-attach 0 tap:aio:<FILENAME> /dev/xvda1 w 0
> mount /dev/xvda1 /mnt/disk        <--- don't use loop driver
>
> see
http://lxr.xensource.com/lxr/source/tools/blktap/README
>
> So I don't understand what am I missing so it can work.
>
> Regares,
> Ian
>
> On 4/13/07, trilok nuwal <tc.nuwal@xxxxxxxxx> wrote:
> >
> >
> > On 4/11/07, Ian Brown <ianbrn@xxxxxxxxx> wrote:
> > > 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
> >
> >  I am doubtful if  this works to dom0, this should be used with other
> > domains. Why u need this device in dom0 . Everything is available to
dom0.
> >
> > > 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
> > >
> >
> >
>



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