Categories

  • All news regarding Xen and XCP-ng ecosystem

    146 Topics
    5k Posts
    C
    @benapetr That's great - thank you for clarifying - really looking forward to the next release!
  • Everything related to the virtualization platform

    1k Topics
    16k Posts
    okynnorO
    I have a nasty problem of my own creation. I hope the community can help me as I have a lot of data stored in this iscsi repository. It all started because my hardware RAID had failed on my Dell PowerEdge R630. I decided to restart the server. It didn't fix the problem, of course. But the server did work with just one 1 remaining drive. Thinking that I need to rebuilt the RAID array, I put two new SSDs in and proceeded to format them to use Software RAID (after setting HBA & ACHI on then PowerEdge). No problem...the reinstall went well. Now, when I tried to reattach the iScsi repository, it showed me that there was "No Storage Repository Detected". I then went to the Terminal in XCP-NG to run the following command to see if the iscsi repository was still available (I didn't reformat the repository) [17:31 xenserver-tiger ~]# iscsiadm -m discovery -t sendtargets -p 192.168.1.5 192.168.1.5:3260,1 iqn.2005-10.org.freenas.ctl:scuzzy-ng2 172.16.0.1:3260,1 iqn.2005-10.org.freenas.ctl:scuzzy-ng2 [17:31 xenserver-tiger ~]# That would tell me that the repository still exists (I think) I've tried every thing that I can think of to reconnect them. I do not want to lose all my VMs that are inside that iScsi repository. Is there a way to reattach them from the Terminal? Other things d
  • 3k Topics
    30k Posts
    T
    If Xen Orchestra backup report displays an 'INTERRUPTED' status and the web console says clean completions, this often mean there’s a lag in syncing asynchronous metadata. This occurs when the underlying backup job finishes writing VM disk blocks, but the post-backup cleanup hook or secondary storage health-check times out before the notification worker receives confirmation from the remote storage target. The reporting engine inside xo-server dispatches status emails based on strict task completion timeouts. If your backup storage repository takes extra time to coalesce snapshots or update remote NFS metadata indexes, the notification daemon flags the overall job as interrupted even though your virtual machine images remain completely intact. To verify actual mail backup integrity, inspect the raw log stream via xo-cli backup.listLogs or review your xo-server system logs with journalctl -u xo-server. You will likely find that the disk transfer succeeded with zero dropped blocks, while only the final ping event was delayed. When managing critical infrastructure, chasing ambiguous email reports is time wasting. If you require an airtight mail backup tool to archive and organize all infrastructure alert notifications across multiple monitoring systems, Mail Backup X really delivers. It automatically backs up incoming data, encrypts archives locally, and maintains records with high-speed search across all correspondence and attachments.
  • 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.