Dang, same issue with the new IP

Okay, I've double-checked that nothing else is answering the phone on that IP either ssh or browser side.
Aside from that I'm trying a fresh static IP that I KNOW is in the clear. I will let you know if it repros with the new IP.

So I'm convinced that the Host network should be okay as there are roughly 78 virtual machines on this esxi host.
The ssh session getting cut seems consistent with the Console getting cut. I would expect the ssh session to get cut/interrupted in the event of a duplicate IP, that I agree with. The reason I think it is more than that is because I have never seen a VM freeze from the console as a result though. Always I have been able to login on the console and correct/change the IP and restart networking and resume ssh connecting to the VM. In this case though, even send ctrl alt delete to the console has absolutely no impact (which to me makes me think kernel panic).
Are you still thinking that duplicate IP could cause a freeze at this level? (not doubting you just suprised because I personally have't experience that to cause console freeze)

I suppose it is possible but I'm using dhcp, and I would never expect a duplicate IP address to make it unresponsive from the console.

node is at v12.16.1

Re: I cann't type anything in vm console after login xen orchestra web

I want to test out Xen Orchestra in my lab so I installed it from source using this script (https://github.com/ronivay/XenOrchestraInstallerUpdater).
Install appeared to work flawlessly. All extra packages downloaded and installed without issue.

Once XO was up and running though, the VM quickly froze.
Installed from source on Debian 10.3 freshly imaged VM.
I had given it 8 vcpu, 8 GB RAM and 50GB disk, with 1 VMXNET3 nic.
Once the service is reachable at the browser I have just enough time to log in and click around a few times. After that the VM itself doesn't respond, if I am ssh'd in already the connection gets cut, the console becomes unresponsive until I initiate a force reset from the hypervisor. No kernel panic text or explanatory visuals.

forced reboot same issue, different host same issue, different datastore same issue.
Does anybody know what I did wrong?
Thanks in advance!