@Tristis-Oris My setup is similar to yours, and I get similar errors on any existing backup job. However, if I create a new backup job, then it works without any error. ping @florent , maybe these data points are useful.

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

@florent Is there somewhere we could discuss therse not on public forum....Thanks !

@john.c Yeah - like I said it is a good step in the right direction. Just doesn't solve my particular storage related problems.

@TeddyAstie I ran iperf3 tests between two VMs on Xeon E5-2680v2 and average results were within 2% of each other with the patch being slower. Peak speed was 14.5 vs. 13.7 Gbits/sec.

@2planks said in NIC not working on new HPE DL360 Gen11: Has this issue happened before? I don't remember such an issue on this hardware. Can you share the outputs of lspci -v, lsmod, dmesg, and dmidecode?

@msupport Right! I'm sure it's a great product, the goal for this is to have no licenses, unlimited users, ported for several hypervisors. It's just a pet project I've wanted to do since I started in IT, and if other people besides me can use it, great! I know one of my employers may work on making it a polished project if the Omnissa renewal is too expensive. And if I can build it, why pay for it? I might not be a programmer by trade, but there's no reason I can't learn and ask around for help!

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

The question that is begging to be answered then is would Change Block Tracking (CBT) address this issue? Presumably it would, but as the post is still actively getting updates, https://xcp-ng.org/forum/topic/9268/cbt-the-thread-to-centralize-your-feedback

@olivierlambert Morning ! it was old server but we want collected some data from VM, I check on Metadata it not has Backup. If there any console we can collected data from VM ?

I was able to find a post which discussed the known NIC issue in Linux imported VMs (by Brandon Lee): https://www.virtualizationhowto.com/2024/02/migrate-from-vmware-to-xcp-ng-a-vsphere-admins-perspective/ It kinda makes sense I guess why this happens -> the NIC is given a static name in Netplan initially when the VM is created. When the VM is migrated/imported into XO, this Netplan NIC name is NOT changed in the Netplan .yml file, thus the OS can't get an IP. To rectify this, change the name XO gives the NIC in the Linux OS (eth0 for Ubnt2204 or enX0 for Ubnt2404) in the .yml file, reboot the VM, then you'll be able to get an IP if you use DHCP. You can then also install Guest Tools by using a pkg mgr (apt for Ubnt). The only remaining problem I'm having now is the CD eject issue. And again..this is on both imported Linux and Windows VMs.

@DustinB said in "Block migraton" option on the VM´s Advanced tab: @abudef The English translation is meant to be "Prevent Migration". I think some lines were crossed ha. I agree it really needs to actually read "Prevent Migration", that will then make it pretty clear.

@stormi Thanks, I was wondering if that was the case from reading the other threads.

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

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

@olivierlambert I did open a ticket but thought I would post here as well to see if anyone had insights. Thanks.

@ATSandrearicci Check the compatibility [image: 1744296853670-0877c1cb-2ac5-4afb-a993-a96fd66c7474-image.png] You must configure the license for the client on the license server: [image: 1744296959393-01b3b16d-8f06-4fe9-94ce-87b5c1cc1fcf-image.png] On the windows 11 client in the Nvidia control panel you have to specify the license server: [image: 1744297049623-8d883042-fc27-4678-8a05-e3c96b7a38a4-image.png] Check the authorization on the file: [image: 1744298130266-796ee95b-956e-4e9e-b178-cf60e92a0c97-image.png]

Upon further testing, it seems that initiating a rescan of the 0 byte SR fixes the size issue. However, I should not be having to do this but at least it appears to be more easily dealt with than I previously assessed.

Great! Enjoy