XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. nickdsl
    3. Topics
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 3
    • Posts 6
    • Groups 0

    Topics

    • nickdslN

      ACL security issue with ansible

      Watching Ignoring Scheduled Pinned Locked Moved Infrastructure as Code
      10
      0 Votes
      10 Posts
      309 Views
      olivierlambertO
      @nathanael-h will
    • nickdslN

      High memory usage

      Watching Ignoring Scheduled Pinned Locked Moved Compute
      4
      0 Votes
      4 Posts
      335 Views
      nickdslN
      I updated XCP-ng to 8.2.1 yesterday. I will write if issue not gone.
    • nickdslN

      XenOrchestra with Terraform

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      4
      0 Votes
      4 Posts
      737 Views
      D
      @ddelnano Sorry to drag this up and also no OP, but I'm just looking at how to set a static RAM allocation via terraform too so this would be relevant to me. Here's a snippet of code, it's using a generic Ubuntu 22.04 LTS cloud image template which has 1GB ram by default, in the code I set the memory to 4GB, which works but uses Dynamic rather than static resource "xenorchestra_vm" "bar" { name_label = "TerraformCreatedMe" name_description = "Terraform Managed" template = data.xenorchestra_template.ubuntu22.id memory_max = 4294967296 cpus = 4 destroy_cloud_config_vdi_after_boot = true hvm_boot_firmware = "uefi" From the hypervisor side the VM looks like this: memory-static-max ( RW): 4294967296 memory-dynamic-max ( RW): 4294967296 memory-dynamic-min ( RW): 1073741824 memory-static-min ( RW): 1073741824 So to me it looks like memory_max in terraform changes just memory-static-max and memory-dynamic-max which leaves the VM with dynamic memory control. I want the behaviour to be, when I create a new VM or change the RAM allocation for the VM to have static RAM not dynamic. I hope this is possible.