@dinhngtu it still wouldn't boot with the correct template. That said, I have been testing other VMs which were created on xcp-ng, with the correct templates, and get better performance out of them when they are migrated to a hyper-v host. I believe that this is related to SMAPIv1 limitations - which are known and being actively worked on with SMAPIv3. Unfortunately for us at this point, xcp-ng may not fit our business - hopefully one day soon it will be, but until then, it is what it is.

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

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

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

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

Great! Enjoy

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

@vkeven XCP-ng 8.1 release note says VSS and quiesced snapshots support is removed, because it never worked correctly and caused more harm than good. Note that Windows guest tools version 9 (the default for recent versions of Windows if you install Citrix drivers) already removed VSS support, even for older versions of CH / XCP-ng I am not sure if this VSS feature is bound to the PV drivers, or if it also needs hypervisor support. Though it is not recommended to stay on a old version of the guest agent.

@CodeMercenary I had a simillar issue to you, check the time and the date on the host. If this might be any help to you: https://xcp-ng.org/forum/topic/10687/after-an-update-the-nic-s-has-disappeared-but-still-works-somehow/10?_=1743764792775

Hi @florent Here is the log. https://drive.google.com/file/d/1y3bPuyQPfYKHH54mIniyHBZ9Mloqjeec/view?usp=share_link Thanks!

@kagbasi-ngc tries this a while ago, but my default group are in OU having , or () in their name (i know it's very bad but it's been there before my arrival) tried with a security group in a simple OU this time it worked using fully DN.

we are reworking the import code , along the new backup code ( https://xcp-ng.org/forum/topic/10664/our-future-backup-code-test-it ) to unify the differetn disk transformation path For now: V2V handles flat, cowd, sesparse, stream optimized vmdk in the format "metadata.vmdk and a data file ) and ova ( for VSAN) disk import support monolithic vmdk ( cowd, sesparse, streamoptimized ) ova improt support only stream ova with streamoptimzed vmdk inside

@jcharles said in xo-cli vm.importFromEsxi give error: JsonRpcError: can't get runtime of object devtest1 (Type: VirtualMachine): ssword=XXXXX sr=2e9ff937-6c4c-86c5-81d2-18331c69bbe5 sslVerify=false stopSource=true user=root template=39f341be-b9aa-c7fd-33a9-355312c2246a vm=devtest1 vm should be an number it is the id in the URL in esxi

No. I'm saying that all VMs (HVM) are using RFB consoles, readable with VNC protocol (used by XO or a VNC client). There's no text console since it's like a screen in HVM. If you are stuck on "Loading in progress", it's not a console issue, it's a VM issue. You can use a LiveCD to check what's going on.

@AtaxyaNetwork said in XO update fails: @edisoninfo Hi, What's xo-install.sh ? It's a third party script ? Very likely indeed Those scripts really needs to make sure to provide the URL of the repo to report issues in a very visible way.

@Danp No sir, I have not. I have, however, exported the same VM in the OVA format. Ended up being about 47 GiB, however, I was able to import it into XOA without any issues, and the import took just under 10 minutes to complete.