1. Home
  2. XCP-ng

Subcategories

  • All Xen related stuff

    603 Topics
    6k Posts
    bvitnikB
    @hitechhillbilly I'd say this is normal if you are low on RAM and you are doing a live VDI migration. XCP-ng requires some amount of free RAM on the host to be able to live migrate the VDI. The larger the VDI, the more RAM is needed but exact sizing is unknown to me. I've encountered this error numerous times so I consider it common. The way around this is to shutdown the VM and then migrate the VDI. RAM requirements in that case are much much lower.

  • The integrated web UI to manage XCP-ng

    26 Topics
    348 Posts
    olivierlambertO
    It's not meant to be used like that. If you are behind a NAT, the right approach is to have your XOA behind the NAT and inside the same network than the hosts. That's because hosts will always use and return their internal IPs to connect to some resources (stats, consoles etc.). XOA deals with that easily as being the "main control point" for all hosts behind your NAT (or a XO proxy if you prefer).

  • Section dedicated to migrations from VMWare, HyperV, Proxmox etc. to XCP-ng

    110 Topics
    1k Posts
    L
    @olivierlambert Thanks for the tip — it’s a very interesting mechanism. I’m going to read the docs now

  • Hardware related section

    144 Topics
    1k Posts
    D
    hardware_report_2025-12-12_17-20-47.txt lspci.txt mlx.txt pci.txt Diagnostic logs

  • The place to discuss new additions into XCP-ng

    244 Topics
    3k Posts
    F
    @dinhngtu Thanks. We plan to migrate all Windows VMs from the Citrix tools down the road and only have a handful of VMs running these so far so will maybe hold off until the next version. Have been running the Linux rust tools for over a year with zero issues..
