My particular setup may be a bit weird but here's a better description. I have my primary pool of servers running at home, and XOA runs there. I have a site-to-site VPN between home and the remote location so I can reach the remote host which is also managed through my XOA instance through the VPN tunnel. I don't need any proxies for this to work because I setup a VPN tunnel and XOA and the remote host have direct IP connectivity.

On the remote host, I have a VM that runs in an isolated network not reachable from home, so I cannot connect directly to the guest with VNC. If I'm connected to my home network I can see this guest through XOA. If however I connect to the VPN service at the remote end (different than the site-to-site tunnel) to get access to normal resources on the remote end and also want to use my test VM it becomes difficult to reach the VM because I can't reach my XOA instance back at home easily.

I'm not sure a proxy would solve this. I followed the instructions to test XO Lite and that looks like it is sort of what I am looking for. When I log into my remote host I can see the dashboard and the list of guests, but I don't see the console for the guests. Is the console supposed to be present or is the plan for it to be exposed in the future? If so, that would solve my problem.

Ah great news then!

@mersper Thank you. I will re-think the setup. Having 256 threads in one VM isn't perhaps possible. I have scheduled a meeting with the software manufacturer to talk about network rendering etc. It might be better to have serveral VMs with pinned CPUs and run render jobs. I'll update on the progress 😃

Yes, this is something I would double check: NIC issue or NIC firmware.

@tsettle Glad to hear this. I had tried getting GNS3 working for a long time but gave up and ran it under ProxMox. Is it still working? Do you mind sharing the guide you used? I have always thought it cool to havae a Xen Orchestra recipe / ansible build.

@tuxen Thank You, looks like it's booting on the selected cpu scaling now.

Looks like the job for a PXE server, like you would do for physical machines.

@Magoo-0
I can't thank you for the help you are giving me I took some data here they are

xl info.txt

@Forza @olivierlambert

I would like to highlight that this does work but there are some performance issues with the iGPU. I it for transcoding plex and it will transcode a 4K to 1080p which is a huge load on baremetal but when I use the passthrough to the same basic Windows install it says hw transcoding. However, there is a performance hit somewhere in the passthrough as I can't do a 4K transcode.

FYI

@mathiashedberg try, with xo/xoa, toggeling autostart off and then on again for 1 of the vm on the new host so xo will also activate the autostart option at the (new) server if it was not already enabled

Yes I had 🙂 Now at least everyone is aware on the more pressing requirements on Windows. Next steps will depends on what we can do with the Xen Project and Citrix (also aware about this).

@Darkbeldin
Seems like the slave still has it registered. When I try to add the slave to XCP-ng Center, it says it's still a part of a pool and I need to connect to that. The master just has no record and can't add the slave back because it's already connected.

Not at all 🙂 It's normal to learn. I hope we answered your questions 🙂

@olivierlambert

We wanted test first since currently vms are on Esxi to move to xcp-ng. If everything goes well we planned to move production by purchasing the pro-support/licenses.

Later when budgeting, management wanted to see and compare prices with different products (as per our requirement).

As per our very small environment concerned we won't get any issues with VMWare if any may be 1 call per year. if any issue VMWare support its per call basis USD 49 an hour.

Also Xcp-ng we won't get issues only issues we will get only when migrating or converting VMs from VMware to xcp-ng.

@olivierlambert thank you for your response.
Here is the /var/log/xensource.log where you can find the error: xensource.log.txt

@GoogleSitemaps

https://github.com/xcp-ng/xcp/issues/565

danielbayley80 created this issue in xcp-ng/xcp open Domain 11 (vcpu#1) crashed on cpu#0: (N5105) #565

I setup a Windows 10 VM, changed the passthrough and installed plex server and it's able to do a hardware transcoding. So it looks like the passthrough of the gpu is working but for some reason debian through a docker isn't seeing it properly.