1. Home
  2. XCP-ng

Subcategories

  • All Xen related stuff

    611 Topics
    6k Posts
    M
    I can confirm that when using Citrix/Xenserver guest utilities version 8.4 (https://github.com/xenserver/xe-guest-utilities/releases/tag/v8.4.0) memory ballooning / DMC is working fine. After live migration the RAM of the linux guest is expanded to dynamic_max again. So this issue was in fact caused by Rust based xen-guest-agent. For now I'll keep using Citrix/Xenserver guest utilities on my Linux guests until the feature is implemented in Vates rust-based guest utilities. Best regards

  • 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

    123 Topics
    1k Posts
    planedropP
    @MajorP93 This was also my thought, the disconnection method you mentioned, I was just wanting some feedback about that. I do have to be a bit careful because the migration must happen and then the VM on VMware must go back online while I work with the vendor to migrate all the rest of the data. As for the bigger than 2TB issue, that won't be an issue for me. This VM is HUGE but it's because it's thick provisioned and no longer needs to be, the new VM will have like 8 disks but none of them will be over 2TB (most will be less than 100GB). So I am thinking using V2V and just powering off the VM on VMware, disconnect the unneeded VDIs, then migrate, then reconnect those VDIs and power the VM back on.

  • Hardware related section

    162 Topics
    2k Posts
    S
    @TeddyAstie I hadn't seen anything special was needed in a VM other that a kernel new enough for support which 6.17 has, is there more to the story with adding things to Ubuntu?

  • The place to discuss new additions into XCP-ng

    248 Topics
    3k Posts
    olivierlambertO
    There's no small contributions, every one of them are great & welcome!
Log in to post
Load new posts
  • T

    XCP-ng 8.2.1 Guest UEFI Secure Boot

    12
    0 Votes
    12 Posts
    2k Views
    MathieuRAM
    I see that the bug is actually already fixed on the latest version (5.98.1).
  • apzA

    Guest running kernel 6.8 hangs after a while

    Solved
    17
    0 Votes
    17 Posts
    4k Views
    T
    I believe Proxmox Backup Server kernel Linux pbs 6.8.4-2-pve has also the same issue. updating to Linux pbs 6.8.12-1-pve solves.
  • M

    Protectli now available preinstalled with XCP-NG

    6
    1
    1 Votes
    6 Posts
    978 Views
    olivierlambertO
    @darkbounce Short answer: it seems that Intel hybrid architecture is finding a way to make something that would result of Xen running the VM with the less "featured" CPU, meaning your VM will never use all P core instructions that aren't on E core, meaning... it will work without disabling one or another. Hard to tell how much is lost in terms of perfs vs the best Intel hybrid scheduler (which is on... Windows) but probably not that much on a machine with a reduced number of P cores like this one.
  • Y

    Mirror moved Permanently

    8
    0 Votes
    8 Posts
    2k Views
    olivierlambertO
    @yammy I hope you are not talking of installing Docker in the Dom0, because this is really a bad idea.
  • P

    xo vm-export / vm-import issue with latest XCP-Ng 8.3

    10
    0 Votes
    10 Posts
    2k Views
    P
    @Pix [image: 1724423840376-capture-d-e-cran-2024-08-23-a-16.36.56.png] Looks like the different HW or Pool is an issue, i'll make more tests and report here if it's ok
  • P

    Disable DHCP option 60 when PXE booting

    10
    0 Votes
    10 Posts
    1k Views
    P
    @PontusB i don't even know if disabling option 66 solves the issue but as soon as we add option 66 in our DHCP server it boots fine from XenServer (but without HA between the many PVS servers).
  • RealTehrealR

    Issue after latest host update

    57
    0 Votes
    57 Posts
    23k Views
    M
    @stormi Thanks, looking forward.
  • T

    Vates please work acquiring vmware in the future

    3
    0 Votes
    3 Posts
    547 Views
    T
    @olivierlambert There you go hehe
  • B

    yum update, no more free space?

    8
    0 Votes
    8 Posts
    2k Views
    I
    @bloodyskullz If you still see the old ISO SR, the easiest way to migrate is simply by creating a new one and migrate the ISOs through XO to the new one. In regards to deletion of the old SR you need to check if it really is mapped to another drive or if the mapping was not working and it filled / if so, you might not be able to delete it
  • C

    Guide to Replace Tianocore UEFI Logo

    1
    1
    1 Votes
    1 Posts
    1k Views
    No one has replied
  • robytR

    update via yum or via xoa?

    5
    0 Votes
    5 Posts
    1k Views
    robytR
    @bleader said in update via yum or via xoa?: yes you're basically doing an RPU manually. But it is indeed odd that the process is stuck at 0%, it should be fairly fast to do the install patches, no errors in the logs? i've another install all patches and install all. Now i'll use rpm update and see if speed is the same or not
  • O

    Pool Tasks Don't Complete? Major Issues...

    6
    0 Votes
    6 Posts
    1k Views
    O
    @Danp Yes to both. I've probably restarted the toolstack at least a dozen times, mostly to clear hung tasks. I did notice some weird issues with a secondary SR being disconnected on xcp02, (one of 10 hosts, 9 after I ejected and forgot xcp01), but there's no disks on it. It wasn't being used for anything at all (yet), and it's fine on all the rest. That does lead me to think maybe it was a power bump that rebooted a switch or something though. Maybe it caused some kind of hangup with xcp01 and xcp02, and since xcp01 was the pool master, it cascaded to the other issues I've seen? Could that cause the VM's that were originally running on xcp02 to die and not be able to be recovered easily?
  • K

    A task keeps poping up every second or so

    7
    1
    0 Votes
    7 Posts
    886 Views
    olivierlambertO
    In any case, you can ignore it.
  • henri9813H

    VM migration is blocked during backup whereas no backup in progress

    5
    0 Votes
    5 Posts
    1k Views
    henri9813H
    @Danp Okay, you're a genius, I upgrade this morning after my backup. So that could explain my issue. the mentioned thread is exactly my issue, but I didn't find it when I was searching about my issue. Thanks for all !
  • D

    can't start vm after host disconnect

    29
    0 Votes
    29 Posts
    10k Views
    olivierlambertO
    No, from the XCP-ng point of view, the VM is still running without any interruption.
  • J

    XCP-ng Documentation - Roadmap

    Solved xcp-ng doc roadmap question out of date questions
    6
    0 Votes
    6 Posts
    1k Views
    J
    @olivierlambert @Marc-pezin Thank you very much for sorting this out!
  • N

    problem with export or moving VM between pools

    18
    0 Votes
    18 Posts
    2k Views
    N
    @nick-lloyd I like your interpretation.
  • A

    Upgrading to 2.5GB NICs and Troubleshooting Driver Issues on XCP-ng

    6
    0 Votes
    6 Posts
    2k Views
    A
    @aghering You could try compiling it yourself on 8.1... I don't have an 8.1 test/build system.
  • N

    Optimization of Virtual Machines

    4
    0 Votes
    4 Posts
    4k Views
    E
    @NerdsOrder66 Ah, good question... My most recent environment included a Windows Server with 100+ RDP users. There wasn't anything special for optimization there aside from giving it a bunch of RAM/CPU resources, but YMMV.
  • T

    Recurring crashes on VM

    3
    0 Votes
    3 Posts
    627 Views
    T
    @olivierlambert No, the only thing I get with xl dmesg on the host, for some time back, are random brief reports of individual CPUs running above temperature threshold and then being clocked down, and then resolving. Nothing else.