[pve-devel] update disk config, always rescan all the storage, can we avoid that ?

[Alexandre DERUMIER]

>>What is the advantage compared to 'qm set virtio0 ...'?

I thinked mainly to manage add/remove in a task worker, as some actions can take some time.

(like add/remove disk for some storage, or hot-unplug which need to wait for vm response,...)

As an example, for an rbd storage, if you delete a big file, when you validate the form, it wait some seconds, 
the form is diplayed again but the disk in correctly created and config updated.

Maybe adding a bigger timeout can work, but we can't known how much time it'll take.


----- Mail original ----- 

De: "Dietmar Maurer" <dietmar at proxmox.com> 
À: "Alexandre DERUMIER" <aderumier at odiso.com> 
Cc: pve-devel at pve.proxmox.com 
Envoyé: Mardi 4 Juin 2013 11:22:26 
Objet: RE: [pve-devel] update disk config, always rescan all the storage, can we avoid that ? 

> qm device_add disk virtio0 ... 
> qm device_del nic net0 
> 
> or 
> 
> qm device_add virtio0 ... 
> qm device_del net0 ... 

What is the advantage compared to 'qm set virtio0 ...'?