Categories

• News

  All news regarding Xen and XCP-ng ecosystem
  145 Topics

  5k Posts

  C

  @dinhngtu Just wanted to pass along some feedback from trialing the newest version (9.2.350) -- in case it's helpful. When comparing to the previous version (9.1.200 -- and earlier versions as well) on Windows 11 Pro VM (with latest updates), this new version results in noticeably slower VM restart and shutdown times (at least when monitored via xenadmin [on Windows] and xenadminqt [on Linux]). ... Just remembered I updated XCP-ng at the same time to the latest iteration, perhaps the slowdown may be related to that.
• XCP-ng

  Everything related to the virtualization platform

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

  15k Posts

  O

  Nice! Have you tested the snapshot, revert and so on?
• Xen Orchestra

  All Xen Orchestra related questions/reports

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

  29k Posts

  C

  @poddingue Sorry for my delay; I appreciate the response and insight. Concerning the Wiki entries, you appear to be correct and the wiki has been updated accordingly and the offending entries removed - perhaps it was my bad google-fu directing me to the blog post from more than 10 years ago (which then referenced the wiki lol) so that's on me and for that I apologise; I do note though that it's still listed in the Feature Matrix - https://xen-orchestra.com/#!/featuresmatrix (Edit: and the Advanced features section ) I'll endeavor to raise this in the appropriate spot in gitlab, and if there's any interesting movement or activity I'll try and post here for posterity. Regards. CAPS
• XOSTOR

  Our hyperconverged storage solution
  50 Topics

  796 Posts

  O

  Great, thanks for the feedback!
• Non-English speakers

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

  135 Posts

  A

  Pour l'ISO montée deux fois : My bad, j'ai ajouter un truc en trop sur mon précédent fix. Une PR est en cours pour corriger ça. Pour le problème principal : J'ai identifié la cause, mais je n'ai pas encore de solution. Sans les drivers Xen (non initialisés avant l'installation), une VM est limitée à 4 périphériques. La séquence de boot ne peut donc pas détecter le second disque contenant le fichier Kickstart (ks). Côté Packer, on semble être bloqués par cette contrainte XCP-ng. Les seules alternatives actuelles seraient de se limiter à : 2 disques + 2 CD ou 3 disques + 1 CD + HTTP (Note : L'installation manuelle fonctionne car l'installateur démarre directement, avec le driver xen_blkfront, alors qu'avec Packer, l'injection de notre fichier interrompt le flux de démarrage classique). Je vais fouiller encore un peu, mais sans certitude d'un contournement possible. (et je regarde pour ajouter le CDlabel)