Subcategories

• Management

  VMs, hosts, pools, networks and all other usual management tasks.
  472 Topics

  4k Posts

  C

  I got my R730 working, thanks to @majorp93 giving the tip about dmidecode. Thanks a bunch. It turns out that while this is a Dell R730, it was actually sold by a different vendor for use as video storage so the internal product name doesn't have Dell in it, it's HD NVR. I used that as the vendor field and tweaked a couple other plugin settings and now it gives me data. I am still missing two of the values in the UI and I'm not sure why, but for different reasons. On my R630 servers they show the server IP address under the IPMI badge. They also both have the default Dell /^ip address$/i as the regex in the ip setting in the plugin. I used that same regex in the R730 and I can see in the ipmitool listing that it has the same field name for the IP address as the R630, yet it shows IPMI: Unknown. Also confusing is that the R630 servers have nothing under fanStatus in the plugin settings but they show 14x fans status: ✅ in the UI. The R730 also has nothing under the plugin settings fanStatus field but it has no data in the UI. Looking at the ipmitool output I am not sure what field it would use for fan status. It makes me think there must be a default field name it is trying with the R630 to get that status but that doesn't work with the R730. Any hints about how to get those last two badges to work on the R730? I am also not sure what bmcStatus should be set to. I don't know what that means exactly so I don't know if any of the fields shown in ipmitool are applicable. This plugin is really cool, thank you so much for building it.
• Advanced features

  ACLs, Self-service, Cloud-init, Load balancing...
  104 Topics

  863 Posts

  L

  @florent Thanks for your reply! We have started to migrate thousands of VMs, so disk transfer speed is important for us.. We will also do our detailed tests soon with different threads setting and publish it here. I think threads=1 is a good and logical default, but not efficient. Others might complain if you set it to a higher value. Configuration option would be a real good solution.
• Backup

  All XO backup features: full and incremental, replication, mirrors...
  510 Topics

  5k Posts

  I

  The problem still persists with commit e376a. After installation of updates to XenOrchestra I reboot the VM. Still no backup on this one VM possible. For now I have created a separate backup job which seems to be working. Regards, Marc
• REST API

  Everything related to Xen Orchestra's REST API
  86 Topics

  645 Posts

  J

  Hello I'm pulling stats for all VMs to understand CPU usage. We're a bit behind the curve in terms of XO versions, but these questions hopefully are still relevant. If using a granularity of days, the interval is set to 86400 (understandably) but the endTimestamp varies. Running this on June 9th @ ~1740 we get timestamps for both Mon Jun 8 01:00:00 AM BST 2026 and Tues Jun 9 01:00:00 AM BST 2026. Does this average across the day? Why is the timestamp 0100? Why would there be different timestamps between VMs (all are running) and does that mean that the figures are misaligned in the results? These are retrieved via curl and a bash script, a bit hacky, but for clarity the request is: ++ curl -X GET -s -H accept:application/json -b authenticationToken=[[REDACTED]] -o [[REDACTED]] 'https://[[REDACTED]]/rest/v0/vms/[[REDACTED]]/stats?granularity=days' Really keen to know if we can control the start and endtime, as well as provide a manual interval, as well as the aggregation strategy (min, max, average). Are any of these possible? Lastly, is cpuUsage the percentage as per the dashboard, but averaged over all CPUs? Thanks so much in advance. James
• Infrastructure as Code

  Terraform, Packer or any tool to do IaC
  50 Topics

  470 Posts

  C

  Kubernetes CSI Driver for XO new release v0.3.0 Stable CSI Volume Identity: This decouples Kubernetes volume identity from backend storage lifecycle events (e.g. VDI migration between Storage Repositories) Topology-Aware Volume Provisioning: Dynamic provisioning now supports topology-aware pool selection. ️ Migration required from v0.2.0 to v0.3.0 Full release note: https://github.com/vatesfr/xenorchestra-csi-driver/releases/tag/v0.3.0