Categories

  • All news regarding Xen and XCP-ng ecosystem

    146 Topics
    5k Posts
    B
    @vxgmichel Installed on my usual test pool. Set disks of a FreeBSD VM to CBT. Migrated the VM from NFS to iSCSI storage. Started Delta Backup Job. No issues except the backup was a full backup for this VM instead of a delta. Followed up with a second backup which then was a delta backup again. No issues with either backup.
  • 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
    J
    I usually work alot in different tabs. And a couple of times now, when I'm trying to use XO6, I've noticed that the "eye"-sidebar stops working. Scenario: Steps to reproduce behaviour I have the "eye" open looking at backup logs from Tasks-pane. Open another tab, I go to a VM and click on the Backup section. This closes the "eye" in the first tab in Tasks. And the "eye" icon no longer works. Reloading Tasks-tab will restore functionality. Bonus behaviour: Split from above 3. Click on the "eye" in VM/Backups-tab. And the sidebar will open for both tabs. You can now close the sidebar from Tasks-tab, and Backups-tab will no longer open the eye-sidebar.
  • 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.