@wezke That would be great ! Thank you !

@AtaxyaNetwork Thank you. Let me know anyway I can help or test. Im not sure about needing a second disk.

Ping @florent

@olivierlambert haha, i'm watching you)

No worries, always good to have feedback

Ping @thomas-dkmt

All the details are here: https://xcp-ng.org/blog/2025/03/14/the-future-of-xcp-ng-lts/ There's no more than this at the moment

@DustinB Here is the backup job configuration: [image: 1743536286372-0459c49d-0b84-4585-9bb8-e3c79bac771b-image.png] [image: 1743536250474-6c3f31b2-aeb7-4d96-b441-3248af6f27a2-image.png]

Hi, Can you describe exactly the steps you are doing? And from which client (XO UI, CLI, API, xe?)

@olivierlambert @olivierlambert said in Diagnosing frequent crashes on host: Maybe there's a usage that's slightly different since when it was "more solid" and now it's trigger more easily. Is your XCP-ng fully up to date? No; as said originally, I'm still on 8.2.1. I have been concerned about moving to 8.3 because it's a new installation, and I don't want to screw it up, but I'm willing to accept that it's the right thing to do.

@ph7 Thank you. It seems to work like that. I'll wait for this fix.

Note: just do a yarn && yarn build and it will work. The XO 6 build might be broken, but that's not surprising, it could happens.

This is essentially why I said in the other thread that "Self Service and ACLs weren't designed to work together" To keep it simple: Self Service will indeed allow some users to see and use some resources even though they don't have ACLs for them. Then, when they create VMs, it will automatically assign ACLs on the objects under the hood. That's why, even though it's not impossible, most of the time it's not recommended to use them together since you might override ACLs that Self Service assigns automatically. We're actually starting to think of a redesign (or at least improvements) of those 2 features so feedback is very welcome about any use case that you might have that isn't covered by them at the moment. I already took note of the "dynamic" need for resource set objects.

Hi @olympicgreg, this seems to be the intended behaviour. Self Service and ACLs weren't designed to work together, so when you create a VM, you either do it under the Self Service feature or thanks to the ACLs you have. So in your case, the user might have Viewer ACLs on the pool, but since they create the VM using Self Service, they will only be able to see the resources available in the Self Service resource set. Regarding ACLs, "Viewer" is not enough to be able to create a VM on the pool. But if you change it to "Admin", you'll see that the user is now able to create a VM outside of the Self Service feature, simply by selecting the pool. And in that case, they'll be able to see all the pool's networks.

@olivierlambert Happy to hear

Hi, This error comes directly from XAPI (XCP-ng) and not from XO. Sadly, XAPI doesn't give much details…

That's weird, likely unrelated eg peering unstuck after a bit and worked later Anyway, happy it works for you, thanks for the mirror reminder, I will try to prioritize this in the next months

@thomas-wood "Remotes" are for XO backups and SR are for VM Storage. Once you add a SR to a pool it's available to all hosts. Also, all hosts should be able to access the IP of the NFS server before setting that up. I have a video explaining storage in XCP-ng here: https://youtu.be/xTo1F3LUhbE?si=QHYkABgElsEVOj6H

@FMOTrust Hey, I think I also am suffering from the same issue that you do. Could you please verify that you have the same issue as me? https://xcp-ng.org/forum/topic/10687/after-an-update-the-nic-s-has-disappeared-but-still-works-somehow?_=1743438466779 It might be a bug or something wrong with an update?