Search results

@Dunuin Thank you! It has indeed solved my problem :)

By the looks of things, this is a classic case of RTFM... I misunderstood the "minimum" setting for memory with ballooning enabled, it seems that increasing this should fix my issue.

VM config: agent: 1 balloon: 3000 bios: ovmf boot: cores: 8 cpu: host efidisk0: NVMe-Striped:vm-132-disk-0,efitype=4m,pre-enrolled-keys=1,size=1M machine: q35 memory: 14000 meta: creation-qemu=6.1.0,ctime=1639849428 name: Ceres-02 net0: virtio=B2:7F:D3:43:DD:D0,bridge=vmbr0 net1...

I have this weird issue where all of the VMs that I run, do not get the allocated amount of memory. When rebooting the VM, the correct amount of memory is in fact available in the VM, but after a couple hours, the maximum allowed memory in the VM will be way less. The issue is resolved when I...

I've now managed to increase performance drastically by changing the CPU type from the default kvm64 to "host". This increased my transfer speeds from the mentioned 25MB/s to ~80MB/s. Besides the obvious throughput increase, this also resolved the "unresponsiveness". While doing this transfer...

Hi, I've set up a debian VM with the following config: agent: 1 balloon: 2048 boot: order=scsi0;net0 cores: 8 memory: 16384 name: Docker net0: virtio=16:D0:54:56:5D:02,bridge=vmbr0 net1: virtio=02:75:60:E0:2E:17,bridge=vmbr1 numa: 0 onboot: 1 ostype: l26 scsi0...

Thank you, I will have to rethink this a bit.

That is a bummer but it does make sense, thank you for your reply. That leaves me with the following problem though: Let's say I have setup a backup job, set to backup a bunch of containers/vms. This backup job, writes to a storage that is available to the node I set the job up from. What...

Hi, I have recently gotten into the whole cluster thing, I've got it all worked out, except for backing up to zfs. Previously, when using standalone nodes, I could simply create a storage type "directory" and point the location to a dir on a zfs array. However, now in a cluster, if I allow...