Bug 2087142

Created attachment 1880468 [details]
cirros

Description of problem:
[Machines] The vnc console is wrongly shown for the vm in a vm when visit by "Add new host"

Version-Release number of selected components (if applicable):
cockpit-machines-268-1.el9.noarch
cockpit-269-1.el9.x86_64
libvirt-dbus-1.4.1-5.el9.x86_64
 
How reproducible:
100%

Steps to Reproduce:
1. Reserve a RHEL9 machine from Beaker, and prepare cockpit machines environment. 
   I call it host1 in following steps.
2. On my laptop, visit : http://$host1_ip:9090 
   Enter "Virtual Machines" page, click "Create VM" and create a vm in host1, in my case it's : rhel9-iso 
3. Click the vm "rhel9-iso" once created and run, check the ip of the vm rhel9-iso, it's : 192.168.122.149 in my case
4. Click the “arrow” on top lefter corner on the web console, click "Add new host" 
    Then add the above ip  in step 3 and neccessory info to connect
5. Enter the "Virtual Machines" page, and import a vm like "cirros" , run it
6. Click the vm "cirros" and enter vm details page, check the "VNC console" now
It's wrongly showing the console of rhel9-iso, which should shown the console of cirros.
Please check attached pictures to understand it correctly.
7. Import a second vm like "cirros2", you will find the vnc console is "disconnected"

Actual results:
The VNC console of cirros is the same with rhel9-iso in step 6

Expected results:
In step 6 , it should display the cirros console, not the rhel9-iso
In step7, the vnc console should not be disconnected

Additional info:
If log into rhel9-iso, and visit the web console directly by the browser inside 
 it, the vnc console for cirros and cirros2 all looks good.