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

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

@dinhngtu That's great, thank you. I think I'll wait a bit before switching tools. Everything's working perfectly at the moment. If you need me to test anything, just let me know. I'd be happy to test it when I have time.

Keep us posted, happy to hear from it!

@florent Yes.

@drwhite85 I suggest watching some youtube videos about xcp-ng. I guest Lawrence Systems - https://www.youtube.com/watch?v=2wMmSm_ZeZ4 He has other videos that go into more depth

@samuelolavo Yes, I do use NUT, but I don’t want to install any additional packet on XCP-ng. The way I found leverage the SSH authorized keys restrictions, and so you only need to change one file. Thanks for the link anyway

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

@gduperrey Thanks! Will test tomorrow as our internal lab / test environment is currently unavailable. I will inform you about the results of my testing here. Best regards

I managed to do the migration by splitting over the two storages the remove system has. This made it work and I managed to move that one VM. However I still have a second one It's thick provisioned (LVM - never can remember the terms thin/thick). Offline isn't an option unfortunately since I need the services running, can't take if off for 15 hours. But since two of the services are docker containers, both having a separate disk of 500GB, I can make it work by setting up a two new systems and moving everything from the container there. Which would reduce the size by 1TB and make thing easier to manage. Was hoping I could finally upgrade the main xcp-ng last weekend.

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

@bleader Hopefully the palm print on my forehead isn't visible from where you are sitting. Of course the interface needs an IP address. In my defense, normally for something like this, I wouldn't put it on the bonded interface with all the trunked VLAN's for guest traffic (we don't give that one an IP) and it would go on the other bonded interface that isn't trunked and does get an IP, but these are test hosts and I didn't set up the other bond, so it is pulling double duty. I was able to set the IP's and get SDN working. Thanks!

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:

@pdonias https://docs.xen-orchestra.com/users [...] Operator An operator can make everyday operations on assigned objects. For example, on a VM: eject a CD insert a CD (if he can view the ISO storage repository) start, restart, shutdown, suspend/resume it All other operations are forbidden. [...] As I understand it (I may be mistaken), changing the "Rate Limit" is already a configuration change and should not be available to an Operator.

@olivierlambert As I pointed out earlier, everything was working perfectly until I shut down to replace an NVMe stick, which involved moving around a couple of PCIe cards, hence changing their IDs for passthrough. It's a Supermicro X11DPH-T running a pair of Xeon Gold 5118. The BIOS was up to date as of the middle of last year, with a date of 3/5/24. Cheers.

@florent As it turns out, the job completed the next time it ran and this task went away, not sure why that first one failed but it seems to be OK for now. I will update this if I see this error again and be sure to include as many logs as I can. Thanks as always!

@psafont Freezing/thawing doesn't actually suspend a VM, but it's just a part of the backup process, where I/O operations are quiesced to create a stable view of the on-disk data.