Many, many happy hours have since transpired 
I ended up wiping out the XO vm that was running the process and making a new one. That seems to have fixed it.
With all that said, I got one again last night with backing up the same VM that has caused an issue in the past. I just told the backup to restart so lets see what happens.
FWIW...having the same issue with Server 2025.
Another weird thing I've noticed with Windows Server 2025 on XCP-ng.
The network keeps resetting itself to "Public" (vs domain). This only happens when the VM is a domain controller and it only happens with Server 2025. If you go into the VM's console and disable the NIC and then re-enable it, it returns to a domain network. I've tried the usual trick of change the "Network location awareness" to delayed start but it doesn't help.
@Chemikant784
So with this being patch Tuesday, two updates got installed:
2024-11 Cumulative Update for Microsoft server operating system version 24H2 for x64-based Systems (KB5046617)
2024-11 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Microsoft server operating system version 24H2 for x64 (KB5045934)
For whatever reason, those processes are no longer showing up and I can run things from the scheduler??
If you updated tonight, did yours go away?
@Greg_E
For the heck of it, I set up a new VM with 2025 and made it a domain controller complete with AD DS. It seems to work fine but, like yours, there are thirty something conhost processes running.
I recently upgraded from 8.3 RC2 to 8.3 final. Ever since then I've had a terrible time getting backups...especially delta backups (going to NFS server).
Under tasks in XO (Xen Orchestra, commit ff118), it says "[XO] Exporting content of VDI blahblah-drive3 using NBD (on host1) 34%". I have tried rebooting the XO VM (after disabling teh backup task) as well as those that has VM with the data. The task will not go away. I've tried restarting the toolstack on every host....its still stuck.
If you go to the backup activity, it says interrupted and then "download logs" you get this:
{
"data": {
"mode": "delta",
"reportWhen": "always"
},
"id": "1730477627182",
"jobId": "7863cc0b-601e-440a-8328-1d1ef2a09972",
"jobName": "HOST1-VM1-delta",
"message": "backup",
"scheduleId": "59590d78-6809-4eb8-97fe-ba938a68939e",
"start": 1730477627182,
"status": "interrupted",
"infos": [
{
"data": {
"vms": [
"5e01568d-3fa9-11f8-e293-e576f15d5cdb"
]
},
"message": "vms"
}
],
"tasks": [
{
"data": {
"type": "VM",
"id": "5e01568d-3fa9-11f8-e293-e576f15d5cdb",
"name_label": "HOST1-VM1 (20241014T050050Z)"
},
"id": "1730477630143",
"message": "backup VM",
"start": 1730477630143,
"status": "interrupted",
"tasks": [
{
"id": "1730477630162",
"message": "clean-vm",
"start": 1730477630162,
"status": "success",
"end": 1730477630497,
"result": {
"merge": false
}
},
{
"id": "1730477630164",
"message": "clean-vm",
"start": 1730477630164,
"status": "success",
"end": 1730477630537,
"result": {
"merge": false
}
},
{
"id": "1730477631151",
"message": "snapshot",
"start": 1730477631151,
"status": "success",
"end": 1730477648388,
"result": "e252e0e8-7c26-cd1c-3365-e519829f41e3"
},
{
"data": {
"id": "0d6da7ba-fde1-4b37-927b-b56c61ce8e59",
"isFull": true,
"type": "remote"
},
"id": "1730477648389",
"message": "export",
"start": 1730477648389,
"status": "interrupted",
"tasks": [
{
"id": "1730477651581",
"message": "transfer",
"start": 1730477651581,
"status": "interrupted"
}
]
},
{
"data": {
"id": "656f82d9-5d68-4e26-a75d-b57b4cb17d5e",
"isFull": true,
"type": "remote"
},
"id": "1730477648390",
"message": "export",
"start": 1730477648390,
"status": "interrupted",
"tasks": [
{
"id": "1730477651599",
"message": "transfer",
"start": 1730477651599,
"status": "interrupted"
}
]
}
],
"infos": [
{
"message": "Transfer data using NBD"
}
]
}
]
}
That happens to me about once every six weeks on one of the XO installs. For what its worth, if I just kill the XO vm and let it reboot, as long as its not out of disk space, it always works the second time.
@stormi
Just rebooted the problematic host. All the VMs autostarted just fine.
Odd!
@stormi
Yes
I've not had a chance to reboot the host since then to see if something else is going on. Will do so tonight.
@stormi
FWIW...one of the boxes where I installed the latest updates (from a few days ago) did not autostart any of the VMs. I had to manually start each of them.
A week or two ago a bunch of updates went out. Were these part of RC2? I updated via yum back then and since this announcement nothing new has come up.
Is there a command line command to run to verify what is installed now is RC2?
I got the same thing two night's ago.
"timeout while getting the remote 0d2da3ba-fde1-blah-blah-blah"
I rebooted teh NFS server and everything worked fine last night.
In the FWIW department, I've now done four sites. Network thing I mentioned above took about an hour to figure out and was a bit confusing. Once I did one (and made a little cheat sheet on how I did it), the rest of the sites were easy.
Arch
@archw
Ignore that entire post...user error. I have two networks that are spelled very close to the same thing and I was using the wrong one.
Likely a dumb question:
I decided to see how NDB would affect backups.
As I understand it, you need to do it from teh command and teh command is this:
"xe network-param-add param-name=purpose param-key=nbd uuid=<network-uuid>"
I went to the command line and typed "xe network-list"
The network I use is this one:
uuid ( RO) : xxxxxxxx-yyyyy-88bc-b327-zzzzzzzzzzzz
name-label ( RW): Main Network
name-description ( RW): Active / Active (Balance-SLB)
bridge ( RO): xapi0
I then typed :
"xe network-param-add param-name=purpose param-key=nbd uuid=xxxxxxxx-yyyyy-88bc-b327-zzzzzzzzzzzz"
It accepted it without error.
If I run "xe network-list params=all" is see the field :
" purpose (SRW): nbd"
for the network above.
The only issue is that the "NBD" field does not appear in the XO screen (Master, commit f9220) for the network does not populate.
Thoughts ?
Thanks!
11 hosts and thirty something VMs (windows, linux, bsd mix) and update went fine.
I found them here:
https://pvupdates.vmd.citrix.com/
I thought installed them with all the update options. I just removed them and reinstalled with all teh options and they now show up!
Thanks!
Any updates coming for 8.3.? It seems like 8.2 had a slew come out last weekish. No biggie...all is well....just curious.
In the words of Ronald Reagan "I don't recall the answer to that question"
If I remember correctly (subject to the after effects of many happy hours since 5-12-24), I ended up rebooting the host that had that VM. It has never done it since.
Arch