[Engine-devel] Low Level design for HotPlug/HotUnplug feature

[Livnat Peer]

On 16/01/12 22:10, Ayal Baron wrote:
> 
> 
> ----- Original Message -----
>> Suppose, we unplug and then re-plug a disk, will VDSM expect the disk
>> be
>> in the same device path as before?  More generic, will the unplugging
>> and plugging keep the PCI device path as the same as before?
> 
> No guarantee for that.
> For example, suppose you unplug a disk, plug another disk then re-plug the first one.
> Unplug is just like removing a physical disk from your machine, the disk does not have any property stating what PCI address it had.
> 
> It would be nice though if the address were kept and when plugging, if the address is not taken then use the same one and if taken then remove address and let the system choose where to place it...
> 
> 
ack.

Basically when you unplug the disk the management clears the device
address and the device is left with no address. next time you plug the
device and run the VM the management will learn the new address and
persist it.

Livnat

>>
>> On 2012-1-9 17:21, Michael Kublin wrote:
>>> Hi, the follow link is providing a low level design for
>>> HotPlug/HotUnplug feature :
>>> http://www.ovirt.org/wiki/Features/DetailedHotPlug .
>>>
>>> The feature is simple and design is short
>>>
>>> Regards Michael
>>> _______________________________________________
>>> Engine-devel mailing list
>>> Engine-devel at ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/engine-devel
>>>
>>
>>
>> --
>> Shu Ming<shuming at linux.vnet.ibm.com>
>> IBM China Systems and Technology Laboratory
>>
>>
>> _______________________________________________
>> Engine-devel mailing list
>> Engine-devel at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/engine-devel
>>
> _______________________________________________
> Engine-devel mailing list
> Engine-devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel