This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
VNC console session limits
This section provides an overview of the controls that limit and manage VNC console sessions for virtual machines (VMs) and the control domain (Dom0) in XenServer.
Background
By default, XenServer does not limit the number of concurrent VNC console sessions per VM or host. In environments with strict access controls, this can create security and operational risks. When session limiting is enabled without a timeout, an active session can remain connected indefinitely. In that case, other administrators cannot access the console if the session limit is set to 1.
Feature overview
This release adds two pool-level settings for VNC console connections.
Connection limiting
- Setting:
pool.limit_console_sessions - Type: boolean
- Default:
false - Behavior: When enabled, only one user can connect to a VM or host console at a time. Additional connection attempts are rejected with an error that identifies the user currently connected.
Idle timeout
- Setting:
pool.vm_console_idle_timeout - Type: seconds
- Default:
0(no timeout) - Behavior: Disconnects idle VM console sessions after the specified number of seconds.
Note:
A separate setting,
host.console_idle_timeout, controls idle timeout for control domain (Dom0) consoles.
Benefits
- Improves security by preventing multiple concurrent VNC console sessions per VM or host.
- Reduces the risk of session takeovers by allowing administrators to enforce single-session access and idle timeouts.
How to enable this feature using the CLI
-
Limit console sessions
xe pool-param-set uuid=<pool-uuid> limit-console-sessions=trueThe default value is false, which means there’s no limitation on concurrent VNC console access.
When enabled, only one user can connect to each VM/host console in the pool at a time. The value can be checked through the following command:
xe pool-param-get uuid=<pool-uuid> param-name=limit-console-sessions -
Console idle timeout
Note:
There is an existing console_idle_timeout introduced in SSH timeout feature which is for dom0/host only.
Reuse this field to set idle timeout for dom0, and in the VNC console session feature, a new field vm_console_idle_timeout is introduced to set idle timeout for domU within a pool.
-
For dom0:
xe pool-param-set uuid=<pool-uuid> console_idle_timeout=<seconds> -
For domU:
xe pool-param-set uuid=<pool-uuid> vm_console_idle_timeout=<seconds>By default, the value is 0 which means no timeout. When setting it to a non-zero value (in second), the idle console sessions will automatically be disconnected after the specified time.
Share
Share
In this article
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.