[pve-devel] perhaps a bug in QemuConfig.pm?

Dietmar Maurer dietmar at proxmox.com
Tue Jun 6 20:40:03 CEST 2017


> > IMHO, this is simply not suitable for a virtualization storage backend. 
> > And I don't want to limit the functionality of our software only because 
> > there are some outdated storage boxes around.
> 
> Do you mean it is a usual situation that a VM has more than 20 disks
> assigned?

If I understand you correctly, we also need to count unused disk (for 
example snapshot ram disks) here? If so, this is not unusual.

> > 
> > Or what was the suggestion exactly?
> > 
> The suggestion was the following:
> 1) A VM or CT will be limited to have a maximum of 20 disks assigned.
> 2) A VM or CT will be limited to have no more than 4 active snapshots
> at a time.
> 3) One LUN is reserved for snapshot backups of CT's.

I guess you can/should implement such limit inside the storage driver?




More information about the pve-devel mailing list