@jsajous26 sorry I misread. I don't know how ti setup this while using veeam

@Mang0Musztarda To add to what @florent said, here's the complete picture: Why your command failed: Wrong URL: localhost:9004 is the internal port that only listens on 127.0.0.1. It's proxied through xo-server at /openmetrics/metrics. Wrong token: The error "Query authentication does not match server setting" means your Bearer token doesn't match the one configured in the plugin. Correct approach: Get your secret from: Settings → Plugins → OpenMetrics → "Prometheus secret" Use the proxied endpoint: curl -H "Authorization: Bearer <your-actual-secret>" \ http://<your-xo-server>/openmetrics/metrics For health checks (no auth required): curl http://<your-xo-server>/openmetrics/health Returns: {"status":"ok"} Full documentation is available at: https://docs.xen-orchestra.com/advanced#openmetrics--prometheus-integration It covers Prometheus configuration, available metrics, Grafana dashboards, alerting rules, and troubleshooting. @MajorP93 Thanks for sharing your Grafana dashboard! It could indeed be a nice addition to link it from the official docs as a community example.

@nikade can you try a journalctl | grep 'nbdkit logs' ? new branch with more fixes ( feat_exposes_esxi_export ) the main fix is a >= that should have been a > https://github.com/vatesfr/xen-orchestra/pull/9411/changes#diff-f0de876ee608dac8d272996fbb8fa63ec76473bd260ad5abf1995a805866d1beR130 hopefully I am not paid by the character. Don't forget to do a yarn build at the root of your XO and restart it. this also expose a way to export a disk from an esxi/vsphere with xo-cli. First install xo-cli with npm install -g xo-cli and register it https://docs.xen-orchestra.com/architecture#xo-cli-cli xo-cli.mjs esxi.exportDisk host=ipOfEsxiOrVsphere user=EsxiLogin password='PlzDontEnter!' vm=3 disk='scsi0:0' @=/mnt/ssd/export/out.qcow2 format=qcow2 You can check that the export is valid with qemu-img check /mnt/ssd/export/out.qcow2 fbeauchamp opened this pull request in vatesfr/xen-orchestra draft feat(xo-server): expose an api method to export a disk from vmware #9411

Hi, unfortunately the problem still exists (fully patched XCP-ng 8.3 pool). After rebooting the hosts remote syslog did not work anymore (no incoming data on graylog server). After setting remote syslog to a different IP address in Xen Orchestra and switching it back to the correct IP address again solves the issue but remote syslog should survive a host reboot... Best regards

I recreate my ZFS pool. But next time or for other stuck with this kind of issue, I think you should start to rename your ZFS POOL. I think the old ZPOOL name stay in XO configuration shadow settings. To rename a ZFS pool, export it with zpool export [poolname] and then import it with the new name using zpool import [poolname] [newpoolname] And then recreate (sr-create) your STORAGE in XO

@Andrew That's exactly what I wanted to know, thanks! Should video=efifb:off be only applied to the VGA controller, or also to the audio device? For instance (applied to vga-only): /opt/xensource/libexec/xen-cmdline --set-dom0 "video=efifb:off xen-pciback.hide=(0000:02:00.0)" <- video /opt/xensource/libexec/xen-cmdline --set-dom0 "xen-pciback.hide=(0000:02:00.1)" <- audio In grub.cfg, are we replacing console=vga with console=ttyS1 under the multiboot2 line?