Categories

  • All news regarding Xen and XCP-ng ecosystem

    146 Topics
    5k Posts
    gduperreyG
    We have just released security updates for xen and blktap. Full details are available on the blog: https://xcp-ng.org/blog/2026/10/13/october-2026-security-updates-2-for-xcp-ng-8-3-lts/

  • Everything related to the virtualization platform

    1k Topics
    16k Posts
    C
    Hello! I have a very weird problem/bug! A while ago I imported the Homeassistant VMDK via XOA and stuffed it into an (Generic Linux UEFI) VM. It booted and runs flawlessly. Everything works - except backup via Commvault! Commvault fails reporting the VM could not be found. Support found the following inside the logfiles: 4116 1984 05/01 21:00:29 58533 VSDisc::ProcessContent_VM() - virtual machine is not found using Name. Searching using both Name [HomeAssistant] and GUID [c3e276ed-1922-08a5-7f95-8b2d630e84ff] 4116 1984 05/01 21:00:29 58533 CXenSDKWrapper::GetVMInfoForVM() - Error:Getting VM information failed.Die Eingabezeichenfolge hat das falsche Format. 4116 1984 05/01 21:00:29 58533 VSDisc::ProcessContent_VM() - virtual machine: [c3e276ed-1922-08a5-7f95-8b2d630e84ff] discovery failed I assume "Die Eingabezeichenfolge hat das falsche Format." would be "The (input) string has the wrong format" in english. What I can: Discover the pool and select the VM to be taken into a backup job. So it somehow can see it, but it can't when running the actual job. Here's where things go really weird: I've spend quite some time, trying to narrow it down to a root cause. I've tried different VM templatesm, changed names and removed characters etc. Then I've interchanged the VDI with another VMs. Surprise: When I've interchanged HAOS VDI with a Debian Linux VMs OS VDI, the VM that cannot be backed up follows HAOS. Means: Now The VM named "Homeassistant" is found and backed up, but the VM called Debian-Test is not. So it turns out: Whenever a VM has booted HAOS, it can't be found during backup-discovery anymore. If it booted a "standard" Debian, the same VM is found again - until I change back to HAOS VDI. The support was clueless and we decided that I should try it over here: It looks like HAOS has to change something at the VM "skeleton" / metadata, that it can't be found otherwise. But how do I debug that further? How to find the difference and what exactly happens when it boots/runs? Greetings Christof

  • All Xen Orchestra related questions/reports

    3k Topics
    29k Posts
    julienXOvatesJ
    Just discussed this with @nathanael-h; I would strongly recommend using the load balancer plugin in XO and create some VM-to-host affinity rules, so that your CP VMs are running on different hosts ! So when the RPU comes you would have minimum impact.

  • Our hyperconverged storage solution

    55 Topics
    827 Posts
    C
    @poddingue Hi, we have a ticket at Vates regarding this. (Ticket#7765809)

  • Non-English speakers

    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.