@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?

On it. Thanks

@ScarfAntennae hello, and thanks for the suggestion. I am discussing it with the XO Team to add it to our next features. Have a good day!

All of that makes sense then, thanks a lot for your feedback! Pinging @stormi so we can triage your input

This is not a backup but a replication

@efny I thought it wouldn't but in fact since I have it (almost a year) I had 0 bug. It's a Core i7-1255U.

@Gurve Oh wow that's neat! It works! very cool we can use the same query search from the GUI. Thank you.

@Studmuffn1134 should be available in XO vm, it was atleast for me, I just used the XO installer script from github. I did a quick search with xo cli now xo-cli list-commands | egrep 'host.' in case it looks weird "\." is just to escape the "." which just tells regex I am looking for an actual "." import aiohttp import asyncio from jsonrpc_websocket import Server async def routine(): async with aiohttp.ClientSession() as client: server = Server('ws://[yourXO]/api/', client) await server.ws_connect() # signIn required result = await server.session.signIn(username='[yourXOusername]', password='[yourXOPassword]') # email attribute is working in place of username #hard shutdown VM #result = await server.vm.stop(id='3f32beeb-ab3f-a8ac-087d-fdc7ed061b58', force=(bool(1))) #clean Shutdown VM #result = await server.vm.stop(id='3f32beeb-ab3f-a8ac-087d-fdc7ed061b58', force=(bool(0))) #bypassbackup and bypassevacuate set off by default but include for wholeness of parameters result = await server.host.stop(id=[hostUUID],bypassBackupCheck=(bool(0)),bypassEvacuate=bool(0)) print (result) asyncio.get_event_loop().run_until_complete(routine()) I just built all examples into one, here in the end is the host.stop example also

Ping @lsouai-vates

Ping @stormi so we track this somewhere internally

Ping @lsouai-vates

@nuentes For reference, the “PCI Passthrough” that was referenced involves buying a USB PCI card, and passing the card through. If you need any help getting the script up, just respond here and I’ll do what I can to help. My comments in the script arent immaculate