Categories

• News

  All news regarding Xen and XCP-ng ecosystem
  139 Topics

  4k Posts

  P

  @dinhngtu said in XCP-ng Windows PV tools announcements: @probain The canonical way is to check the product_id instead https://docs.ansible.com/projects/ansible/latest/collections/ansible/windows/win_package_module.html#parameter-product_id The ProductCode changes every time a new version of XCP-ng Windows PV tools is released, and you can get it from each release's MSI: No problem... If you ever decide to have the .exe-file as a separate item. Not bundled within the zip-file. Then I would be even happier. But until then, thanks for everything!
• XCP-ng

  Everything related to the virtualization platform

  • Compute
  • XO Lite
  • Migrate to XCP-ng
  • Hardware
  • Development
  1k Topics

  14k Posts

  D

  Hi, you are not the only one to have the problem. We do as well and with a smaller environment in terms of physical hosts ( only 3). I did not engage with support yet because the size has gone back under 90% on its own but it keep popping up any other day. We have constanst sr.scan as well which in our case last for a long time and we have other issues as well at running task like starting or stopping VM but we haven't figured why yet.
• Xen Orchestra

  All Xen Orchestra related questions/reports

  • Management
  • Advanced features
  • Backup
  • REST API
  • Infrastructure as Code
  3k Topics

  26k Posts

  O

  Create an appliance with all those VMs and configure the order and delay inside it.
• XOSTOR

  Our hyperconverged storage solution
  38 Topics

  691 Posts

  D

  Hello, we have a pool of 3 hosts with XOSTOR and we are having various performance issues related to tasks like start/stop VMs, VM migrations or similar which according to Vates support are down to the task waiting for Sr.scan to be completed. I can see sr.scan running all the time and some of them takes around 4 / 5 minutes... the XOSTOR storage is around 27Tb and store about 107 VMs base disk + same amount of snapshots + what I think is the current changes for each of them for a total of 348 disks. What your environments look likes? how long your sr.scans takes and most importantly do you have problems at start/stopping and migrating VMs? For instance when we migrate VMs, the VMs freeze for about 3 / 4 minutes just before re-attaching the VDI on the target host and according to support is due to the sr.scan.
• Non-English speakers

  • French (Français)
  • Turkish (Türk)
  • Portuguese (Português)
  31 Topics

  90 Posts

  O

  Yes, account aren't related