Hi @MathieuRA unfortunately, I won't be back until Sunday evening. I'll test it first thing Monday morning and then get back to you

@dave.opc that's it keep us updated on this

@florent said in vmware vm migration: @acebmxer yes after the first migration, XO knwo that the migration is incomplete and that you may want to finish it later. But if you start this VM direvtly , it will write some data, thus it won't be in sync anymore with the Vmware snapshot. Then XO won't be able to resume You can start a copy of the VM ( XO will handle it for you ) and delete the copy when you're done My advice is to migrate this VM to the right SR and then do the resume. But keep in mind that the V2V tool is intended to target only one SR, so migrate all they disk to the same SR, and select the right one when resuming the V2V. You can change the network after My previous migration was successful with no issues. Previously test vm was fresh install so no vmtools installed. But I did shut the vm down myself prior to starting the migration. VM boots no issues no prompts. This time I decided to follow the steps listed in the documentation as i have been following the changes and updates for the v2v migration. Following the steps as mention XO presented me with that prompt which was not mention in the documentation. As i was typing the post to gather my information it was then i noticed i did not select the proper destination SR and the appropriate nic/vlan for networking. So I noted that in the post. With the assumption i could correct that on the final migration. With that said the I guess the documentation should state - Start vm to test if boots, etc.. When prompted choose "Start a copy". When done shutdown vm and remove.

@dcskinner No this is not intend, I just ran some tests, my host has a bond for management, which showed up in the dropdown. Then I created a second bond, it did not show in the dropdown until I actually configure it. When creating it, it was actually created by default with "mode=none" so I went to the host's network tab, chose static and assigned an IP to it and it was then showing in the dropdown. Are you sure your bond is properly configured?

This is indeed not normal, could be a BIOS problem or even hardware problem (or a pretty bad bug in Xen?). What kind of hardware is it? I would be surprised to be server grade (or this points to a software bug then).

Let me ping @Team-OS-Platform-Release

Hi @champagnecharly , On the XO side, it seems that this PCI has an empty string ID, which doesn't enable us to delete it. We'll have to do some tests to find out how to prevent that. We might have trouble reproducing the issue, so would you mind helping us with the tests? You would need to add this piece of code on file xo-server/dist/xapi-object-to-xo.mjs before the line that start with if (isHvm) { (that should be near line 475) if ((_vm$attachedPcis = vm.attachedPcis) !== null && _vm$attachedPcis !== void 0 && _vm$attachedPcis.includes('')) { warn('Empty string PCI id:', otherConfig.pci); } then restart xo-server and look at the output of journalctl, there should be some lines looking like: 2026-01-30T09:26:17.763Z xo:server:xapi-objects-to-xo WARN Empty string PCI id:

@Tristis-Oris the logic was directly ported over from C# version, so it does the same stuff what it filters there. It just toggles this search scope: QueryScope* TreeSearch::GetTreeSearchScope() { ObjectTypes types = Search::DefaultObjectTypes(); types |= ObjectTypes::Pool; SettingsManager& settings = SettingsManager::instance(); if (settings.getDefaultTemplatesVisible()) types |= ObjectTypes::DefaultTemplate; if (settings.getUserTemplatesVisible()) // these are custom types |= ObjectTypes::UserTemplate; if (settings.getLocalSRsVisible()) types |= ObjectTypes::LocalSR; return new QueryScope(types); } I assume it matches all user-defined templates, the defaults you see are "system defined" and part of xcp-ng .rpm packages. It's possible that this logic just wasn't ported correctly, I will look into it.

@busthead said in Windows 11 (Win11_25H2_English_x64.iso) Fails to Install: It appears I missed the key press to start setup Dont you know your are not suppose to blink when doing working. You might miss something Glad you figured it out.