starred/webvirtmgr
1
0
Fork 0
mirror of https://github.com/retspen/webvirtmgr.git synced 2026-04-25 15:45:51 +03:00
Code Issues 209 Projects Releases 7 Packages Wiki Activity

[GH-ISSUE #287] Renaming VM in virt-manager may break VNC #227

New issue
Closed
opened 2026-02-27 16:38:29 +03:00 by kerem · 2 comments
kerem commented 2026-02-27 16:38:29 +03:00
Owner
Copy link

Originally created by @devfaz on GitHub (Apr 20, 2014).
Original GitHub issue: https://github.com/retspen/webvirtmgr/issues/287

Looks like renaming a VM in virt-manager may break VNC in webvirtmgr. I had a VM "debianwheezy" and renamed this VM to "webvirtmgr" in virt-manager. I didn't test VNC before, but here are the steps I did to get a working noVNC:

root@webvirtmgr:/var/log# /var/www/webvirtmgr/console/webvirtmgr-novnc
WebSocket server settings:
  - Listen on 0.0.0.0:6080
  - Flash security policy server
  - SSL/TLS support
  - proxying from 0.0.0.0:6080 to ignore:ignore

  1: 31.16.228.150: Plain non-SSL (ws://) WebSocket connection
  1: 31.16.228.150: Version hybi-13, base64: 'False'
WARNING:root:No local_settings file found.
  1: connecting to: None:None
  1: handler exception: Connect mode requires a port


sqlite> select * from instance_instance;
1|1|debianwheezy|7c9be911-ccb6-4aa0-a951-b45bf80b64c5
2|1|webvirtmgr|7c9be911-ccb6-4aa0-a951-b45bf80b64c5

so I just stopped webvirtmgr and cleared the instance_instance-.table:

sqlite> delete from instance_instance;

started webvirtmgr was able to connect to VNC.

root@webvirtmgr:/var/log# /var/www/webvirtmgr/console/webvirtmgr-novnc
WebSocket server settings:
  - Listen on 0.0.0.0:6080
  - Flash security policy server
  - SSL/TLS support
  - proxying from 0.0.0.0:6080 to ignore:ignore

  1: 31.16.228.150: ignoring socket not ready
  2: 31.16.228.150: ignoring socket not ready
  3: 31.16.228.150: Plain non-SSL (ws://) WebSocket connection
  3: 31.16.228.150: Version hybi-13, base64: 'False'
WARNING:root:No local_settings file found.
  3: connecting to: 192.168.120.1:5900

sqlite> select * from instance_instance;
1|1|webvirtmgr|7c9be911-ccb6-4aa0-a951-b45bf80b64c5

Maybe there is some logic missing to detect renames?

Nevertheless, thanks a lot for this great software!

Originally created by @devfaz on GitHub (Apr 20, 2014). Original GitHub issue: https://github.com/retspen/webvirtmgr/issues/287 Looks like renaming a VM in virt-manager may break VNC in webvirtmgr. I had a VM "debianwheezy" and renamed this VM to "webvirtmgr" in virt-manager. I didn't test VNC before, but here are the steps I did to get a working noVNC: ``` root@webvirtmgr:/var/log# /var/www/webvirtmgr/console/webvirtmgr-novnc WebSocket server settings: - Listen on 0.0.0.0:6080 - Flash security policy server - SSL/TLS support - proxying from 0.0.0.0:6080 to ignore:ignore 1: 31.16.228.150: Plain non-SSL (ws://) WebSocket connection 1: 31.16.228.150: Version hybi-13, base64: 'False' WARNING:root:No local_settings file found. 1: connecting to: None:None 1: handler exception: Connect mode requires a port sqlite> select * from instance_instance; 1|1|debianwheezy|7c9be911-ccb6-4aa0-a951-b45bf80b64c5 2|1|webvirtmgr|7c9be911-ccb6-4aa0-a951-b45bf80b64c5 ``` so I just stopped webvirtmgr and cleared the instance_instance-.table: ``` sqlite> delete from instance_instance; ``` started webvirtmgr was able to connect to VNC. ``` root@webvirtmgr:/var/log# /var/www/webvirtmgr/console/webvirtmgr-novnc WebSocket server settings: - Listen on 0.0.0.0:6080 - Flash security policy server - SSL/TLS support - proxying from 0.0.0.0:6080 to ignore:ignore 1: 31.16.228.150: ignoring socket not ready 2: 31.16.228.150: ignoring socket not ready 3: 31.16.228.150: Plain non-SSL (ws://) WebSocket connection 3: 31.16.228.150: Version hybi-13, base64: 'False' WARNING:root:No local_settings file found. 3: connecting to: 192.168.120.1:5900 sqlite> select * from instance_instance; 1|1|webvirtmgr|7c9be911-ccb6-4aa0-a951-b45bf80b64c5 ``` Maybe there is some logic missing to detect renames? Nevertheless, thanks a lot for this great software!
kerem closed this issue 2026-02-27 16:38:29 +03:00
kerem commented 2026-02-27 16:38:30 +03:00
Author
Owner
Copy link

@AlexH-HankIT commented on GitHub (Apr 20, 2014):

I have the same problem with live migration. If i move one guest to another host i'm unable to connect via vnc. Same error as above. By the way, thanks for the sql commands, until now i had no idea how to work around this issue.

<!-- gh-comment-id:40904291 --> @AlexH-HankIT commented on GitHub (Apr 20, 2014): I have the same problem with live migration. If i move one guest to another host i'm unable to connect via vnc. Same error as above. By the way, thanks for the sql commands, until now i had no idea how to work around this issue.
kerem commented 2026-02-27 16:38:30 +03:00
Author
Owner
Copy link

@retspen commented on GitHub (Apr 22, 2014):

This fix only for migration.

<!-- gh-comment-id:41022852 --> @retspen commented on GitHub (Apr 22, 2014): This fix only for migration.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
v4.8.9
v4.8.8
4.8.7
v4.1.0
v4.0.1
v3.0.0
v2.3.2
Labels
Clear labels   
bug

   
pull-request

Mirrored from GitHub Pull Request

  
wontfix
No labels
bug
pull-request
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/webvirtmgr#227
No description provided.