Bug 33167 – noVNC disconnects on softreboots

Bug 33167 - noVNC disconnects on softreboots


Summary:	noVNC disconnects on softreboots

Status:	CLOSED WORKSFORME

Product:	UCS
Classification:	Unclassified
Component:	Virtualization - UVMM
Version:	UCS 4.2
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-11-06 18:28 CET by Erik Damrose
Modified:	2023-06-28 10:46 CEST (History)
CC List:	3 users (show)

See Also:	35428
What kind of report is it?:	Bug Report
What type of bug is this?:	4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?:	1: Will affect a very few installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.046
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2014052721004854
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Erik Damrose

2013-11-06 18:28:28 CET

noVNC looses its connection to the instance if the VM reboots. While performing the UVMM product tests this happened in 50% of all cases. Pressing F5 will reconnect the session, but it is annoying nonetheless.

Comment 1 Philipp Hahn

2013-11-06 20:51:27 CET

This is caused by Xen exiting the old qemu-dm and starting a new qemu-dm, even for reboots.
With kvm the process is kept.

Comment 2 Moritz Muehlenhoff

2013-11-07 09:40:27 CET

(In reply to Philipp Hahn from comment #1)
> This is caused by Xen exiting the old qemu-dm and starting a new qemu-dm,
> even for reboots.
> With kvm the process is kept.

And this is unrelated to noVNC, the same happens with krdc as well; the VNC session needs to be restarted for Xen VMs.

Comment 3 Tim Petersen

2014-05-27 12:08:39 CEST

Reported again at 2014052721004854

Comment 4 Tim Petersen

2014-05-27 14:31:37 CEST

It seems that the reconnect via f5 does not always work...the customer reported this. A new search for the machine (in uvmm) will always get the new vnc session.

Comment 5 Philipp Hahn

2017-05-02 17:09:51 CEST

Xen is OoM; with QEMU the connection persists in most cases.
There still are VNC dis-connects when QEMU is restarted, for example on snapshot-revert. <https://github.com/novnc/noVNC/pull/747> should help, so +1 for switching from out very old version to a more recent upstream version (Bug #35428)