The remote console provides direct interaction (mouse/keyboard) with Virtual Machines.

All toolbar options, except the Exit button, work as a toggle, switching between on/open or off/closed.

Example: Clicking theChat button opens the chat window, and clicking the button again closes the chat window. A button is orange when on/open; white when off/closed.

 Scale Remote Console

Scales the console window to fill the screen.

 Toggle Browser Full Screen

Activates/deactivates the browser's full-screen option.

 Change/Eject CD-ROM

Toggles the view of the CD-ROM selection form, where an *.iso file is selected.

 Clipboard

Opens the clipboard window where text can be placed to insert into the Virtual Machine.

 Power

Opens/closes the power buttons window.

 Extra Keys

Opens/closes the extra keys window, which allows simulating keyboard operations to the machine, such as:

 Chat

Opens/closes the chat window where all users that are consoled into the virtual machine can share messages with each other.

Name - Displayable characters only; double quotations not allowed; spaces not allowed as first or last character. VM Name field is changeable after creation.

Enabled - Default is selected. When a VM is disabled, it cannot be powered on.

Description - Allows for storing additional information about the VM. Description can prove very helpful in systems with large numbers of virtual machines and/or high virtual machine turnover.

OS Family - Select the OS type that will be installed/run on this virtual machine. Virtualization flags are used to optimize based on the guest OS type.

⚠️ Performance can be adversely affected if an incorrect OS Family is selected.

OS Description - Provides further documentation area for the VM; intended for additional information about the guest OS (e.g. RC1, SP2, Dev Edition, Enterprise, etc.).

Snapshot Profile - Defines the snapshot schedule for the individual VM. Typically, this field is left blank because VM restores can easily be extracted from system snapshots. However, defining a snapshot profile here provides a way to perform additional, more frequent snapshots, and/or longer snapshot retention, and/or quiesced snapshots of the VM. The selection list includes all Snapshot Profiles currently available.

HA Group - HA Group value is used to define node affinity:

Cluster - Defines the primary-choice cluster (at the time of VM Power On) to be used for the VM compute resources. Options include all clusters to which the user has permissions

Failover cluster - Defines secondary-choice cluster to be used when the primary cluster is unavailable (at the time of VM Power On). Options include all clusters to which the user has permissions.

Preferred node - Select the host node on which the VM will first try to start up. Options include all nodes within the selected cluster.

Cloud-init Datasource - Cloud-init Integration option

Owner User - Allows for assigning a user to the given VM. Assigning Owner User will automatically assign List/Read permissions for the VM to the given user and will auto-delete the VM if the assigned user account is deleted.

RAM - The amount of RAM to allocate to the VM. The UI will allow assigning a VM a higher amount of memory than is actually available. However, if the defined amount of RAM is not available when a Power on command is issued, an error will be thrown and the VM will not start.

Cores - The number of CPU cores to allocate to the VM. Cores can be over-provisioned.

CPU Type - Typically it's recommended to keep the default setting as this will automatically select the CPU type that is optimized for the underlying physical host hardware (at VM creation). A different CPU type can be selected to accommodate legacy operating systems/applications and for allowing porting systems to failover sites where different physical host hardware is employed.

Boot Order - Defines the order in which disk devices are checked for a bootable operating system.

Machine Type - Emulated board architecture.

Allow Hotplug - This allows drives and NICs to be added without restarting the VM. Disable if guest OS or emulated hardware does not support it.

Console Type

Console Password Enabled - If enabled, login is required with the specified username/password for accessing the remote console. Prompts for username and password fields displayed when the Console Password Enabled field is checked.

USB Tablet - When selected, a tablet pointer is emulated rather than a mouse, providing for less overhead and network traffic. For a command-line only VM, with no mouse, this option is unnecessary. For spice VMs that will use the client agent, this option is unnecessary.

Video Card

RTC Base - Sets the time clock for the VM.

UEFI - Selection needed will typically depend on the guest OS to be used on the VM. (selected=UEFI, unselected=BIOS) Modifying this option on an existing VM requires a power cycle of the VM.

Serial Port - When enabled, a virtual serial port is created; used only for guest OS compatibility (e.g. Ubuntu Cloud images require a serial port for installation.)

Boot Delay - (in seconds) - Used to control the timing of booting the VM when the owning node is powered on. For example, a delay can be specified on a web server to allow time for its database server to boot and load first, before the web server VM is powered on.

On Power Loss - Determines the action taken when power is restored to the VM. This can be after a physical power loss or after the node is powered off/on in the UI.

Disable Power Cycle - By default, when a reboot is initiated from the guest OS, the system will perform a complete power cycle (which re-initiates all the VM hardware.) When this option is selected, a guest-OS-initiated reboot will simply reset the guest operating system without a power cycle/hardware reset.

Virtual Machines (VMs) running Windows OS may experience "time shift", where the guest OS will periodically adjust the time to an incorrect value.

This time shift issue stems from a fundamental mismatch between Windows' expectations and modern hypervisor behavior. Specifically, the time shift comes from:

The issue is that Windows expects hardware time to be local time, but modern hypervisors (including KVM/QEMU) provide UTC time. This is caused by the Windows OS, which expects time from the physical motherboard to be in local time (RTC) instead of Coordinated Universal Time (UTC).

KorGrid provides time in UTC, which has become the industry standard as it compensates for Daylight Saving Time (DST) changes. The guest OS will automatically adjust the time when comparing its clock value against an authoritative time source because it assumes the time provided by the hardware is local instead of UTC. This comparison causes periodic discrepancies because the guest OS is unable to adjust the physical node clock to match what it perceives as the correct time.



RTC Base is an individual VM setting that allows administrators to set the time provided to the OS as either Local Time or UTC. The value can be found when editing any VM.

With this configuration setting, administrators can granularly control every machine, though it is important to understand the expected behavior of each option.

Local Time

Setting RTC Base to Local Time will pass the time from the physical nodes to the virtual guest OS. This emulates the legacy behavior that Windows expects. When Windows compares the local time clock against an authoritative time service, Windows will adjust the time within the guest OS based on the time zone defined in the Windows configuration. This can result in unexpected behavior.

Things to consider with local time are:

UTC Time

Setting RTC Base to UTC will pass the time from physical nodes into guest VMs as coordinated universal time. This is the industry standard for modern software applications that handle time.

When using the UTC setting, Windows VMs should be configured to recognize that time is presented as universal. For most Windows operating systems, the adjustment is made in the Windows registry by adding a value to recognize "RealTimeIsUniversal".



The registry fix RealTimeIsUniversal=1 is the most elegant solution because it:

For 64-Bit Operating Systems

After adjusting this setting, administrators will need to completely Power Off the VM and then Power On the VM before the change takes effect.