Documented at https://xen-orchestra.com/docs/xoa.html#other-interfaces

Although I didn't encounter your problem, I followed the steps in an article ( sorry fail to post the link) and successfully migrated the virtual machine from VMware to XCP-ng, which was very convenient.

@vahric-0 Then I am out of suggestions, sorry.

FWIW, a filter of !"SR_type":"udev" would remove both DVD and Removable Storage entries

That's a great feedback @felibb , thanks! We'll try to dig on this to see if that lead takes us to something

@olivierlambert thanks for the feedback

Okay so it will be more logical to use the same logic than with the Load balancer, where we compute a total of all vCPUs

@MathieuRA said in Pool overview - Some suggestions: Ho, i see the it was already planned to be in the pool dashboard for XO6. Not yet designed BTW. [image: 1715759886512-capture-d-%C3%A9cran-de-2024-05-15-09-56-55.png] Great, that looks exactly like I want it.

Don't be, nice to know it's OK for you now

Are you trying to move them all at once?

@doogie06 Thank you too! I also have XO setup for self-signed TLS access. I knew about the xo-cli task deletion command, but always had to disable TLS in my /root/.config/xo-server/config.toml file and then restart xo-server.service to delete the orphaned tasks. The allowUnauthorized parameter was just what I needed. That's why this community is really wonderful. Thanks again.

@Danp Thanks for the feedback So i understood correctly so wait and see Regards

Because the current storage stack doesn't support live resize, which is obvious after your tests.

@Andrew awesome, thank you for your explanation. After reading a bit more about MTU (see this) I get it now. I looked up MTU in OPNsense for the VLAN interfaces and was surprised that it automatically uses 1496 MTU, which explains why it works and means I don't have to adjust my host's MTU settings, which I really didn't want to do. Now, as far as I understand, keeping it this way could introduce some split packets and therefore potentially limiting throughput. To fix this, I would need to increase the MTU to 1504 or larger. However, after some more reading (thanks for the keyword "baby giants"), it seems that today, MTU is just a "guideline" for LAN. I will keep the host MTU at 1500 for now.

@jimmymiller you mean disk size is locked on? You can't change it. I think only way it's try to automate VM creation with things like packer https://xcp-ng.org/blog/2024/02/22/using-packer-with-xcp-ng/

@Andrew thanks