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
    C
    Coming from here: https://github.com/xcp-ng/xcp-ng-org/pull/566 All installations stopped listing the PV tools ISO. It has always been a "separate SR", that could be selected as "CD ROM". With the installation of 8.3 - no matter of Upgrade or fresh installatin - it's not showing up anymore. The thread shows, that the images are still included, but neither XO Lite nor XCP-ng Center shows them: # xe sr-list is-tools-sr=true uuid ( RO) : 7521974c-9c5c-a13a-ea73-f7bb75f6c493 name-label ( RW): XCP-ng Tools name-description ( RW): XCP-ng Tools ISOs host ( RO): xcp-xxx type ( RO): iso content-type ( RO): iso # xe vdi-list sr-uuid=7521974c-9c5c-a13a-ea73-f7bb75f6c493 uuid ( RO) : f80266a9-3df9-4656-a86b-3e872254488f name-label ( RW): guest-tools.iso name-description ( RW): sr-uuid ( RO): 7521974c-9c5c-a13a-ea73-f7bb75f6c493 virtual-size ( RO): 25679872 sharable ( RO): false read-only ( RO): true uuid ( RO) : 95596409-0716-4dae-8fd7-a6a0b2a9eb00 name-label ( RW): Old version of guest-tools.iso name-description ( RW): sr-uuid ( RO): 7521974c-9c5c-a13a-ea73-f7bb75f6c493 virtual-size ( RO): 20066304 sharable ( RO): false read-only ( RO): true [image: grafik.jpeg] [image: grafik.jpeg] So it seems to be a bug.
  • 3k Topics
    30k Posts
    poddingueP
    @blueh2o I think the two things you saw fit together, at least going by what I see in the mirror code. The 1 differencing tag only says that this one backup's disk is a delta, which is normal for an incremental; the key sits further back in the chain, which I think is why the health check could still rebuild the whole ~280 GiB disk. And as I wrote a few posts up, the mirror reads the parent of each delta on Ark and then asks each target whether it already has it, so last night's error would mean the Synology is missing d08f1acc for that one VM (fb7fca7d), not that Ark is broken. That brings us back to Florent's suggestion from the older thread, deleting that VM's most recent backups on the Synology so they get sent again, though I can't tell you why the Synology lost that base in the first place. At least it's down to one VM out of 56 last night, against 16 in October.
  • 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.