[SOLVED] Possible Bug with VNConsole with Template Clones

[HE_Cole]

Hey Everyone Again!

So i have been working to create a bunch of templates for my people to use when they create a VM in my pve cluster. I seam to have ran into a weird issue though. I follow the normal steps to create a VM and i convert it to a template using the GUI. The templates disks are stored on my Ceph shared storage. I then select in the GUI the template i wish to use for making a new VM then i select Clone. In the dialogue box i pick my name and select full clone and pick the same storage "ceph" as the template. But i pick i different node to spawn the VM on. Promox creates the full vm clone on the selected node "i pick a different one then where the template is" Promox then creates the VM clone on the new node with out issue. Now here is the error when i go to that VM and i select VNC console "after i start it" the VNC console just reloads and reloads. The only way i get vnc to work is to spawn the clone on the server which the templte is on even though every server uses the same ceph storage pool for templates and vms.

Anyone else able to replicate this? Or have a fix it?

The issue makes it so any VM's I full clone from a template to another node makes VNC just disconnect and reconnect over and over.


Thanks

 

[dcsapak]

are you by any chance using serialX for the display? if yes, try to connect with xtermjs instead of novnc, there is a bug where a cross node novnc with serial display does not work properly
this has nothing to do with cloning btw. only to which node you connect in the browser and where the vm is located

 

[HE_Cole]

Hey there dcsapak!

You are very right i am using serialx for the display becuase i was told cloud-int required it. I will try xtermjs. Any news on a patch for this?

 

[dcsapak]

no but i opened a bug right now, so that we do not forget this https://bugzilla.proxmox.com/show_bug.cgi?id=2003