bwlimit does not work as expected

[supermario87]

Hi all,

I'm trying to do some operations, cloning templates first of all, with bwlimits to simulate slow storage and/or slow network. Under no circumstances these limits are respected, in fact the clone operations go always at full speed.

What I've tried:

clone from API call
clone from gui
clone from cli qm clone

Datacenter limits:

Api call example:

What I've done:
using bwlimit parameter in api calls
using datacenter limits and/or storage limits in api calls
using datacenter limits and/or storage limits in gui
using datacenter limits and/or storage limits in qm clone


System config:

proxmox-ve: 7.0-2 (running kernel: 5.11.22-5-pve)
pve-manager: 7.0-13 (running version: 7.0-13/7aa7e488)
pve-kernel-helper: 7.1-2
pve-kernel-5.11: 7.0-8
pve-kernel-5.11.22-5-pve: 5.11.22-10
pve-kernel-5.11.22-4-pve: 5.11.22-9
pve-kernel-5.11.22-3-pve: 5.11.22-7
pve-kernel-5.11.22-1-pve: 5.11.22-2
ceph-fuse: 15.2.13-pve1
corosync: 3.1.5-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve1
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-10
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-3
libpve-storage-perl: 7.0-12
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.11-1
proxmox-backup-file-restore: 2.0.11-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.3-6
pve-cluster: 7.0-3
pve-container: 4.1-1
pve-docs: 7.0-5
pve-edk2-firmware: 3.20210831-1
pve-firewall: 4.2-4
pve-firmware: 3.3-2
pve-ha-manager: 3.3-1
pve-i18n: 2.5-1
pve-qemu-kvm: 6.0.0-4
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-16
smartmontools: 7.2-1
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.5-pve1

bwlimit: clone=2048,default=2048,migration=2048,move=2048,restore=2048
keyboard: it

dir: local
    path /var/lib/vz
    content rootdir,snippets,images,backup,vztmpl,iso

lvmthin: nvme-lvm
    thinpool nvme-lvm
    vgname nvme-lvm
    bwlimit default=2048
    content images,rootdir
    nodes mynode

lvmthin: ssd-lvm
    thinpool ssd-lvm
    vgname ssd-lvm
    bwlimit default=2048
    content rootdir,images
    nodes mynode

nfs: backup
    export /mnt/###
    path /mnt/pve/backup
    server ###
    content backup
    prune-backups keep-last=3

nfs: iso
    export /mnt/###
    path /mnt/pve/iso
    server ###
    content iso
    prune-backups keep-all=1

nfs: truenas-nfs
    export /mnt/###
    path /mnt/pve/truenas-nfs
    server ###
    bwlimit default=2048
    content rootdir,images
    prune-backups keep-all=1

 

[supermario87]

up

 

[fabian]

the bwlimit is only honored for clones of running VMs at the moment.

 

[caribou]

Is there any chance that bwlimit will be honored for cloning VMs from Templates?

My Proxmox node is equipped with a single SSD as local storage and if I clone a VM from a template, all other VMs experience huge IO issues, basically don´t function anymore for several minutes. This is annoying esp. during heavy testing of VMs. My hope was to use bwlimit to avoid such problems.
If this feature can´t / won´t be implemented, is there another/better approach?
I guess attaching some slow USB flash drive as storage for VM template might be such a solution, is there any better?

 

[fabian]

filed https://bugzilla.proxmox.com/show_bug.cgi?id=4249 for better tracking, this shouldn't be too hard to fix hopefully