Allow multiple simultaneous console viewers for KVM user VMs

Open

#13,869 opened on Aug 12, 2026 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 52/100

Issue type: Feature
Clarity: Mostly clear
Activity status: Active
Tech stack: java
Domain: backend, cloud

Research direction

Start by tracing the existing Console Proxy handling for KVM user VM console requests and the sessionRequiresNewViewer behavior. Verify how the new consoleproxy.kvm.multiple.viewers.enabled setting should affect viewer sessions, while preserving current behavior when disabled and for system VMs or other hypervisors.

Written by the indexing model from the issue text.

Description

component:console-proxy component:kvm type:enhancement

The required feature described as a wish

ISSUE TYPE

Feature Idea

COMPONENT NAME

KVM / Console Proxy

CLOUDSTACK VERSION

Behavior reproduced on 4.22.1.0.
Feature implementation targets current main (4.23.0.0-SNAPSHOT).

CONFIGURATION

KVM user VMs using the standard CloudStack Console Proxy / noVNC console.

OS / ENVIRONMENT

KVM-based CloudStack environment.

SUMMARY

Currently, when two users attempt to access the console of the same KVM user VM,
opening the second console disconnects the first viewer.

The Console Proxy already supports using a unique console session UUID as the
viewer key when sessionRequiresNewViewer is enabled. This capability can be
used to allow multiple simultaneous console viewers for KVM user VMs.

The proposed change adds a global setting:

consoleproxy.kvm.multiple.viewers.enabled

The setting defaults to false to preserve the existing single-viewer behavior.

When enabled, each console request for a KVM user VM receives a unique viewer
session so multiple users can remain connected to the same VM console
simultaneously.

The change is restricted to KVM user VMs and does not alter console behavior for
system VMs or other hypervisors.

STEPS TO REPRODUCE

1. Start a KVM user VM.
2. Log in to CloudStack as User A and open the VM console.
3. Log in separately as User B and open the console of the same VM.
4. Observe User A's console session.

EXPECTED RESULTS

Both users should be able to remain connected to the same VM console when
multiple console viewers are enabled.

ACTUAL RESULTS

Opening the console as User B disconnects the existing console session for
User A.

Dominant language: Java
Stars: 3.1k
Forks: 1.4k
Avg merge: 6d 20h
Merged PRs (30d): 27

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

executions.Query — startDate and timeRange filters are sent with inverted comparison operators Open

area/plugin

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

kestra-io/plugin-kestra#190 · Opened Sep 24, 2026
litertlm-android AAR ships no consumer ProGuard rules → "mid == null" SIGABRT in minified apps Open

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

google-ai-edge/LiteRT-LM#3739 · Opened Sep 24, 2026
Add canonical URLs and a sitemap Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

integra-team-red/meet-map#249 · Opened Sep 24, 2026
[Studio][Bug] Cancelled create-user dialog keeps the password and admin switch for the next attempt Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

apache/rocketmq-dashboard#5064 · Opened Sep 24, 2026
Consent portal: creating a duplicate Purpose shows a generic error instead of "already exists" Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

wso2/dpdp-accelerator#287 · Opened Sep 24, 2026

More Java issues