@DustinB thank you! I suspected as much, but as my wife points out all the time, I am terrible at finding things, so I figured I would ask.

Ping @Team-XO-Backend

@jerry1333 could you do a TOP in XOA vm to identify what consumes CPU ?

Replying to an old thread because this one popped up in a search. There is an open source and locally running ignition/combustion generator that I've used on bare metal. To use it with XCP-ng, we would need the ability to have a second "cd rom" drive during the install phase, one for the OS installer, one for the combustion/ignition ISO generated from the tool. https://opensuse.github.io/fuel-ignition/ They say it only runs locally, no info is send out to the web. I didn't monitor my connection on the one time I used it, and probably won't the next time (coming soon to a bare metal cluster in my lab). For the record, I'm using the LEAP version of Micro for my tasks.

@TheNorthernLight Thanks for pointing that out, that totally makes sense, I should have realized to look it up that way. I guess I just think of XCP-ng as its own product so much that I forget it's based on Xen even though I know that.

Still working fine But after this work You put in it seems like VDI-size in VMs VDIS is back to showing size of snapshot instead of size of VM. I'l update the XO6 thread https://xcp-ng.org/forum/topic/11604/xo-6-dedicated-thread-for-all-your-feedback/169

This usually happens when dependencies are out of sync after pulling updates. Did you try removing node_modules and the lock file and then running yarn install again before starting XO?

I haven't found how to set up a physical NIC. you can only edit already configured ones.

@simonp - Can you reshare the dashboards. The link says json is not available for any of these dashboards,