Categories

  • All news regarding Xen and XCP-ng ecosystem

    143 Topics
    5k Posts
    X
    Installed latest updates on my four host home lab pool and a fifth standalone host with no apparent issues.
  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    E
    Wearing my best Lazarus cosplay outfit, I'll apologise for the resurrection. Today I had an issue with my UPS which caused me to reboot XCP a few times. During those reboots I had at least 2, maybe 3, re-occurrences of this where when TrueNAS was booting, XCP would lock up. Most of the time, after a power cycle of the server, the next boot would start TRUENAS cleanly. One time it took 2 power cycles before success. Unfortunately only one of the crashes resulted in a /var/crash report, but that did have the same symptoms as my original report: (XEN) [ 81.101362] Non-responding CPUs: {24-47} (XEN) [ 81.101363] (XEN) [ 81.101364] **************************************** (XEN) [ 81.101365] Panic on CPU 5: (XEN) [ 81.101366] FATAL TRAP: vec 2, NMI[0000] IN INTERRUPT CONTEXT (XEN) [ 81.101366] **************************************** (XEN) [ 81.101367] (XEN) [ 81.101368] Reboot in five seconds... (XEN) [ 81.101369] Executing kexec image on cpu5 (XEN) [ 82.101441] Failed to shoot down CPUs {24-47} Between my original report and today, I have rebooted other times, following updates, when this issue has not surfaced. Does anyone think this could be hardware related, despite all the memory testing and stress testing I did when I built the server and again after the original issue, all with no faults. Or have I just got an unlucky set of circumstances with some sort of race condition.
  • 3k Topics
    28k Posts
    itservicesI
    Hi @pierrebrunet. I have deleted the "parentless" VDIs and snapshots. So the "Unhealthy VDI" page is empty for me. So everytime I retry with the VM in question it is creating a new (full) backup-chain. Regards, Marc
  • Our hyperconverged storage solution

    47 Topics
    755 Posts
    poddingueP
    Thanks for coming back to close it out. That's useful to know. So I was plenty wrong, as it was the XOSTOR licensing backend rather than the repo side I guessed at; those -32000 errors really don't give much away. For anyone landing here later: sounds like -32000 on XOSTOR creation can come from either end, a licensing/entitlement issue that support sorts, or a host not reaching the package repo, so both are worth checking. @alcoralcor, did support get yours sorted too, or is yours still the repodata / repo-reachability one? Glad you're unblocked either way.
  • 35 Topics
    113 Posts
    olivierlambertO
    Ah excellente nouvelle Je passe le sujet en résolu !