Change VM Properties
Select a virtual machine in the Resources pane, and on the General tab, click on the Properties button to view or change the properties of the VM.
On the General Properties tab you can change the VM’s name and description, place it in a folder, and manage its tags.
- To change the VM name, enter a new name in the Name box.
- To change the VM description, enter new text in the Description box.
- To place the VM in a folder or to move it to a different folder, click Change in the Folder box and select a folder. See Using folders for more information about using folders.
- To tag and untag the VM and to create and delete tags, see Using tags.
Custom fields allow you to add information to managed resources to make it easier to search and organize them. See Using custom fields to find out how to assign custom fields to your managed resources.
On the CPU tab, you can adjust the number of virtual CPUs allocated to the VM, set cores-per-socket for the vCPU, and specify the vCPU priority. Note that you should shut down the VM before modifying these settings.
Number of vCPUs (for Windows VMs) : To modify the number of virtual CPUs allocated to the VM, change the number in the Number of vCPUs drop-down list. To ensure you get the best performance out of your VM, the number of vCPUs should not exceed the number of physical CPUs on its host server.
Maximum number of vCPUs (for Linux VMs) : To modify the maximum number of virtual CPUs allocated to the VM, change the number in the Maximum Number of vCPUs drop-down list. To ensure you get the best performance out of your VM, the maximum number of vCPUs should not exceed the number of physical CPUs on its host server.
By default, XenCenter allocates one core per socket for each vCPU. The Topology drop-down list displays valid cores-per-socket combinations. Select an option from the list to modify this setting.
Depending on the number of vCPUs you select, XenCenter displays a list of options where the number of vCPUs will be divisible by the number of cores per socket. For example, if you specify 8 vCPUs for your VM, the number of cores per socket can only be 1, 2, 4, or 8. If you specify 5 vCPUs, the number of cores per socket can only be 1 or 5.
Current number of vCPUs (for Linux VMs) : This drop-down displays the current number of vCPUs allocated to the VM. You can increase the number of vCPUs allocated to the VM even when the VM is running by choosing the required number of vCPUs from the drop-down list. Note : You should shut down the VM to decrease the number of vCPUs allocated to the VM.
vCPU priority for this virtual machine
vCPU priority is the priority given to each of the VM’s vCPUs during host CPU scheduling, relative to all of the other VMs running on the same host server. To adjust the vCPU priority for the VM, move the vCPU slider.
The Citrix Hypervisor templates provide typical VM configurations and set reasonable defaults for the memory, based on the type of guest operating system. You should also take into account the following considerations when deciding how much memory you give to a VM:
- The kinds of applications that will run on the VM.
- Other virtual machines that will be using the same memory resource.
- Applications that will run on the server alongside the virtual machine.
The available boot options on this tab may vary, depending on the guest operating system. For example, on some VMs, you can change the boot order (or boot sequence), or specify additional boot parameters.
- To change the boot order, select an item in the Boot Order list and click Move Up or Move Down.
- To specify additional boot parameters, enter them in the OS Boot parameters box. For example, on a Debian VM, you can enter single to boot the VM in single-user mode.
On this tab you can adjust the start order , start delay interval and HA restart priority for the selected VM.
Specifies the order in which individual VMs will be started up within a vApp or during an HA recovery operation, allowing certain VMs to be started before others. VMs with a start order value of 0 (zero) will be started first, then VMs with a start order value of 1, followed by VMs with a start order value of 2, and so on.
Attempt to start next VM after
This is a delay interval that specifies how long to wait after starting the VM before attempting to start the next group of VMs in the startup sequence, that is, VMs with a lower start order. This applies to VMs within a vApp and to individual VMs during an HA recovery operation.
HA restart priority
In an HA-enabled pool, this specifies which VMs will be restarted automatically in the event of an underlying hardware failure or loss of their host server.
- VMs with an HA restart priority of Restart are guaranteed to be restarted if sufficient resources are available within the pool. They will be restarted before VMs with a Restart if possible priority.
- VMs with an HA restart priority of Restart if possible are not considered when calculating a failure plan, but one attempt to restart them will be made if a server that is running them fails. This restart is attempted after all higher-priority VMs are restarted, and if the attempt to start them fails, then it will not be retried.
- VMs with an HA restart priority of Do not restart will not be restarted automatically.
See VM startup settings for more information about these settings.
On the Alerts tab, you can configure performance alerts for the VM’s CPU usage, network, and disk activity.
For information about configuring alerts, see Configuring performance alerts.
On the Home Server tab of the VM Properties dialog box you can nominate a server which will provide resources for the VM. The VM will be started up on that server if possible; if this is not possible, then an alternate server within the same pool will be selected automatically. See Creating a new VM to find out more about home servers.
Note that in pools with Workload Balancing (WLB) enabled, you cannot set a home server. Instead, XenCenter nominates the best server for the VM by analyzing Citrix Hypervisor resource pool metrics and recommending optimizations. You can decide if you want these recommendations geared towards resource performance or hardware density, and you can fine-tune the weighting of individual resource metrics (CPU, network, memory, and disk) so that the placement recommendations and critical thresholds align with your environment’s needs.
On the VM’s GPU properties tab, you can assign a dedicated graphics processing unit (GPU) or a virtual GPU to a VM, providing direct access to the graphic hardware from the VM. This allows a VM to use the processing power of the GPU, providing better support for high-end 3D professional graphics applications such as CAD/CAM, GIS and Medical Imaging applications.
The GPU type list displays available GPUs and virtual GPU types. Select a virtual GPU type from the list to assign a specific virtual GPU type to the VM. Alternatively, select Pass-through whole GPU to allow a VM to use the full processing power of the GPU.
Note: GPU Virtualization is available for Citrix Hypervisor Premium Edition customers, or those who have access to Citrix Hypervisor through their Citrix Virtual Apps and Desktops entitlement. For more information about licensing, see About Citrix Hypervisor Licensing.
On the VM’s USB properties tab, the right side pane displays the list of USBs attched to the VM. You can attach additional (maximum of 6) USBs to the VM. You can also choose to detach USBs from the VM.
For more information, refer to the Tabs section.
Note: USB Pass-Through is available for Citrix Hypervisor Premium Edition customers.
Advanced Options (Optimization)
On the Advanced Options tab, you can adjust the amount of shadow memory assigned to a hardware-assisted VM. In some specialized application workloads, such as Citrix Virtual Apps, extra shadow memory is required to achieve full performance. This memory is considered to be overhead, and is separate from the normal memory calculations for accounting memory to a VM.
- To optimize performance for VMs running Citrix Virtual Apps, click Optimize for Citrix Virtual Apps.
- To manually adjust the VM’s shadow memory allocation, click Optimize manually and enter a number in the Shadow memory multiplier box.
- To restore the default settings for shadow memory, select the Optimize for general use option.
The Container Management tab allows you to enable the container management functionality for the VM. Select the checkbox to enable container management for the VM. After you have enabled this option, details about container management will be displayed on the VM’s General tab. For more information, see Managing Containers.
Note: You must shut down the VM before making any updates to the cloud-config parameters.
On the Cloud-Config Parameters tab, you can review and modify the configuration parameters you have specified for the VM. For more information about cloud-config parameters, see Cloud-Config Parameters.