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 reply
I try to do it under your guide as follows
# xm block-attach dom6 file:/vm1/template/tp.img sdb2 w
[root@genode012 vmcserver]# xm block-list dom1
Vdev BE handle state evt-ch ring-ref BE-path
2049 0 0 4 7 8 /local/domain/0/backend/vbd/102/2049
2050 0 0 4 8 815 /local/domain/0/backend/vbd/102/2050

and xm block-detach can work
but xm console dom1, then there is not the new disk in dom1
what is wrong with it?



that is the log in /var/log/xen/xend.log as follows:
[2007-02-01 14:08:47 xend 6460] DEBUG (DevController:110) DevController:
writing {'backend-id': '0', 'virtual-device': '2050''
, 'device-type': 'disk', 'state': '1', 'backend':
'/local/domain/0/backend/vbd/102/2050'} to /local/domain/102/device/vbd/2055
0.
[2007-02-01 14:08:47 xend 6460] DEBUG (DevController:112) DevController:
writing {'domain': 'dom1', 'frontend': '/local/domaii
n/102/device/vbd/2050', 'dev': 'sda2', 'state': '1', 'params':
'/vm1/template/tp1.img', 'mode': 'w', 'online': '1', 'frontendd
-id': '102', 'type': 'file'} to /local/domain/0/backend/vbd/102/2050.
[2007-02-01 14:08:47 xend 6460] DEBUG (DevController:149) Waiting for 2050.
[2007-02-01 14:08:47 xend 6460] DEBUG (DevController:464)
hotplugStatusCallback /local/domain/0/backend/vbd/102/2050/hotplug--
status.
[2007-02-01 14:08:47 xend 6460] DEBUG (DevController:464)
hotplugStatusCallback /local/domain/0/backend/vbd/102/2050/hotplug--
status.
[2007-02-01 14:08:47 xend 6460] DEBUG (DevController:478)
hotplugStatusCallback 1.


could you give me help
Thanks in advance










Kasai Takanori 写道:
> Hi
>
>> I am using the xen-3.0.3 on paravirtualVM
>> and I try to use xm block-attach dom6 /vm1/tp.img sda2 w
>> It seems to be ok, no error ,
>> but in the dom6 there is no sda2
>> and xm block-detach dom6 2050,it does not work
>> and xm block-list dom6 as follows ,
>
> The block-attach command seems to have failed because your use is wrong.
> # xm block-attach dom6 /vm1/tp.img sda2 w
> ^^^^^^^^^^^
> When backend device is a file, it is necessary to specify file.
> Moreover, when it is a physical device, it is necessary to specify phy.
>
> The example is as follows.
> # xm block-attach dom6 file:/vm1/tp.img sda2 w
> # xm block-attach dom6 phy:/dev/sdb sda2 w
>
> The block-detach command works correctly, if the block-attach command
> succeeds.
>
> 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