Categories

• News

  All news regarding Xen and XCP-ng ecosystem
  145 Topics

  5k Posts

  J

  @dinhngtu When creating GPOs if you have an non-policy setting for all users in the settings area for the agent config. The policy based registry settings can go into “Software\Policies”, for the appropriate HKEY and keys. In which case the policy based registry entries supersede the non-policy ones, when considering also the HKLM vs HKU and HKCU cascade. Also a disabling of user configuration of the managed setting(s) along with display of a message like “At least some of these settings are managed by the organisation”.
• XCP-ng

  Everything related to the virtualization platform

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

  15k Posts

  D

  @poddingue the response is "VM_REQUIRES_SR". The VMs are storing their vdisk on a local NVME. This is crucial for this hypervisor as I do not want it to depend on network storage. Can I work around this error in such a scenario, i.e. is a Rolling Pool Update possible under these circumstances? Does the Smart Reboot require evacuating the VMs? Technically it shouldn't as in XO there will be a warning that can be manually overridden. WHy do I get the warning in case of a Smart Reboot?
• Xen Orchestra

  All Xen Orchestra related questions/reports

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

  29k Posts

  M

  @MajorP93 Last Message from Veeam: Veeam Support - Case # 08187386 thank you for your email! We are currently waiting for R&D team conclusion, and a bit more time is required for the investigation. I am sorry for the possible inconveniences here! Best regards, Viktoria Nesmiyanova Technical Customer Support - EMEA Veeam Software
• 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)