@ronan-a Any more information about RawISCSISR usage? I can't seem to find any good match on the web.

@olympicgreg Hello! And thanks for your feedback on the ACL subject. I note this on our XO-6 next features, so we will discuss on it and see what we can improve. Indeed the ACL subject is quite not trivial and we keep on working on it. Have a good day and don't hesitate to give us feedbacks on XO features.

@NathanO Hello there! We have a feature on the isPubKeyTooShort spamming on the XO next sprint priority, so to me it should be available on May 2025 XO release. Check at the next blogspots to keep informed. Hope my comment responds to your questions, have a good day!

@Tomcatter yes it was already implemented in XO-Lite [image: 1744189947925-f1dc4d66-3ffc-43cc-baca-56f934901f99-image.png] You can find it from the pool view. (click on a pool on the treeview and then on the VM tab) It is also planned for XO-6, it is in our backlog for next features. Does it respond to your questions?

@lawrencesystems @olivierlambert Thought I'd provide an update here...only fair After getting everything running again, I was able to add 2 physical XCP Hosts to XO and get things going -> create a Pool; create some VMs; test Live Migration (not VDI-based yet); import from VMW (an issue there with Linux); but overall...able to dive into it a bit deeper and see how things in XCP/XO work vs VMW. So far, after getting through my initial issues...I think it's ok I think my Host2 network issue may have stemmed from attempting to add it back into XO when I was no longer seeing it in the Settings > Servers area after adding it to a Pool. I wasn't aware it would disappear from that area when adding it to a Pool. I don't think the documentation states this (unless I overlooked it? if not, would be helpful I think). Anyway...thanks to all for chiming in!

@FMOTrust I had this issue as well on a Slave host in my test environment. I was able to do Network Reset from xsconsole, but then after the Host rebooted to finish the reset, the Host reverted back to not having/seeing the Mgmt network, and...like you, I couldn't see any NICs either. Since this was for testing, and I had no VMs on it, I just reinstalled XCP. I think there's a way to reset XCP I saw in another Forums post by removing the Local SR? Olivier shared that in the post..but I don't remember what post it was. Not sure if this is a test or prod Host/environment for you...but if you can, unless someone from the Vates team comments, I think all that can be done is reinstall.

@olivierlambert Ah, ok...thanks, but I'm not using the appliance; I installed XO via source.

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

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.

@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

@kagbasi-ngc said in Using Multiple Servers in LDAP Plug-in: @john.c Thanks for the suggestion - I'm exploring this option. Oh, forgot a bit of follow up. You can also do something similar with Linux. Using the clustering software configured for failover and also a Samba server. The Samba server needs to be at minimum version 4.0, though to be supported with updates version 4.20 at minimum, to guarantee a long period of support either 4.21 or 4.22. Though using the in box Samba server from RHEL 9 is best as its supported by Red Hat and is version 4.15. Though you can select another Linux distribution which is new enough to support at minimum the same version of Samba. Then run the process of setting up the Samba Server as an Active Directory Domain Controller. https://wiki.samba.org/index.php/Setting_up_Samba_as_an_Active_Directory_Domain_Controller Also with Windows Server based solution, you can add more servers to the AD Failover Cluster as required. So effectively you could even have 3-5 AD domain controllers, instead of just the 2 AD Controllers for redundancy.

Also post VGA being disabled, it does seem better.

Hi, Looks like we've got a similar problem on our newly deployed XOA (5.103.1). There are approx. 500 tasks and some of them are "refreshing/changing places in the list". Also, next to the "Tasks" button on the left inventory menu we can see "1" from time to time (screenshot: 03.PNG). Haven't yet tried to clear it but would first understand why this is happening and maybe it can be perma fixed? 01 [image: 1742913684189-01.png] 02 [image: 1742913690478-02.png] 03 [image: 1742913697611-03.png]

@DustinB Yeah, that's what I will try to remember to do next time. This is still worlds easier for me than trying to keep my ESXi hosts up to date was back when I used them. So very much better than that. I very rarely updated those at all.

@djp I am not really sure what else besides migration traffic passes over that .

@Forza There are various topics touching on how SMAPIv1 is a bottleneck here, eg: https://xcp-ng.org/forum/topic/9389/backup-migration-performance/8 - that's probably not the best example as it is also more on backups than migration!

Hi, If you have support, you should create a ticket asking for the feature if you need. We don't have much request for that, but if nobody ask, it will never happen by chance If you don't, you can still open an issue on our XCP-ng repo to ask for it, at least we'll have a trace of the request

@john.manning Happy to hear that. I guess it was my fault - I edited the naming of the snipped pseudo vars: OLDVBDUUID = xe vdi-param-get uuid=VDIUUID param-name=vbd-uuids VDIUSERDEVICE = xe vbd-param-get param-name=userdevice uuid=OLDVBDUUID maybe that way it's clearer for others that might find that helpful