I updated XCP-ng to 8.2.1 yesterday.
I will write if issue not gone.

I updated XCP-ng to 8.2.1 yesterday.
I will write if issue not gone.

Hello! I got some issues with at least one of my XCP-ng.
Version: 8.2.0

~ Once in a month it becomes unavailable or VM's running on it becomes unavailable. Dmesg shows OOM reports.
I see that ovs-vswitchd uses too much memory.

Could you tell me what I need to check?

Hello! We got some issues with VM's creating using Terraform via XenOrchestra.
We prepared some VM Templates with Packer.
Template VM RAM size: 4 GiB

For example we need to deploy a new VM with 8 GiB RAM. We add required property to .tf file: memory_max = 8394967296

This is doc: https://registry.terraform.io/providers/terra-farm/xenorchestra/latest/docs/resources/vm

After successfuly VM creation we saw that VM has dynamically RAM pool settings: memory min 4 GiB, memory Max: 8 GiB

Could you tell us how to set a fixed memory size for VM using terraform and XenOrchestra?

If target VM has same amount RAM as a template we see dynamically RAM pool with 4 GiB min and 4 GiB max settings.
We tried manually set template size (experiment!) to 128 GiB. We thouhgt that terraform will reduce this value to our target value = 8 GiB. But it failed VM got 128 GiB RAM and cannot start (Because our host have 128 GiB total mem and other running VM's).

We saw that dynamically memory feature is deprecated. We wanna know hot to solve this.

Thank you.