Hmm I'm not sure it will apply for the whole pool, let me ask @Team-XAPI-Network

Ping @pdonias

Don't mix XO commands and xe, even if XO is on top of it, the mapping isn't exactly 1:1.

In XO, host force shutdown is preventing XAPI to try moving the VMs around to another host. So in force mode in XO, the host is disabled first, then shutdown command is sent. If you want to do the same thing, you have then 2 xe commands to do: host.disable and finally host.shutdown

Hi,

Have you followed https://help.vates.tech/kb/en-us/8-technical-support/15-open-a-support-ticket ?

Hmm that's interesting. I suppose you can remove it via xe CLI, but XO shouldn't prevent you to remove it.

Let me ping @Team-XAPI-Network for the xe command to remove this parameter, and ping @bastien-nollet to see how we could get rid of this limitation that blocks removing bogus devices.

Worth asking @Team-OS-Platform-Release

There's a similar magic we've seen countless time with XO: you have a bug that nobody reports for years and suddenly it pops from various sources (or with many details so it's easy to spot), you think it's recently introduced, you check your diff and then after hours you realize it's there since a while

Nice find! Is there's any plan for Debian to backport that patch?

Does it work as you wanted now? If yes, probably something we can put in our official doc! Ping @thomas-dkmt

Good to know, maybe it's time to finish that at some point, let me ping @gregoire

Indeed, it's hosted in Lyon, so an issue could happen in many places in the middle ^^

They aren't meant for that, I have no idea how difficult it would be to make the PV drivers to actually "do something" (what exactly? write a value in the xenstore?). Maybe @teddyastie could provide an opinion on that.

And beyond that, I'm not sure we actually want this behaviour from a security perspective. But it's another topic.

No, it's not using the same mechanism. It's a PV call (if I remember, but I'm not sure). You cannot write a xenstore key in live to a VM (only on boot).

Tools are aware of a snapshot so you don't have blocks in flight.

Bad ping: it's @Team-XAPI-Network

Works for me and from the office.

https://downforeveryoneorjustme.com/xen-orchestra.com

You can read key/values from the xenstore, and write some (from VM to outside), but you cannot write values "in live" from outside the VM to the inside.

I don't think stop will remove it, probably better to yum remove it.

For Openmetrics, check: https://docs.xen-orchestra.com/advanced#openmetrics--prometheus-integration

I switched our own production to that, so far it looks promising.

Hi,

I think I would prefer to take the OpenMetrics route today It's easier to setup and get your data in a Prometheus server where Grafana can shine.