ddelnano
commented
2 years ago @newknowledg I just checked the the VMs I've created with terraform and all of their HVM-shadow-multiplier values are 1.0 so I think there is something else at play here.
[root@localhost ~]# xe vm-list | grep uuid | cut -d ':' -f2 | xargs -I{} xe vm-param-list uuid={} | grep -i hvm-shadow
HVM-shadow-multiplier ( RW): 1.000
HVM-shadow-multiplier ( RW): 1.000
HVM-shadow-multiplier ( RW): 1.000
HVM-shadow-multiplier ( RW): 1.000
HVM-shadow-multiplier ( RW): 1.000
HVM-shadow-multiplier ( RW): 1.000
HVM-shadow-multiplier ( RW): 1.000
HVM-shadow-multiplier ( RW): 1.000
HVM-shadow-multiplier ( RW): 1.000
HVM-shadow-multiplier ( RW): 1.000
HVM-shadow-multiplier ( RW): 1.000
HVM-shadow-multiplier ( RW): 1.000
HVM-shadow-multiplier ( RW): 1.000
HVM-shadow-multiplier ( RW): 1.000The terraform provider isn't specifying that value in the Xen orchestra api calls it makes (although it appears the Xen orchestra code base does allow overriding it).
Can you please provide what hypervisor you are running, the version, the version of Xen orchestra you are using and provide your terraform code.
It would also be helpful if you could provide the terraform provider debug logs so I can see specifically what vm.create api call it's making. Could you create another VM using terraform but make sure to specify the following environment variable when doing so TF_LOG=debug terraform plan and TF_LOG=debug terraform apply. Those logs may contain sensitive information so please give them a look before sharing the contents with me.
newknowledg
I am facing an issue that prevents me from shutting down any vm created using terraform or using terraform to update the vm's it creates.
The problem manifests in the shadow_multiplier. I was provided with a solution to run on the hypervisors shell in order to set this value to one. This will resolve the issue but I would prefer to not have to do this for every new vm I create.
I do not observe this issue when I create vm's manually.