@danp Sweet that worked! Thank you!!
This things pretty kickass, I was just able to duplicate a VM that was rendering heavy CG to a completely different node and had that duplicate VM rendering in less than 5 mins...
Thank you so much for the assistance!
@manilx champion!! That's excellent! Thank you so much!
Hi! LOVE XCP-ng, its been the backbone of my little growing VFX studio.
I have a pool with two identical hosts, each have the same GPUs in the same slots and to the OS the slots have the same ID. Up until this point I have been doing 1 host per pool but decided to try and add more hosts to a pool to take advantage of the pool features. How do I assign a VM to a specific host? I have to manually assign the GPU passthrough so this kind of breaks the "fluidity" of the VM floating between hosts thing. (for example If I assign GPU c1 to a VM and I have two c1's on a pool how do I manage to assign c1 on host 1 and not c1 on host 2?).
Or maybe I'm not assigning GPUs correctly and there's a better way to manage these types of VMs?
@tuxen No GPUs were removed. only 2 were added. The only PCIE item removed was a NIC but I didn't remove it from dom0 or assign it to any VMs, it was just in the system.
@tjkreidl Yes, This node had 12GPUs in it running in a bare metal environment a year ago before being repurposed.
Additionally I noticed that when SSHed into the node and working with the CLI xe commands some of them don't go through:
[16:19 gpuhost05 ~]# xe vm-list
uuid ( RO) : b8e7a3c8-e68e-ac45-2dec-b04b4fc5426b
name-label ( RW): vast-ws14
power-state ( RO): halted
uuid ( RO) : c6b78b22-1153-4622-a5a1-1a0880b2d68f
name-label ( RW): Control domain on host: gpuhost05
power-state ( RO): running
[16:19 gpuhost05 ~]# xe vm-list
uuid ( RO) : b8e7a3c8-e68e-ac45-2dec-b04b4fc5426b
name-label ( RW): vast-ws14
power-state ( RO): halted
uuid ( RO) : c6b78b22-1153-4622-a5a1-1a0880b2d68f
name-label ( RW): Control domain on host: gpuhost05
power-state ( RO): running
[16:19 gpuhost05 ~]# xe vm-list
uuid ( RO) : b8e7a3c8-e68e-ac45-2dec-b04b4fc5426b
name-label ( RW): vast-ws14
power-state ( RO): halted
uuid ( RO) : c6b78b22-1153-4622-a5a1-1a0880b2d68f
name-label ( RW): Control domain on host: gpuhost05
power-state ( RO): running
[16:19 gpuhost05 ~]# xe vm-list
Error: Connection refused (calling connect )
[16:19 gpuhost05 ~]#
I try to start a VM manually:
[16:11 gpuhost05 ~]# xe vm-start uuid=b8e7a3c8-e68e-ac45-2dec-b04b4fc5426b
Lost connection to the server.
[16:12 gpuhost05 ~]# xe vm-start uuid=b8e7a3c8-e68e-ac45-2dec-b04b4fc5426b
Lost connection to the server.
[16:12 gpuhost05 ~]# xe vm-start uuid=b8e7a3c8-e68e-ac45-2dec-b04b4fc5426b
Lost connection to the server.
[16:12 gpuhost05 ~]# xe vm-list
uuid ( RO) : b8e7a3c8-e68e-ac45-2dec-b04b4fc5426b
name-label ( RW): vast-ws14
power-state ( RO): halted
uuid ( RO) : c6b78b22-1153-4622-a5a1-1a0880b2d68f
name-label ( RW): Control domain on host: gpuhost05
power-state ( RO): running
[16:12 gpuhost05 ~]# xe vm-start uuid=b8e7a3c8-e68e-ac45-2dec-b04b4fc5426b
Lost connection to the server.
We just encountered this again.
I added 2 new GPUs to the node and removed 1 (unused) NIC. Nothing else was changed in the system. Just 3 PCIe changes. The already installed and assigned GPUs were not removed or changed at all, full error:
server.enable
{
"id": "565d1ea8-582c-4596-ae1f-d96f95ef2c37"
}
{
"errno": -104,
"code": "ECONNRESET",
"syscall": "write",
"url": "https://10.169.4.124/jsonrpc",
"call": {
"method": "session.login_with_password",
"params": "* obfuscated *"
},
"message": "write ECONNRESET",
"name": "Error",
"stack": "Error: write ECONNRESET
at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:94:16)
at WriteWrap.callbackTrampoline (node:internal/async_hooks:130:17)"
}
I can SSH into the node without issue.
I was looking over this: https://xcp-ng.org/docs/api.html
Tried this:
xe-toolstack-restart
I get this error now:
server.enable
{
"id": "88698db1-9b95-4ca8-b690-98395145f282"
}
{
"errno": -111,
"code": "ECONNREFUSED",
"syscall": "connect",
"address": "10.169.4.124",
"port": 443,
"url": "https://10.169.4.124/jsonrpc",
"call": {
"method": "session.login_with_password",
"params": "* obfuscated *"
},
"message": "connect ECONNREFUSED 10.169.4.124:443",
"name": "Error",
"stack": "Error: connect ECONNREFUSED 10.169.4.124:443
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1300:16)
at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17)"
}
I will try this suggested same version upgrade and report back.
While I was able to solve this issue the first time it popped up for us by returning the GPUs back to the DOM, this issue happened again 2 weeks ago for us and I was unable to get it to work again. We had to re-install the HOST entirely to get it to work. I'm sure this is a user error on our part by missing something. I'd very much like to know the proper workflow to solve this as XCP-ng is our backbone to our entire virtual VFX production suite.
We used this command to push the GPUs back to the DOM
/opt/xensource/libexec/xen-cmdline --delete-dom0 xen-pciback.hide
@olivierlambert It was a pci passthrough issue. A device changed from 83: to 84: for no reason at all... All good now!
Hi we're getting this error via the web interface when we try to reconnect to a host but we can SSH into the node just fine.
server.enable
{
"id": "0e1f7b1c-9cc5-4c31-ae55-32185fcb637d"
}
{
"errno": -104,
"code": "ECONNRESET",
"syscall": "write",
"url": "https://10.169.4.120/jsonrpc",
"call": {
"method": "session.login_with_password",
"params": "* obfuscated *"
},
"message": "write ECONNRESET",
"name": "Error",
"stack": "Error: write ECONNRESET
at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:94:16)
at WriteWrap.callbackTrampoline (node:internal/async_hooks:130:17)"
}
Apologies if this has been asked before I searched for the error number and the econnreset but didn't find anything relevant to this issue.
@danp Sweet that worked! Thank you!!
This things pretty kickass, I was just able to duplicate a VM that was rendering heavy CG to a completely different node and had that duplicate VM rendering in less than 5 mins...
Thank you so much for the assistance!