Subcategories

  • All Xen related stuff

    606 Topics
    6k Posts
    F
    @redakula said in Coral TPU PCI Passthrough: Frigate.nvr which is one of the popular uses for the Coral do not recommend it for new installs either. Frigate updated their recommendations because of the Google decision to sunset the device and because there are alternative options available to frigate for image inferencing. The coral is still supported though, and frigate is not the only use case or platform that can benefit from an accelerator. At the end of the day if you've already got the hardware, and it's efficient enough to run, then not using it is a waste or resources that could be allocated to other VMs.
  • 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

    119 Topics
    1k Posts
    D
    @firefly because the underlying hardware that the VM has registered has likely changed, maybe substantially. A sysprep has the Windows system go through and validate what it's hardware is, it removes hardware specific drivers namely, but it does other stuff too.
  • Hardware related section

    161 Topics
    2k Posts
    Y
    @samuelolavo Thanks for your answer It's very weird because by seeing the command outputs that you pasted, it looks like everything is behaving as it should be. Even the PCI ID (segment:bus:device:function) seems to stay correct (0000:03:00.0) I'll ask others internally.
  • The place to discuss new additions into XCP-ng

    247 Topics
    3k Posts
    P
    @olivierlambert said in Rust-based guest-tools... How are things going?: The thing is that it works very well and doesn't need fixes… I know, not usual right? It was so stable that we left it like that waiting for people coming for bugs and nothing happened… We'll cut a 1.0 in the next weeks/months. I have indeed seen the stability of it myself. But the lack of updates made me worry anyway. But I'm really looking forward to the promotion to 1.0 as well. Thanks!
  • Ubuntu 24.04 VMs not reporting IP addresses to XCP-NG 8.2.1

    9
    5
    0 Votes
    9 Posts
    3k Views
    M
    Commenting for my future self and others as I just came across this issue too and it's not overly well documented and comments on the forums are often missing a a full story for how to debug and get this working...... When using Ubuntu 24.04, the usual apt method of installing XE Guest Utilities via the command; apt-install xe-guest-utilities Works, but doesn't. It successfully brings through the Memory information through to XO/XOA/XCP-ng Server, but not the IP Address, which is a tad strange. When checking the version of xe-guest-utilities that is contained within the APT Repository that comes configured out of the box with Ubuntu 24.04 using the following command; apt info xe-guest-utilities You can see the response is that it is running version "7.20.2-0" (as at the time of writing, which is before running an apt update command. Even when after running an update command; sudo apt update Then checking what packages are available to be updated using the following command; apt list --upgradable xe-guest-utilities wasn't available for an update past this point unfortunately. So to uninstall xe-guest-utilities installed via APT, simply run the following command; sudo apt remove xe-guest-utilities Then install via XO/XOA/XCP-ng Guest-Tools.iso Mount + Command Line by following these steps. Firstly, Select the guest-utilities.iso from the Disk within the XO/XOA/XCP-ng Platform for the VM. Then SSH into the box/console view and run the following commands; sudo /dev/cdrom /mnt sudo bash /mnt/Linux/install.sh sudo umount /dev/cdrom What you will notice when you run the second command is that gets installed here is "xe-guest-utilities_7.30.0.12_amd64.deb" - So is further ahead. Then you'll need to use the following commands to start the service on boot and also start the service. systemctl enable xe-linux-distribution.service systemctl start xe-linux-distribution.service And that now results in the IP Address of the virtual machine flowing through to XO/XOA/XCP-ng, which ever you are using.
  • Issues with new vm after latest 8.3 updates (priror to release)

    Solved
    4
    1 Votes
    4 Posts
    112 Views
    olivierlambertO
    No worries, it happens! Glad you found the problem
  • USB-Passthrough does not survive reboot of VM

    3
    1
    0 Votes
    3 Posts
    76 Views
    C
    @DustinB doesn't it use the exact same mechanism? I have to find out.
  • Issues joining pool with less pif on the newest host

    13
    0 Votes
    13 Posts
    420 Views
    A
    @semarie This pool is still on 8.2.1, we are trying to add this host in order upgrade with little to no downtime.
  • Deploying firewall to XCP-NG with rescue

    3
    1 Votes
    3 Posts
    66 Views
    ditzy-oliveD
    @bleader thanks for the tip. You see my knowledge in redhat based systems is almost non existant. Think I'm almost 99% debian and 1% ubuntu (and that not by choice) So I will take care of redeploying the script as soon as I upgrade, should be easily noticeable since monitoring will loose access and yell at me.
  • Every virtual machine I restart doesn't boot.

    24
    0 Votes
    24 Posts
    567 Views
    D
    @nikade said in Every virtual machine I restart doesn't boot.: @DustinB yeah im guessing the VDI isn't attached to the VM for some reason, based on the screenshot. Im also wondering if he ever rebooted the VM's after installing them with PXE Right, it's a likely answer... but even then I would've expected his PXE server to just restart the installation process all over again... assuming that the disk is attached to the VM etc and that PXE boot isn't disabled automatically like it is with an ISO after first boot. haha
  • Hosts fenced, new master, rebooted slaves not reconnecting to pool

    1
    3
    0 Votes
    1 Posts
    41 Views
    No one has replied
  • HP DL380 Gen 8 - XCP-ng 8.1.0 Failing to update microcode

    1
    0 Votes
    1 Posts
    48 Views
    No one has replied
  • VM state is halted but should be running

    5
    0 Votes
    5 Posts
    206 Views
    DanpD
    @olivierlambert New thread is here
  • Error installing Ubuntu 24.04 on new xcp-ng host.

    24
    1
    0 Votes
    24 Posts
    3k Views
    A
    @malemburg Kernel versions: 24.04 - Linux ubuntu-server 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux 24.04.3 - Linux ubuntu-server 6.8.0-71-generic #71-Ubuntu SMP PREEMPT_DYNAMIC Tue Jul 22 16:52:38 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux This is what is running after all the updates: Linux pxe000 6.8.0-100-generic #100-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 13 16:40:06 UTC 2026 x86_64 x86_64 x86_64 GNU/Linux I have this in my autoinstall to install the tools late-commands: - echo 'deb [trusted=yes] https://gitlab.com/api/v4/projects/xen-project%252Fxen-guest-agent/packages/generic/deb-amd64/ release/' > /target/etc/apt/sources.list.d/xen-guest-agent.list - curtin in-target -- apt update - curtin in-target -- apt install -y xen-guest-agent And this to get all the updates: updates: all
  • Booting to Dracut (I trusted ChatGPT)

    26
    0 Votes
    26 Posts
    2k Views
    M
    I know this is old but I had a similar issue. In the end I told dracut NOT to reassemble my raid array which allowed the system to boot perfectly after. I have no idea why it tries to assemble the same array two but on the second seems to be important
  • VM time ahead by 5 hours

    7
    0 Votes
    7 Posts
    258 Views
    A
    @dinhngtu I think it just have been a bad migration or the Win 11 Template did other things to the windows 10 os. Since new test vm did not show the time issues, and a fresh migration of the vim with correct template selected did not have the issues either. I dont know but maybe there is a way to put detect the correct VM template or make note. I didnt think using the win 11 template would have caused issues since using the "wrong" template on vm creation does not have the same effect.
  • Windows 11 (Win11_25H2_English_x64.iso) Fails to Install

    12
    4
    0 Votes
    12 Posts
    865 Views
    A
    @busthead said in Windows 11 (Win11_25H2_English_x64.iso) Fails to Install: It appears I missed the key press to start setup Dont you know your are not suppose to blink when doing working. You might miss something Glad you figured it out.
  • Create new virtual machine?

    7
    -1 Votes
    7 Posts
    349 Views
    A
    @drwhite85 I suggest watching some youtube videos about xcp-ng. I guest Lawrence Systems - https://www.youtube.com/watch?v=2wMmSm_ZeZ4 He has other videos that go into more depth
  • 0 Votes
    3 Posts
    236 Views
    olivierlambertO
    Worth asking @Team-OS-Platform-Release
  • botched pool patching and now we can't change pool master

    9
    0 Votes
    9 Posts
    472 Views
    R
    Resolved. Patched the rest of the hosts. Restarted all the toolstacks for good measure. I can move the master role now, and deploy new VMs.
  • Lost VMs disk after using new SR

    6
    4
    0 Votes
    6 Posts
    371 Views
    D
    Resolved by rebuild, and doing VM backup and metadata to trunas dataset.... Start Backup earlier. Be better then me
  • Red Hat Linux 10.1 ISO Won't Boot in UEFI Mode

    7
    2
    0 Votes
    7 Posts
    512 Views
    J
    Actually Alma Linux does have a variant for v2 CPUs so they can run 10.0. Just look for x86_64 v2 on the downloads page.
  • log_fs_usage / /var/log directory on pool master filling up constantly

    17
    1
    0 Votes
    17 Posts
    954 Views
    M
    Another thing that I noticed: despite enabling remote syslog (to graylog) for all XCP-ng hosts in the pool /var/log gets filled up to 100%. Adding remote syslog seem to not change usage of /var/log at all. Official XCP-ng documentation states otherwise here: https://docs.xcp-ng.org/installation/install-xcp-ng/#installation-on-usb-drives The linked part of the documentation indicates that configuring remote syslog can be a possible solution for /var/log space constraints which seems to be not the case. I feel like logging could use some investigation by Vates in general.
  • suggestions for upgrade path XCP-ng 8.2.1 -> XCP-ng 8.3.0

    11
    0 Votes
    11 Posts
    867 Views
    olivierlambertO
    Great! Keep us posted