Categories

  • All news regarding Xen and XCP-ng ecosystem

    145 Topics
    5k Posts
    X
    Applied the latest candidate updates to my four-node pool home lab. The once or twice that I previously tried the RPU feature, it didn't work for me so have since performed the updates from the dom0 CLI followed by properly sequenced manual host reboots. (I'm happy to try RPU in any future update where correcting that functionality is a focus.) Post update, everything appears to be working well including live migration during which the VM is deliberately made busy e.g. Windows and Linux updates; taking and deleting snapshots and tailing the SMlog to see if any GC errors occur. (Didn't see any.) I also like the new XCP-ng VM firmware boot logo. That's a nice touch as it further emphasizes Vates' commitment to the platform from the firmware on up. That's good marketing! All in all, this looks like a solid set of updates.

  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    S
    Before today, I had XCP-NG 8.3 installed on the Metal of my server, and a LSI 3008 SAS Card going to a backplane, which was hidden in dom0 (Location 03:00.0, this is important), and passed through to a TrueNAS VM. No Issues, operated for years. Today, I installed a PCI to M.2 adapter, and to do so, I moved the LSI card to another slot, and put the M.2 adapter in the slot the LSI Card was in. Long story short, the new arrangement just made more sense to handle the bifurcation stuff needed. I booted XCP-NG, and TrueNAS reported that my Dataset was missing, but it saw the NVMe drive. Made sense once i checked a 'xe pci-list' , as the M.2 Adapter was now 03:00.0... Why it changed? don't know, I can't imagine that's an important detail. I saw the LSI 3008 card was on 05:00.0 I pulled the usual xe pci-disable-dom0-access uuid=<pci uuid> Reboot the host. And it throws me into the Emergency Shell... After Google searching I find the google page about "Initrd is missing after an update" The weird part here is that the Emergency Shell is NOT reporting "/boot/initrd-4.19.0+1.img is missing" The Error I get is "Warning: /dev/disk/by-label/root-lfgrma does not exist" For thoroughness, I did load into the fallback kernel, and it loaded fine... Not sure where to go from here though. For testing purposes, I did attempt to Rebuild the initrd with 'dracut -f /boot/initrd-4.19.0+1.img 4.19.0+1' even though the error wasnt saying the img was the issue... but wanted to make sure A restart throws it back into the emergency shell. Any advice would be appreciated Any questions, I will gladly answer... I'm stumped

  • All Xen Orchestra related questions/reports

    3k Topics
    29k Posts
    C
    Hello @poddingue and @Team-XAPI-Network is there anything else to check?

  • Our hyperconverged storage solution

    50 Topics
    796 Posts
    olivierlambertO
    Great, thanks for the feedback!

  • Non-English speakers

    37 Topics
    135 Posts
    AtaxyaNetworkA
    Pour l'ISO montée deux fois : My bad, j'ai ajouter un truc en trop sur mon précédent fix. Une PR est en cours pour corriger ça. Pour le problème principal : J'ai identifié la cause, mais je n'ai pas encore de solution. Sans les drivers Xen (non initialisés avant l'installation), une VM est limitée à 4 périphériques. La séquence de boot ne peut donc pas détecter le second disque contenant le fichier Kickstart (ks). Côté Packer, on semble être bloqués par cette contrainte XCP-ng. Les seules alternatives actuelles seraient de se limiter à : 2 disques + 2 CD ou 3 disques + 1 CD + HTTP (Note : L'installation manuelle fonctionne car l'installateur démarre directement, avec le driver xen_blkfront, alors qu'avec Packer, l'injection de notre fichier interrompt le flux de démarrage classique). Je vais fouiller encore un peu, mais sans certitude d'un contournement possible. (et je regarde pour ajouter le CDlabel)