Subcategories

  • All Xen related stuff

    612 Topics
    6k Posts
    P
    perhaps "in the context of a proceeding RPU, do not start halted VMs" ? or "boot only halted VMs that have HA enabled" ? but I can imagine corner cases where this is not wanted. some chicken & egg problem.
  • The integrated web UI to manage XCP-ng

    27 Topics
    354 Posts
    O
    Hi @olivierlambert and @pilow Thank you for your answers, it helps a lot, Regards, Olivier
  • Section dedicated to migrations from VMWare, HyperV, Proxmox etc. to XCP-ng

    123 Topics
    1k Posts
    kruessK
    Good moaning... The solution was pretty simple: a toolstack restart on the master (xcp83) did get all back on track and it now allows me to move the systems with a simple shutdown/start.
  • Hardware related section

    165 Topics
    2k Posts
    T
    @yannsionneau said: Can you retry with an up-to-date xcp-ng 8.3 please? FYI on recent XCP-ng 8.3 versions the pci-passthrough will enable the ROM expansion bar. The guest VM will have access to it, so no need to pass it via qemu anymore. See my comment on GitHub: https://github.com/xcp-ng/xcp/issues/786#issuecomment-4281846490 Regards, Yann I tried, yes. I confirmed as well on github that the patch does what it suppose to do - it exposes ROM BAR, but that alone is not sufficient to get our cards working. More in my other topic.. I believe it will still fix a lot of issues, and it could potentially fix amd gpu passthrough for some card, but not Phoenix, Raphael and this generation of Ryzen iGPUs (not sure specifically about Barcelo).. But it is a good progress anyway as I wouldn't be able to fix this ever on my own, so I am really glad it is done. Now I will probably get back to the topic and try to patch whatever else is needit and give it to people in a form of rpm package for the time being.. we will see, it is all about time
  • The place to discuss new additions into XCP-ng

    251 Topics
    3k Posts
    poddingueP
    Thank you so much for your feedback, @Vagrantin !
  • All NICs on XCP-NG Node Running in Promiscuous Mode

    7
    0 Votes
    7 Posts
    1k Views
    bleaderB
    Running tcpdump switches the interface to promiscuous to allow all traffic that reaches the NIC to be dumped. So I assume the issue you had on your switches allowed traffic to reach the host, that was forwarding it to the VMs, and wasn't dropped because tcpdump switched the VIF into promiscuous mode. If it seems resolved, that's good, otherwise let us know if we need to investigate further on this
  • Debian VM Takes down Host

    3
    0 Votes
    3 Posts
    488 Views
    P
    @Andrew Ok, thanks I will give that a try.
  • Does XCP-NG support NVMe/TCP?

    4
    0 Votes
    4 Posts
    982 Views
    M
    @olivierlambert Thanks!
  • 0 Votes
    1 Posts
    272 Views
    No one has replied
  • DC topology info

    11
    0 Votes
    11 Posts
    2k Views
    I
    @bleader yes, Thank you.
  • 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.
  • Copying a VM from 8.2 to 8.3 and back

    2
    0 Votes
    2 Posts
    486 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
  • Unable to find logs in XenCenter or Xen Orchestra

    Solved
    5
    0 Votes
    5 Posts
    796 Views
    S
    @olivierlambert thanks i got it.
  • 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
  • how to use template created in another host machine?

    2
    0 Votes
    2 Posts
    198 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.
  • Openstack vs xcp-ng (XO)

    3
    0 Votes
    3 Posts
    751 Views
    I
    @olivierlambert got it.
  • XCP-ng host - Power management

    11
    2
    0 Votes
    11 Posts
    3k 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.
  • 1 Votes
    8 Posts
    2k Views
    S
    @spcmediaco FYI, I never figured out how to fix. I am doing backup recovery now.
  • 0 Votes
    8 Posts
    2k 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.
  • GRUB waits for confirmation

    8
    0 Votes
    8 Posts
    2k 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.
  • Wide VMs on XCP-ng

    13
    0 Votes
    13 Posts
    3k 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.
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    4 Views
    No one has replied
  • VM cannot be migrated after NICs of one host died

    Solved
    5
    0 Votes
    5 Posts
    659 Views
    DanpD
    @hansve You're welcome.
  • block tdc: sector-size: 512/512 capacity: 20938752

    3
    0 Votes
    3 Posts
    497 Views
    K
    @apz I see. Thanks.
  • 0 Votes
    21 Posts
    5k 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