Categories

  • All news regarding Xen and XCP-ng ecosystem

    146 Topics
    5k Posts
    A
    @vxgmichel @lmolina Pools updated, working so far. Rolling reboot failed because of backup (CR) conflicts. CR backups cause RPU to fail. RPU causes CR backups to fail.
  • Everything related to the virtualization platform

    1k Topics
    16k Posts
    S
    @yannsionneau Is it going to be a long time before iGPU PoC packages are ready to be included in the standard XCP-ng update packages?
  • 3k Topics
    30k Posts
    poddingueP
    @tjkreidl has it right, I think: the host and the XO VM each keep their own clock, so both of them need a working NTP source. The page he means is probably this one: https://docs.xcp-ng.org/management/hosts-pools#time-synchronization-ntp. There are two older threads with this warning, and in both it seems to have come down to one side not reaching any NTP server, once because NTP was never set on the host (https://xcp-ng.org/forum/post/86396) and once because DNS broke after an update (https://xcp-ng.org/forum/post/97429). Could you run chronyc sources on the host and timedatectl on the XO VM right after a reboot, and tell us whether you're on XOA or XO built from sources? Olivier mentioned in one of those threads that XOA comes with an NTP client while a from-sources install leaves that part to you, but I'm not sure that alone explains why it shows up after every reboot.
  • Our hyperconverged storage solution

    57 Topics
    844 Posts
    C
    @poddingue said: Do your hosts have public IP addresses on their management interface? I'm asking because the XOSTOR docs carry a warning about that setup (here) : according to them, the LINSTOR satellites listen on port 3366 without authentication, and an outside party can connect to them and get in the way of the real controller. If yours are reachable from outside, I think a different address each time would fit that, but I haven't checked it against a setup like yours. Thanks for offering to keep the cluster in that state for a bit. I'd point @Team-Storage at it before you reboot anything, since they're much better placed than me to say what's worth collecting. Does it look like you need to examine anything? I'm okay keeping it as-is for another day or two, but it would be good to know.
  • 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.