Log in to post
Load new posts
  • I

    DC topology info

    11
    0 Votes
    11 Posts
    1k Views
    I
    @bleader yes, Thank you.
  • W

    Beginner advice - coming from Debian

    8
    1 Votes
    8 Posts
    1k Views
    D
    @WillEndure said in Beginner advice - coming from Debian: @DustinB @DustinB said in Beginner advice - coming from Debian: Why are you keen on keeping raw XEN on Debian? Not committed to the idea - its just what I currently have and invested a bit of time into setting it up and understanding it since before XCP-ng was around. Time is a factor too because you can waste a lot of it setting stuff like this up! But overall yes, I should probably move over to XCP-ng for my host. Got it, sunk-cost fallacy.
  • A

    Copying a VM from 8.2 to 8.3 and back

    2
    0 Votes
    2 Posts
    358 Views
    stormiS
    I think this part of the doc describes your issue: https://docs.xcp-ng.org/releases/release-8-3/#a-uefi-vm-started-once-on-xcp-ng-83-cant-start-if-moved-back-to-xcp-ng-821
  • S

    Unable to find logs in XenCenter or Xen Orchestra

    Solved
    5
    0 Votes
    5 Posts
    656 Views
    S
    @olivierlambert thanks i got it.
  • E

    PCIe card removal and failure to boot from NVMe

    Solved
    14
    1 Votes
    14 Posts
    2k Views
    olivierlambertO
    Okay weird, at east glad to know it works now
  • X

    how to use template created in another host machine?

    2
    0 Votes
    2 Posts
    147 Views
    olivierlambertO
    If the machines are on the same pool no problem. If they are not, you need to export the template and import it in the other pool.
  • I

    Openstack vs xcp-ng (XO)

    3
    0 Votes
    3 Posts
    569 Views
    I
    @olivierlambert got it.
  • A

    XCP-ng host - Power management

    11
    2
    0 Votes
    11 Posts
    2k Views
    A
    @tjkreidl We don't need performance, but we do need to test how XCP-ng pools, networking, migration, live migration, backup, import from VMware and so on work. It's just a playground where we can have relatively many XCP-ng hosts, but it's not about performance, it's about efficiency and low requirements, because it's just a playground where we learn, validate how things work, and prepare the process for the final migration from VMware to XCP-ng. We originally had two R630s ready for this, then 4, but that would have been unnecessary, given the power consumption, to have physical hypervisors, so in the end we decided to virtualize it all. Well, on ESXi it's because XCP-ng works seamlessly there in nested virtualization.
  • S

    XenServer VM Fails to Start - HeadersTimeoutError & Hotplug.Device_timeout(_) After Power Outage

    8
    1 Votes
    8 Posts
    1k Views
    S
    @spcmediaco FYI, I never figured out how to fix. I am doing backup recovery now.
  • S

    Backup fails with "Body Timeout Error", "all targets have failed, step: writer.run()"

    8
    0 Votes
    8 Posts
    1k Views
    julien-fJ
    @Bambos A timeout error means that the host did not reply in the expected delay, which, if I'm remembering correctly is 5 minutes. I suspect a problem on your host but we will take a look further on your support ticket.
  • T

    GRUB waits for confirmation

    8
    0 Votes
    8 Posts
    1k Views
    J
    @techknowbabble said in GRUB waits for confirmation: What did finally work was re-installing with the 'no serial' option and everything seems to be working as expected now. I only have a handful of XCP-NG installations under my belt but I wonder if this is a known bug or if anyone else has had a similar experience. It's not something I've ever seen before and I've done quite a few installations but I can think of some possibilities as to why something like that might fix the problem. My best guess is that there's something built into, connected to, or otherwise in your system that looks like a serial port (maybe even a real serial port) that spits out a character or two into the system at boot time, confusing GRUB and stopping the normal boot process. The bad KVM I mentioned before was doing something like that, throwing a bogus keypress into the system at boot time.
  • P

    Wide VMs on XCP-ng

    13
    0 Votes
    13 Posts
    2k Views
    planedropP
    @plaidypus Ah gotcha, this makes sense. I second scaling out instead of up. If you're getting new hosts, I'd also keep in mind newer CPUs do have much higher per core performance (not sure what your current stuff is), so you also might be able to get away with less vCPUs and lower likelihood of NUMA spanning. Either way though I think scaling out is the better direction to go.
  • S

    This topic is deleted!

    1
    0 Votes
    1 Posts
    4 Views
    No one has replied
  • H

    VM cannot be migrated after NICs of one host died

    Solved
    5
    0 Votes
    5 Posts
    492 Views
    DanpD
    @hansve You're welcome.
  • K

    block tdc: sector-size: 512/512 capacity: 20938752

    3
    0 Votes
    3 Posts
    389 Views
    K
    @apz I see. Thanks.
  • R

    Server Locks Up Periodically with ASRock X570D4I-2T AMD Ryzen 9 3900X and Intel X550-AT2

    21
    0 Votes
    21 Posts
    4k Views
    daveD
    @R2rho yeah, there are Supermicro systems with AM5 which can handle a decent amount of load, like based on the h13sae-mf, like: https://www.supermicro.com/de/products/system/mainstream/1u/as-1015a-mt (with less depth) Seem to be stable, but we have a small issue regarding onboard graphics ATM: https://xcp-ng.org/forum/topic/9976/black-screen-after-install-on-supermicro-h13sae-mf-with-ryzen-9950x/3?_=1734419502978
  • D

    VM not booting after attaching GPU

    2
    0 Votes
    2 Posts
    247 Views
    DanpD
    You should start by checking the logs. https://docs.xcp-ng.org/troubleshooting/log-files/
  • K

    XCP-ng v8.3 Host Crashing Upon Console Login and Performing Any Action

    Solved
    6
    1
    0 Votes
    6 Posts
    457 Views
    bleaderB
    Thanks for letting us know, and I'm happy you have thing working nicely now. I think to mark this as resolved you need to convert your original post as a question, and it can then be marked as resolved. I actually cannot do it myself, I think only a few people have the permission to do it for others at Vates.
  • C

    Change VM RAM

    Solved
    6
    0 Votes
    6 Posts
    714 Views
    olivierlambertO
    Enjoy XO & XCP-ng then
  • C

    host time and xoa time are not consistent with each other

    Solved
    4
    1
    0 Votes
    4 Posts
    2k Views
    C
    @olivierlambert I resolved it, logged in the XCP-ng console and set the NTP servers to default. All good now. Thanks [image: 1733066154172-xcp-ntp2.png]