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-devel

Re: [Xen-devel] [PATCH] fix free of event channel in blkfront

Thank you for your detail reply
Now I boot the VM with the conf file
...
disk = [ 'file:/vm/dom3.img,sda1,w' ]
...
and then commit the commands as follows

[root@genode012 vmcserver]# xm block-attach dom3 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 瀹归噺 宸茬敤 鍙敤 宸茬敤% 鎸傝浇鐐?
/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 写道:
Hi,


I boot the VM with a img file and the conf file is as follows
...
disk = [ '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 file.
# 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
※ 1 -> sdb1, 2 -> sdb2, 3->sdb3

It is possible to recognized as follows if there is no partition in attached file.
# xm block-attach file:/vm1/template/another.img sdb1 w

Best Regards,

--
Takanori Kasai



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




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