Categories

  • All news regarding Xen and XCP-ng ecosystem

    146 Topics
    5k Posts
    C
    @benapetr That's fantastic - thank you! Thanks @bvitnik for the better screenshots .
  • 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
    J
    I'm having very fun testing this out. And you've really got something with extreme potential here. And I am very impressed. Thank you! So far I've noticed a couple of things, both very small and medium in size. And I've tried to collect my initial thoughts below. v2v xo6 thought "next: mapping" is far down, when browsing "ALL". Could be remedied with placing it up at the top. With the header fixed at the top as well. Consider showing what networks are attached in the VM-list. Further suggestion could be to look into some smart-mapping. A simple (not saying the implementation would be easy, but the matching algorithm), that matches source-VLAN vs target-VLAN. Have a V2V settings page, where many defaults could be set. Examples are: Tags: Although you can click into each VM that is supposed to be migrated. Doing so for hundreds of VMs would be tedious very quickly. So an on-masse applying of tags would be great. (yes I'm aware there is a notice specifically about tags. Deciding what would be the active default. Such as example deciding if Docking and "Start the VM on XCP-ng" would be pre-checked or not (current default). Concurrent VMs Incorporate an option to set if a VM should be booted with BIOS or UEFI. Perhaps be able to match with vmware-source? When creating a migration, there is no way to discard already existing list, except for continuing with existing list and clear it inside. When a migration is underway. It would be nice if the migration task for that VM would show up under the Tasks-tab for that particular VM as well. Not just in the "Tasks-section for XO" Questions: When importing a VM. The task for that particular VM has a percentage counter for its import. This does not seem to work. So my question is, what is the percentage of completion based on?
  • Our hyperconverged storage solution

    56 Topics
    838 Posts
    poddingueP
    If I follow your excerpts, there are two different problems stacked here. One is the LinstorSR attach giving up on what looks like a one-second controller hiccup, which is the @Team-Storage side. The other is xenopsd leaving state behind on both hosts after the failed sync point 4, so that every later run trips over it. I think that half belongs to the toolstack people rather than storage, so I'm adding @Team-XAPI-Network too. I can't judge either part myself, so I'll leave it with them.
  • 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.