Categories

  • All news regarding Xen and XCP-ng ecosystem

    146 Topics
    5k Posts
    acebmxerA
    @vxgmichel Big update... Installed on Intel 13th gen and 14gen cpus CBT was already enabled on vms prior to update. 2026-11-19T19_42_40.762Z - backup NG.json.txt - After update - regular incremental backup 2026-11-19T19_46_25.835Z - backup NG.json.txt Migrated 1 vm from nvme SR QCOW2 format to hdd SR QCOW2 format and did another incremental backup.
  • Everything related to the virtualization platform

    1k Topics
    16k Posts
    poddingueP
    I haven't tried Duo on a host myself, so this comes from reading an 8.3 dom0 rather than from experience. The first thing I'd watch is that XAPI checks the root password through PAM as well. /etc/pam.d/xapi just includes system-auth, so my guess is that a Duo module placed in system-auth would make every password login to XAPI (XO's connection to the pool, xe -pw, XO Lite) ask for a factor it can't give. The physical console is less simple than it looks too: tty1 runs xsconsole, and on my 8.3 host it checks root against the password-auth PAM service by handing over just the password, so I'd expect a module that asks a second question to make that login fail rather than prompt. Also worth knowing before an audit: software from outside the XCP-ng repos isn't supported in dom0 (https://docs.xcp-ng.org/installation/requirements), and as far as I can tell from rpm, /etc/pam.d/xapi isn't marked as a config file, so an update would put it back. Anyone who has been through this for real will know more than me.
  • 3k Topics
    30k Posts
    B
    And the health check passes. How can that be possible? { "id": "0mwnnmk6y-jd7jumsiui", "start": 1795099050682, "status": "success", "updatedAt": 1795103578854, "tasks": [ { "id": "0mwnnmmmn-jvm3zflms38", "start": 1795099053839, "status": "success", "end": 1795103578854, "result": { "size": 302621130752, "id": "b656b0d4-b575-c805-5738-6fd50d150951", "liveMounts": [] }, "message": "transfer" } ], "end": 1795103578854, "result": { "size": 302621130752, "id": "b656b0d4-b575-c805-5738-6fd50d150951", "liveMounts": [] }, "message": "restore", "data": { "backupId": "dc0a417c-e1cb-4b4b-8fd9-d59e2564999f//xo-vm-backups/fb7fca7d-7355-4a48-f35c-d32c8dfa71ee/20261119T051216Z.json", "jobId": "73d695c7-901b-45bd-94ba-f38682705d35", "srId": "caba922c-ac32-67e8-f83b-a5907d880179", "time": 1795065136373 } }
  • Our hyperconverged storage solution

    57 Topics
    843 Posts
    C
    @ronan-a said: @ccooke As said by @poddingue , your network is not isolated. You must change that to protect your pool. We are aware of this issue and we will change this behavior in a future release to block LINSTOR controller and satellite access from the outside (probably in December). Also we will use TLS to add another security layer. Right. I missed that warning - I was going from https://xcp-ng.org/forum/topic/5361/xostor-hyperconvergence-preview which doesn't look to link to the XOSTOR documentation with the warning. Does this need a full reinstall effectively, or can I recover it? I see the warning is you can't have hypervisors with any public IPs - that will need a little re-engineering for my small test cluster. I know you can change the IP addresses for linstor after installing xostor - does that resolve the issue, or is there no way to secure it when the hypervisor is on a public IP? Could I not just add some firewall rules for now? Thanks for the reply.
  • 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.