Re: XCP: sr driver question wrt vm-migrate

[yamamoto@valinux.co.jp (YAMAMOTO Takashi)]

hi,

i'll try deferring the attach operation to vdi_activate.
thanks!

YAMAMOTO Takashi

> Yup, vdi activate is the way forward.
> 
> If you advertise VDI_ACTIVATE and VDI_DEACTIVATE in the 'get_driver_info' response, xapi will call the following during the start-migrate-shutdown lifecycle:
> 
> VM start:
> 
> host A: VDI.attach
> host A: VDI.activate
> 
> VM migrate:
> 
> host B: VDI.attach
> 
>   (VM pauses on host A)
> 
> host A: VDI.deactivate
> host B: VDI.activate
> 
>   (VM unpauses on host B)
> 
> host A: VDI.detach
> 
> VM shutdown:
> 
> host B: VDI.deactivate
> host B: VDI.detach
> 
> so the disk is never activated on both hosts at once, but it does still go through a period when it is attached to both hosts at once. So you could, for example, check that the disk *could* be attached on the vdi_attach SMAPI call, and actually attach it properly on the vdi_activate call.
> 
> Hope this helps,
> 
> Jon
> 
> 
> On 7 Jun 2010, at 09:26, YAMAMOTO Takashi wrote:
> 
>> hi,
>> 
>> on vm-migrate, xapi attaches a vdi on the migrate-to host
>> before detaching it on the migrate-from host.
>> unfortunately it doesn't work for our product, which doesn't
>> provide a way to attach a volume to multiple hosts at the same time.
>> is VDI_ACTIVATE something what i can use as a workaround?
>> or any other suggestions?
>> 
>> YAMAMOTO Takashi
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel