--- Begin Message ---
>
> No manual editing needed, just use "qm set" twice with the same
> volume
> ;) Sure, those are most likely quite exotic use cases. If we want to,
> we
> could go ahead an prohibit this for PVE 9. There always is the -args
> escape hatch for people that really need it. Would also avoid cases
> where it's done accidentally, so I'm not opposed to this. We'd need
> to
> document it as a breaking change in the upgrade guide and add a check
> to
> the pve8to9 script.
>>it is very handy for testing multipath ;)
Well, indeed, that can be an usecase. (if you don't use qcow2,
snapshots, cache=writeback, ceph rbd with exclusive lock, .... ;)
>> we could add the "slot" to the input for deriving the node name?
I wait fiona the decision for the node-name :)
(for slot, one way could be to append deviceid (ide0, virtio0,..) in
the encoded nodename)
--- End Message ---
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
