Subcategories

  • All Xen related stuff

    616 Topics
    6k Posts
    A
    @laszlobortel we've seen far less of this issue since my last message, not sure what made it better and when. But we're still making sure to reboot monthly (during patching, as we normally do anyways) + after live migration, and that helps. We don't use load balancing, so once a VM is staying put on one hypervisor, there is no issue. Live migration and time triggers the issue for us. What changed in our infra is upgrade to XCP-NG 8.3 and moving to XOSTOR as shared storage. We've seen no issue with AlmaLinux 9 and CloudLinux 9 at all. They also perform better I/O wise.
  • The integrated web UI to manage XCP-ng

    29 Topics
    369 Posts
    acebmxerA
    @pdonias confirmed... [image: 1780065202934-screenshot-2026-05-29-103255.png]
  • Section dedicated to migrations from VMWare, HyperV, Proxmox etc. to XCP-ng

    126 Topics
    1k Posts
    C
    Hi, everyone Thank you for your help. I had a flux that was blocked by our firewall. The button worked after that. But it doesn't explain why I lost this configuration and had to reinstall it. Thanks again.
  • Hardware related section

    169 Topics
    2k Posts
    poddingueP
    That leftover NIC is probably a stale PIF that XAPI is still holding, even though the card is physically gone, and the Refresh button re-scans rather than removing it. The docs have proper "remove a physical NIC" steps that end in forgetting the old PIF with xe pif-forget: https://docs.xcp-ng.org/networking/#remove-a-physical-nic. For the GPU side, the PCI passthrough flow (hiding the device from dom0, then assigning it) is here: https://docs.xcp-ng.org/compute#detaching-a-pci-device. If the GPU still won't show up as assignable once the stale PIF is gone, it might be worth a mention to @Team-Hypervisor-Kernel.
  • The place to discuss new additions into XCP-ng

    253 Topics
    3k Posts
    nathanael-hN
    @pszelestey Hi, yes, we've pushed an initial commit and a few more here https://github.com/vatesfr/cluster-api-provider-vates/ it is moging every day. Ping us in Matrix/Discord devops if you want to chat live while trying
  • Pool Master unreachable

    8
    0 Votes
    8 Posts
    2k Views
    S
    @sushant-diwakar
  • Issues with PCIE Passthrough

    20
    0 Votes
    20 Posts
    6k Views
    J
    @ImThatFluffy said in Issues with PCIE Passthrough: @john-c Yea im not sure, it was either an issue with the way I had Debian setup or compatibility things booted up Ubuntu 22.04LTS with the HWE kernel and it worked perfectly. Well if you are using Ubuntu Linux 22.04.1 LTS or one of the later point releases then it would be using a Linux Kernel version 6.1 or later, when its a HWE kernel. So any bugs from earlier versions of the kernel would have been fixed, also the Intel ARC graphics hardware would have been released during one of the point releases. On the Debian Linux front a distribution version earlier than version 12.0 would have been unlikely to have complete properly functioning support, due to that release being the first one with the Linux kernel version of 6.1 or later.
  • Imbedded Docker

    docker container xcp-ng
    12
    0 Votes
    12 Posts
    9k Views
    S
    @DustinB said in Imbedded Docker: Has anyone else done this, and can provide benefits or faults in doing so, besides the obvious that this isn't officially supported? I am actually going through the process of trying this right now, and am having significant difficulties with the xscontainer-prepare-vm piece - it doesn't work. So far, I have built a Docker VM, made sure all prerequisites are in there, and then run this script. It does insert an ssh-rsa key into my user's authorized_keys file, but the public key it inserts doesn't actually work. The host is not able to ssh into the VM due to the certificate not matching and requires a password, which does not work because it can't pass the VM check. Has anyone else seen this behaviour before?
  • Issues with Windows 11 VM

    5
    0 Votes
    5 Posts
    3k Views
    planedropP
    I've got passthrough to work a number of times without issue, the only thing I had to make sure of was that all devices related to the GPU were passed through completely. Are you following the docs step by step? I have a Ubuntu VM running with a 2060 passed through right now, works flawlessly and even survived a power loss on the host.
  • How do I/should I disable the local webserver

    Solved
    11
    0 Votes
    11 Posts
    3k Views
    J
    @olivierlambert Thank you. We'll be looking into it when we upgrade the hardware.
  • Inquiry Regarding XCP-NG Web UI Access Issue

    6
    1
    0 Votes
    6 Posts
    4k Views
    planedropP
    @ajpri1998 I agree in regards to XOA getting damaged somehow, so that makes sense. I think my question here to OP was more about why they're concerned with it if they already have XOA. Normally if something happens to XOA though you'd SSH into the XCP-ng host and figure it out from there (which also means XO Lite could be enabled). Not criticizing at all, just was curious about the use case here in specific since it's being evaluated for enterprise use.
  • windows 11 Support

    11
    0 Votes
    11 Posts
    14k Views
    Z
    Could someone who tried Win11 with the latest XCP-ng beta confirm if hibernation works?
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    1 Views
    No one has replied
  • Run a script inside guest OS from host

    22
    0 Votes
    22 Posts
    10k Views
    V
    Get Wendell to talk more about xcp-ng
  • Update strategy for a consistent XCP-ng pool

    8
    0 Votes
    8 Posts
    2k Views
    olivierlambertO
    Thanks, and also thank you for your feedback, it's important to understand the pain points to improve our product Keep us posted!
  • XCP : Server Failed

    7
    1
    0 Votes
    7 Posts
    1k Views
    olivierlambertO
    As a general rule, you MUST keep all your hosts up to date. If you update normally, you will be on a 8.2.1
  • VM Graceful shutdown using apc network shutdown

    6
    0 Votes
    6 Posts
    2k Views
    S
    @olivierlambert Ihave been tryign to get graceful power off to work with my nas whcih is Truenas by the way but i havent gotten it to work yet oddly i cant seem to get them talking yet
  • 0 Votes
    10 Posts
    2k Views
    D
    @Danp said in Patching and trying to Pool Hosts after they've been in production: Warm migration should work in this case because the VM is halted then restarted as part of the process. See here for more details. Sweet, I'll setup something small on the old host for testing and use the Warm Migration process.
  • Can not recover /dev/xvda2

    4
    1
    0 Votes
    4 Posts
    2k Views
    olivierlambertO
    There's no issue to restore everything from scratch, as long as your backup repo (BR/remote) is available. For example, fresh XCP-ng install, deploy XO, connect to the BR and it will find all your previous backups. Then restore, that's it!
  • Largest Stack?

    10
    0 Votes
    10 Posts
    2k Views
    D
    Now we have 76 VMs running on a 3 host pool. Each server has 320 GB of RAM. Our scenario doesn't need big CPU resources so everything works fine.
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    2 Views
    No one has replied
  • 0 Votes
    11 Posts
    3k Views
    RAG67958472R
    anyone has any other ideas ?? I seem to be lost at what to do.
  • VM Templates does choosing correct one matter?

    4
    0 Votes
    4 Posts
    1k Views
    planedropP
    @wilsonqanda Yes, BIOS as well, assuming I am remembering right haha. If you just pick whatever is closest and go with it I doubt you'll run into issues, if you do just make a post here and I'm sure someone will be willing to help out or work on a new template or something.
  • 1 Votes
    6 Posts
    2k Views
    A
    @wilsonqanda Downgrading the EKD2 package fix it for now, as posted: yum downgrade edk2-20180522git4b8552d-1.5.1.xcpng8.3
  • Add kernel boot params for dom0

    4
    0 Votes
    4 Posts
    3k Views
    stormiS
    The grub setup is rather simple and not very flexible. There's just one file to modify, as you found out (/etc/grub.cfg in BIOS mode, /etc/grub-efi.cfg in EFI mode, both being symbolic links to the actual file location). You can add an entry to it, but there's a small chance this doesn't play well with scripts from either XenServer or ourselves which may want to update the file and get confused. It's usually better to just modify the existing entries, ideally using /opt/xensource/libexec/xen-cmdline, so that the file structure remains unchanged.