You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My composition needs VMs with 2GB of memory, but the default value is 1GB. I found out that I can set the VM memory using the MEM environment variable, but this is not very reproducible and I'd like to have a more permanent way to set this value.
Is it possible to set it in the composition directly? Or in the setup.toml?
Thanks!
The text was updated successfully, but these errors were encountered:
After some discussion with @augu5te, because VM specific options should not go into the composition, I'll try to add a new node-config option to nxc start to specify the resource of each nodes and the Qemu options to mount the volumes. This file should be generated by an external tool at first.
It includes the memory, and the CPU core, but also the disk setup. For example:
# Will be append to the deployments.json to be use inside the composition to mount the diskdeployments:
volumes-config:
nodes-1:
path: /dev/hda1mount: /var# Will be use by the start command to append options for each nodequemuOpts:
node-1: -drive file=/tmp/disks/diskID1234.qcow -m=2Gnode-2: -drive file=/tmp/disks/diskID4567.qcow -m=2Gserver: -drive file=/tmp/disks/diskID0987.qcow -cpu=3
An external tool should be call to create the disks before the VM starts and remove disks once stopped.
Hi!
My composition needs VMs with 2GB of memory, but the default value is 1GB. I found out that I can set the VM memory using the
MEM
environment variable, but this is not very reproducible and I'd like to have a more permanent way to set this value.Is it possible to set it in the composition directly? Or in the setup.toml?
Thanks!
The text was updated successfully, but these errors were encountered: