From mboxrd@z Thu Jan 1 00:00:00 1970 From: tgh Subject: Re: [PATCH] fix free of event channel in blkfront Date: Fri, 02 Feb 2007 09:42:41 +0800 Message-ID: <45C29711.8030901@ncic.ac.cn> References: <023701c73385$dbfd0e50$dab2220a@VF03007L><071e01c733b6$0845e010$dab2220a@VF03007L> <45C156EC.7020400@ncic.ac.cn> <198201c745b8$a2062840$dab2220a@VF03007L> <45C19AD0.2010608@ncic.ac.cn> <1bdf01c745df$d016d7d0$dab2220a@VF03007L> <45C1E998.4000305@ncic.ac.cn> <017601c7465f$abcb18c0$dab2220a@VF03007L> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <017601c7465f$abcb18c0$dab2220a@VF03007L> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Kasai Takanori Cc: xen-devel List-Id: xen-devel@lists.xenproject.org Thank you for your detail reply Now I boot the VM with the conf file ... disk =3D [ 'file:/vm/dom3.img,sda1,w' ] ... and then commit the commands as follows [root@genode012 vmcserver]# xm block-attach dom3=20 file:/vm1/template/tp1.img sda2 w [root@genode012 vmcserver]# xm block-list dom3 Vdev BE handle state evt-ch ring-ref BE-path 2049 0 0 4 6 8 /local/domain/0/backend/vbd/107/2049 2050 0 0 4 8 534 /local/domain/0/backend/vbd/107/2050 [root@genode012 vmcserver]# xm console dom3 [root@office2 ~]# cat /proc/diskstats 1 0 ram0 0 0 0 0 0 0 0 0 0 0 0 1 1 ram1 0 0 0 0 0 0 0 0 0 0 0 1 2 ram2 0 0 0 0 0 0 0 0 0 0 0 1 3 ram3 0 0 0 0 0 0 0 0 0 0 0 1 4 ram4 0 0 0 0 0 0 0 0 0 0 0 1 5 ram5 0 0 0 0 0 0 0 0 0 0 0 1 6 ram6 0 0 0 0 0 0 0 0 0 0 0 1 7 ram7 0 0 0 0 0 0 0 0 0 0 0 1 8 ram8 0 0 0 0 0 0 0 0 0 0 0 1 9 ram9 0 0 0 0 0 0 0 0 0 0 0 1 10 ram10 0 0 0 0 0 0 0 0 0 0 0 1 11 ram11 0 0 0 0 0 0 0 0 0 0 0 1 12 ram12 0 0 0 0 0 0 0 0 0 0 0 1 13 ram13 0 0 0 0 0 0 0 0 0 0 0 1 14 ram14 0 0 0 0 0 0 0 0 0 0 0 1 15 ram15 0 0 0 0 0 0 0 0 0 0 0 8 1 sda1 1837 184 60546 3330 1034 1155 17512 16510 0 2290 19840 9 0 md0 0 0 0 0 0 0 0 0 0 0 0 8 2 sda2 0 0 0 0 0 0 0 0 0 0 0 [root@office2 ~]# df -h Filesystem =E7=80=B9=E5=BD=92=E5=99=BA =E5=AE=B8=E8=8C=AC=E6=95=A4 =E9=8D= =99=EE=88=9C=E6=95=A4 =E5=AE=B8=E8=8C=AC=E6=95=A4% =E9=8E=B8=E5=82=9D=E6=B5= =87=E9=90=90? /dev/sda1 5.8G 4.0G 1.5G 73% / none 128M 0 128M 0% /dev/shm [root@office2 ~]# what do I do wrong? How should I make it ? I am really confused with it Kasai Takanori =E5=86=99=E9=81=93: > Hi, > > >> I boot the VM with a img file and the conf file is as follows >> ... >> disk =3D [ 'file:/vm/dom3.img,sda1,w' ] >> >> and if I want to attach another img file to the VM ,then >> the VM boot img must have many partitions such as sda ,sda1, sda2 when >> the img file is made and >> xm block-attach file:/vm1/template/another.img sda1 w >> then in the VM ,mount the sda1,and access it >> I am not for sure whether I understand your mean >> or do you mean that the another img file with I want to attach to the = VM >> needs have many partitions? > > The boot image when starting has already been allocated to sda1. > (BackDev: file:/vm/dom3.img) > Therefore, it is not possible to attach to sda1 by block-attach command= . > Please do not overlap with FrontEnd device that has already been used. > > It is recognized as follows if there is a partition in the attached fil= e. > # xm block-attach file:/vm1/template/another.img sdb w > > another.img file (BackDev) | GuestOS(FrontDev) > ------------------------------------------------------- > 3 partitions(1,2,3) | sdb, sdb1, sdb2, sdb3 > 1 partitions(1) | sdb, sdb1 > =E2=80=BB 1 -> sdb1, 2 -> sdb2, 3->sdb3 > > It is possible to recognized as follows if there is no partition in=20 > attached file. > # xm block-attach file:/vm1/template/another.img sdb1 w > > Best Regards, > > --=20 > Takanori Kasai > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > >