@Kptainflintt said in Cloning Windows 11 with vTPM: No reply to this topic but just seen same thing. And same "workaround" : disabling vTPM at VM creation from template to avoid crashing. I can confirm that XOA want to add a second vTPM, any fix ? Sharing for temporal context: This appears to still be be happening when creating a VM using my custom Windows 11 template (didn't do any cloudbase stuff, just some really basic stuff like updates, then sysprep). Once I click "Open advanced settings" then toggle "Enable vTPM" into the disabled state, my attempt to create the VM succeeds, and the newly cloned VM has a vTPM with a different UUID. This is literally my first attempt at creating and then cloning a windows 11 template, but it seems to be working.

@McHenry like @olivierlambert said, keep in mind that a VM with 16 CPUs will be less available than a VM with 4 vCPUs, because it's easier to have 4 vCPUs ready to work than 16 simultaneously beware of this graph, it only graph the first 16 vCPU, but you can have more working ! the visual widget is failing you. think of topology too : if you have two sockets, you can have a topology of 2 sockets with 4 cores for a 8 vCPU VM. If you have only one socket, try to keep the topology to "1 socket xx cores" for your VMs, performance wise.

@psafont thats good to know the system will prevent you from uploading the same ISO. Since my latest testing i cant seeem to get XO-CE to show the incorrect file name .img of the iso that was uploaded. But know @plaidypus is not alone in this as I have seen it myself and that is why you will see most of the iso in the picture have a date just a few days prior to this recent testing. I manually deleted the iso that were .img and manually uploaded the ISOs again.

@Pilow said in "ACLs" and "VM creator" options on the VM´s Advanced tab: @panzersrmm I tried to snapshot and revert on a VM with Resource set + ACLs and they did not disappear... ? [image: 1759935440961-b316a971-e2cf-4843-9d05-a96b2299d12a-image.png] @Pilow Yes, yours were kept because you didn't modify them manually. My test case was: Set ACLs + VM creator for a working VM Make a snapshot of this VM Change various VM advanced properties including ACLs + VM creator (simulate evolution of VM) Revert the VM to that snapshot state Check if the set properties were restored: all were restored except ACLs I was wrong about VM creator. That is indeed restored, but ACLs isn't. @olivierlambert Thank you for the explanation. I wasn't trying to judge, just to understand how it actually works.

@andriy.sultanov said in "Block migraton" option on the VM´s Advanced tab: @panzersrmm @panzersrmm said in "Block migraton" option on the VM´s Advanced tab: Hi! Is there a VM parameter that saves this "Block migration" UI button? I wasn't able to identify which one it is with command: xe vm-param-list uuid=<VMuuid> Thank you! How do you mean? Is the XO option not persistent? XO sets these parameters: # xe vm-list uuid=$UUID params=blocked-operations blocked-operations (MRW) : pool_migrate: true; migrate_send: true Which you can set like this yourself: # xe vm-param-set uuid=$UUID blocked-operations:migrate_send=true # xe vm-param-set uuid=$UUID blocked-operations:pool_migrate=true @andriy.sultanov Thank you for your answer! That's what I was looking for. I was looking directly at the VM parameters, with xe vm-param-list uuid=$UUID and I was directly searching for "blocked_migration". Now I know what to look for. @olivierlambert Thank you for pinging the appropriate team for the answer.

Hi, To start, it's good to read: https://docs.vates.tech/security/ Especially https://docs.vates.tech/security/#contact--disclosure Then, I can answer here directly: we are not affected since Redis is only listening locally, therefore it's not exposed outside XO. There's nothing interesting to do with that CVE, because in order to use it, you already must be a privileged user.

@Forza Good point. I need to apply the latest patches anyway, so I'll be rebooting the pool later today anyway.

@ThisGuy_420 Great! We'll try to get those tools available more broadly and finally get a 1.0 officially, this is taking too much time while they are perfectly working. Pinging @Team-OS-Platform-Release

This is now solved. I rebuilt the XO VM and can create multiple VMs as expected.

@olivierlambert said in Xen Orchestra commit a62ac Templates not loading data: The fix was merged in master, you should have it now if you update to the latest commit Very cool. Works perfectly fine again. Love this Keep up the excellent work you guys Regards, Marc

@olivierlambert yes Olivier. but I'm in doubt of the correct redirection I have to make in NPM ... Should I port the token part of the url also in the redirected internal part ? or do I miss an nginx parameter to help pass this token 'inside' ?

@flakpyro All this complexity makes me question the advantages of having all hosts in the same pool.

Ping @pdonias

@okynnor IIRC, it would take a reboot before the problem showed up. I'd check after a reboot if XenSvc wasn't stuck in the starting state.

Then reboot than broken host and in the meantime, re-issue the power reset command from the master.

I had a similar issue, and what helped me was routing update traffic through Static Residential Proxies to avoid deep packet inspection that was blocking some repositories. They worked better than regular proxies in our setup since they look like normal home users, so the network didn’t treat the traffic as suspicious. You might need to whitelist some domains manually though, depending on how strict your proxy rules are.

That's very clear, thank you for your prompt response!

It might record the max static RAM (IDK)

@DustinB Thank you. I understand, it's absolutely a cosmetic request.

@olivierlambert did not check that unfortunately, since it it is already setup now, will be hard to reproduce it