Categories

  • All news regarding Xen and XCP-ng ecosystem

    146 Topics
    5k Posts
    stormiS
    @Andrew said: @vxgmichel Update installed and running. Rolling pool reboot failed waiting to evacuate an empty host, I can't blame the update. Interesting. Worth a report to XO team?
  • Everything related to the virtualization platform

    1k Topics
    16k Posts
    poddingueP
    For the partitioning part, the docs say NVIDIA vGPU isn't supported on XCP-ng, since it depends on a proprietary XenServer component that can't be redistributed: https://docs.xcp-ng.org/compute#vgpu. So as far as I can tell, the "20, 40 or 80 GB per VM" split won't work through vGPU. Passing a whole GPU to one VM is the documented path, on the same page. I haven't seen anyone report on H100 or H200 cards here, though, so I can't tell you if that class of card brings its own surprises. There's also a blog post doing LLM inference that way on a much smaller Tesla T4: https://xcp-ng.org/blog/2025/07/28/your-own-gpu-powered-llms-with-xcp-ng/. There's an open design discussion upstream in XAPI about GPU partitioning, MIG included (https://github.com/xapi-project/xen-api/pull/7260), but that's the XenServer side, and I don't know if or when it would reach XCP-ng. As GPU partitioning matters for your project, it might be worth opening a request on https://feedback.vates.tech/ with what you described here (H200s, LLM inference, several tenants per card, fixed VRAM per VM). From what I've seen, a concrete use case like yours carries more weight there than a plain "please support vGPU", and other people needing the same thing can vote on it.
  • 3k Topics
    29k Posts
    poddingueP
    My guess, and I'm not an AD person so take it lightly: sAMAccountName holds the short login (jdoe), while userPrincipalName is the jdoe@yourdomain form. So if you typed the full address in the Test box, the first filter would find nobody. Was that the case? The docs list both filters but don't really say when to pick which: https://docs.xen-orchestra.com/users-and-access/users#ldap. On the logging, if I read the plugin code right, it already logs how many entries the filter matched at debug level, it's just that the Test button only gives back "could not authenticate user". Showing that in the UI sounds like a good one for https://feedback.vates.tech/, where the XO team tracks this kind of request.
  • Our hyperconverged storage solution

    55 Topics
    831 Posts
    Maelstrom96M
    @dthenot Do we have a fix yet?
  • 37 Topics
    137 Posts
    S
    @jqueiroz said: Bom dia a todos, Estou com um problema em uma VM, ela está ligando/desligando sozinha, repetidamente. Não encontro nenhuma mensagem de erro explicando o motivo. Alguém pode me dar alguma dica sobre como solucionar isso? Uso o XCP-NG 8.0 em um cluster de dois servidores HP Proliant DL-360, com o HA-Lizard. Tudo vinha funcionando bem até alguns dias atrás, quando houve uma queda de energia no datacenter da localidade. Tenho o mesmo arranjo de VMs/servidores em mais seis localidades, nenhuma apresenta esse problema. Analisar esse comportamento instável do cluster é quase como prever resultados complexos, parecendo a análise de riscos que a malta faz ao dar palpites no https://mostbetbrasil.lat. Grato. Como o problema começou depois da queda de energia e só acontece nessa localidade, eu começaria verificando os logs do XCP-ng e do HA-Lizard para entender quem está disparando os reinícios. Pode ser alguma política de HA tentando recuperar a VM repetidamente, algum problema de armazenamento ou até inconsistência no estado do host após a interrupção. Também vale conferir o estado do pool e os logs do Xen Orchestra, se estiver usando. Se possível, desative temporariamente a automação de recuperação dessa VM, com cuidado para não comprometer a disponibilidade, e veja se ela continua reiniciando sozinha. Isso ajuda a isolar a causa.