Categories

  • All news regarding Xen and XCP-ng ecosystem

    145 Topics
    5k Posts
    stormiS
    @mthird said: Spoke to soon. While the updates succeeded, one of the nodes is rebooting every few minutes due to an HA self-fence. Could you open a dedicated thread and ping me there?
  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    AtaxyaNetworkA
    Hello everyone ! I rebuild a new OME appliance with the latest version (4.7) What i did on the rebuild: Via live CD add xen-blkfront and xen-netfront driver, and rebuild the initrd change root password activate SSH. Via TUI Change admin password Set interface to DHCP Via SSH sed -i -e 's/sda/xvda/g' /opt/dell/omc/utilities/tui/bin/ome_disk_config.sh sed -i -e 's/sda/xvda/g' /opt/dell/mcsi/appliance/scripts/appliance_resources.sh bash /mnt/Linux/install.sh # To install XCP-ng tools As usual, please send a DM if you want the link to the VHD Also, if you want to build it yourself, the driver are here https://cecilemorange.fr/drivers/xen-netfront.ko https://cecilemorange.fr/drivers/xen-blkfront.ko Feedback is welcome ! (Disclamer: This build is something I create on my free time and to help people who have difficulty running Dell appliances on XCP-ng. I do not guarantee a fully functional appliance, but I do my best to make it work. If you have a support contract with Dell and require official support for OME, please contact Dell and request compatibility with XCP-ng.)
  • 3k Topics
    29k Posts
    acebmxerA
    install_xen_orchestra v0.5.0 — build your own cloud-init VM templates As I am sure most of you know that XOA Hub is not accessible from Xen Orchestra from sources. So v0.5.0 of my install script adds a VM Template Library — a new --build-templates flag (and menu entry) that builds the equivalent on your own pool, from each distribution's own published cloud image. ./install-xen-orchestra.sh --build-templates It runs from your workstation over SSH against the pool master, like --deploy does. Nothing is installed locally and your XO install isn't touched. What you get A sealed template that shows up next other vm templates you have, with: cloud-init — supply an SSH key or a full cloud-config at VM creation. XCP-ng guest tools, installed from guest-tools.iso on the pool. Without these XO never reports the VM's IP. On Debian 13 there's no xe-guest-utilities package, and a failed package install doesn't stop cloud-init, so an apt-first approach silently gives you a template that looks fine and is useless. The ISO is what the XCP-ng docs prescribe anyway. A scrubbed identity — machine-id, SSH host keys, cloud-init state and logs are all wiped before sealing, so clones don't collide on DHCP leases or share an SSH fingerprint. growroot, so the disk size you ask for at creation is actually filled. One template for both BIOS and UEFI — the Debian generic images carry an ESP and a BIOS boot partition, so you just flip "Boot firmware" in XO's advanced settings. The build itself isn't prompted for storage or network — it uses your pool's default SR (or the emptiest one, if you haven't set a default) and the management network. Both are just build-time choices; you pick whatever you want when you actually create a VM from the template. Images are pulled from the distribution's own mirror (nothing redistributed), downloaded onto the pool master so the ~3 GB never crosses your workstation's link, and verified against the origin's published SHA512SUMS at build time —so new upstream releases get picked up without me editing anything. Allow roughly five to ten minutes per template; it has to boot the VM once to install the guest agent and run the scrub. Distros Debian 13 (Trixie) is the only one for now. That's a starting point, not the limit — the catalogue is a table with one row per distro, and adding another is a row in that table, not a change to the build. So: comment here if there's a specific distro you'd want to see sooner rather than later and I'll prioritise accordingly. Repo: https://github.com/acebmxer/install_xen_orchestra Docs for this feature: https://github.com/acebmxer/install_xen_orchestra/blob/main/docs/templates.md
  • Our hyperconverged storage solution

    51 Topics
    798 Posts
    poddingueP
    Before anything else, could you post rpm -q sm from one of the hosts? A batch of LINSTOR fixes landed in sm 3.2.12-23.1 back in July, and two of them sit in the path your error comes out of: one stops it loading VDIs during VDI.deactivate, and another changes when the GC gives up if a VHD chain is still open. I'm reading patch names out of the changelog rather than the patches themselves (way out of my league), so I honestly don't know whether they touch your case, but the version is the cheapest thing to rule in or out first. If you're already on that one or later and still hitting this, let us know, because being up to date and still broken is a different problem from being behind. Either way, probably worth pulling in @Team-Storage.
  • 37 Topics
    136 Posts
    J
    @AtaxyaNetwork Merci pour tes recherches ! Oui "cd_label" serait cool comme ajout au plugin ce qui permet sur les distro type Fedora/Redhat de ne pas avoir de boot_command à gérer