You have a rather long chain now, but it should coalesce anyway

That would be interesting if a we have a test driver solving this very issue here, but I wouldn't expect too much either Those drivers are as bad as the chips

@JamfoFL said in Xen Orchestra from Sources unreachable after applying XCPng Patch updates: @john.c I am able to PING the VM hosting Orchestra with no issues. How about trace routing the tcp port using tcptraceroute (Linux) or tracetcp (Windows). Can you run this on the IP Address and port used by Xen Orchestra, from both local address (same machine) and another address (remote machine)? Can help to see if there’s an issue in the path to that IP’s TCP Port!

@dinhngtu Thank you so much. If you want me I'll be at the pub.

I did it that way so as to get the old Citrix driver first, and then let it update and watch it reboot. That was my logic anyway. @dinhngtu said in Migrating from XCP-ng Windows guest tools to Citrix: @bberndt Okay, I managed to reproduce your situation. I think it's because the "driver via Windows Update" option was enabled after installing the XS drivers, which caused the drivers to lock onto the non-C000 device and prevent updates from coming in. Normally, XenClean should be able to fix the situation. But if you want to fix things manually, or if things still don't work (C000 is still not active), here's a procedure that should fix the problem: Take a snapshot/backup/etc. Keep a note of static IP addresses (if you have any; there's a chance those will be lost). You can also use our script here: https://github.com/xcp-ng/win-pv-drivers/blob/xcp-ng-9.1/XenDriverUtils/Copy-XenVifSettings.ps1 Reboot in safe mode and disable the non-C000 device. Reboot back to normal mode; it'll ask you to reboot a few more times. The C000 device should now be active and you should be able to get driver updates again. (Optional) You can now enable and manually update the non-C000 device (Browse my computer - Let me pick).

@ronan-a Thanks! I've installed the plugin, and configured it. Now to wait until the next power outage. (or until I get time this weekend to test it and annoy my family)

@flakpyro i try to find a new version but site and search only found 3.3.0. When try to search again in a proxmon forum found the repo xD

@olivierlambert Dang ok. I waited a few minute then clicked the Connect in XOA for that host and it connected. Not sure what to do really.

Great!

@Razor_648 While I was writing my previous message, I have been reminded that there are also issues with LVHDoISCSI SR and CBT, you should disable CBT on your backup job and on all VDI on the SR. It might help with the issue.

@icompit Thank you. It seems that the backup process fails to get the file lock on the backup directory. Have you modified anything on your remote recently? Also, could you tell me if this is happening on all of this job's runs, all of your backup runs, or if it only happened once on this specific backup job execution?

@jivanpal We do not currently have any plans to support elliptic curve keys - this is a very sensitive topic given different governmental security requirements around the world. Note that Let's Encrypt recommends a dual setup for this exact reason: "Our recommendation is to serve a dual-cert config, offering an RSA certificate by default, and a (much smaller) ECDSA certificate to those clients that indicate support." (https://letsencrypt.org/docs/integration-guide/)

I moved this discussion to its own topic, as we need the other one for update candidate testing.

@StephenAOINS This endpoint is not currently present in our REST API swagger, but we do plan to add it to the list of endpoints. We are currently finalizing the migration of existing endpoints, the next step will be adding new ones. We will keep you informed when it is available. Feel free to come back to us if you want to learn more and follow our blog posts. have a good day

@andriy.sultanov After running that command I didn't have anything returned.

@olivierlambert I agree, ping @thomas-dkmt

@gb.123 In XO on the "Advanced" tab for the VM I added the GPU devices by first adding them both as "Attached PCIs" near the bottom of the page. I also disabled the "VGA" option under "Xen Settings" and clicked the "+" next to "GPUs" and added the vGPU type "passthrough () 0x0" which was available on the drop-down list. I don't know if it matters or not, but I also set the "Static Max", "Dynamic Min", and "Dynamic Max" memory limits under "VM limits" to the total RAM size I allocated the VM.

@gb.123 Interesting -- alert the XCP-ng team to take a closer look, if they haven't seen this already.

@olivierlambert Hmm. It may just be easier to do a restore and export. I tried doing a file restore of / but I get a Cannot GET error when trying to download the tgz. I don't see anything in the UI to indicate what the problem is or if it actually created the tgz.