Subcategories

  • All Xen related stuff

    627 Topics
    6k Posts
    H
    @dinhngtu said: dinhngtu VATES 🪐 XCP-NG TEAM a day ago @hrvojer There are many bugs in older versions of the Xen PV drivers. I suggest running Windows without guest tools and drivers if you can take the performance and functionality hit (no suspend/migration on UEFI VMs, no metric reporting, etc). Thanks @dinhngtu, appreciated. Running without PV drivers is hard for us: this is an I/O-heavy production SQL Server and we already had timeout problems before adding RAM, so I'm worried emulated disk performance would hurt more than an occasional crash. Our medium-term plan is to migrate SQL to a new VM with a supported Windows Server and current tools. Until then, a few follow-up questions: Is there any official place to still get XenServer VM Tools 9.2.3 (or whichever last version works on 2012 R2)? Would an older XCP-ng PV driver release (e.g. 8.2.2.200) likely be any better here, or is it the same xenvbd code base? One more detail I missed: in the same Feb 2026 change we also enabled "Lock Pages in Memory" for the SQL Server service account (together with 16 -> 64 GB RAM). Is there any known issue between old xenvbd and locked pages / large guest memory? Meanwhile we've capped SQL max server memory at 32 GB as a stopgap.
  • The integrated web UI to manage XCP-ng

    29 Topics
    367 Posts
    olivierlambertO
    The same as @john.c and also XO Lite tends to be less a priority because less critical than the full fledged XO (the priority is to replace entirely XO 5 in the next releases). Why you would need XO Lite outside basic actions? It's mostly meant to bootstrap XO itself and do basic operations (which is already the case, at least with many basic features already). Initially, the goal hasn't moved: replacing XenCenter. We are moving in that direction, but again, I think it's more important to get XO 6 finished first. I'm curious to understand more the use case of XO Lite in your context @unreal-shizzle ?
  • Section dedicated to migrations from VMWare, HyperV, Proxmox etc. to XCP-ng

    132 Topics
    1k Posts
    J
    @mpiton Thanks for a fantasticly quick answer, and detailed as well. I will test this immediately! Update: I can confirm that this was indeed the problem!
  • Hardware related section

    178 Topics
    2k Posts
    S
    @yannsionneau Yes it works Thank you very much, great job Tested on Ryzen 9 9950X / AMD Raphael iGPU Tested the new experimental iGPU passthrough packages. - CPU: AMD Ryzen 9 9950X - iGPU: AMD Raphael (1002:13c0) - XCP-ng: 8.3 - Guest: Bazzite AMD - VBIOS: extracted from the ACPI VFCT and supplied as /root/vbios.bin - iGPU passthrough: working - AMD amdgpu driver: working - Physical HDMI output: working - Bazzite desktop displayed successfully on the physical HDMI port. Ubuntu 24.04.2 was able to initialize the GPU and Vulkan/RADV detected the Raphael iGPU, but the HDMI output went black when the graphical desktop started. Bazzite worked and provided a stable display output. So on my Ryzen 9 9950X, the experimental packages appear to successfully enable Raphael iGPU passthrough and physical HDMI output.
  • The place to discuss new additions into XCP-ng

    255 Topics
    3k Posts
    dicode-nlD
    New version: https://github.com/dicode-nl/xcp-ng-ceph-rbd/releases/tag/v20260903 This one includes native Ceph rbd SXM over SMAPIv3! GitHub updated with the latest commits and changes. As always, use with caution. I did run a lot of test scenario's but please do test yourself and let me know your findings!
  • 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.
  • Menu Migrate to server missing

    Moved
    4
    0 Votes
    4 Posts
    1k Views
    olivierlambertO
    Ah that makes sense then
  • Migration woes - SR_BACKEND_FAILURE_78

    13
    0 Votes
    13 Posts
    3k Views
    olivierlambertO
    You need a fully up to date XO (check that first). If you are on XOA Free, you might need a trial (send me a private chat message with your email registered to this XOA, so I can unlock you the free trial). Alternatively, you can also use XO from the sources
  • 0 Votes
    7 Posts
    3k Views
    J
    Just updating for anyone that has the same issue, we ended up just rebooting the master and like @JamuelStarkey said everything just automatically fell in place. Did have to exit maintenance mode on the master and replug the PBD but everything else went back to normal immediately. Still frustrating to experience and would really love to know what caused this. If there's any logs I can pull to figure this out do let me know @olivierlambert
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    2 Views
    No one has replied
  • XCP-ng Center 20.04.01 - console no "remote desktop RDP" on Windows 11 VM

    Solved
    15
    0 Votes
    15 Posts
    5k Views
    olivierlambertO
    Perfect!
  • Multiple PCI-E passthrough problem

    3
    0 Votes
    3 Posts
    921 Views
    kasn_codeK
    So I managed to get the VM to see both drives. In dmesg I can see something like this [ 1.160149] ahci 0000:00:08.0: AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x20 impl SATA mode [ 1.161043] ahci 0000:00:08.0: flags: 64bit ncq sntf ilck led clo only pmp fbs pio slum part [ 1.187888] ahci 0000:00:09.0: SSS flag set, parallel bus scan disabled [ 2.186211] ahci 0000:00:09.0: controller reset failed (0xffffffff) [ 2.187307] ahci: probe of 0000:00:09.0 failed with error -5 So I removed the pci and did a rescan with root@mars-test-uefi:~# echo "1" > /sys/bus/pci/devices/0000\:00\:09.0/remove root@mars-test-uefi:~# echo "1" > /sys/bus/pci/rescan Now when I checked dmesg it shows up properly [ 795.538214] ahci 0000:00:09.0: AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x4 impl SATA mode [ 795.538219] ahci 0000:00:09.0: flags: 64bit ncq sntf ilck led clo only pmp fbs pio slum part fdisk -l also shows up both drives now too root@mars-test-uefi:~# fdisk -l Disk /dev/sda: 7.28 TiB, 8001563222016 bytes, 15628053168 sectors Disk model: ST8000DM004-2U91 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/sdb: 7.28 TiB, 8001563222016 bytes, 15628053168 sectors Disk model: WDC WD80EFZZ-68B Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes It seems like on boot it tries to find the device but it fails to, but on a remove/rescan it seems like its fine? The question now becomes, how do I make this work ON boot.
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    2 Views
    No one has replied
  • Upgrade from 8.1 to 8.2

    Solved
    12
    1
    0 Votes
    12 Posts
    2k Views
    olivierlambertO
    Thanks a lot for your feedback!
  • Ubuntu desktop issue

    1
    0 Votes
    1 Posts
    422 Views
    No one has replied
  • 0 Votes
    4 Posts
    810 Views
    olivierlambertO
    Really, you should because it would have prevent you this situation in the first place, but also some other future questions or problem you might have That's one of the few capital rules in XCP-ng world. Your master must ALWAYS be more recent than the slaves (or at the same level obviously), otherwise slaves won't be able to connect. I think you really need some assistance on best practices and such, please contact us so we can assist more generally. If this basic requirement is not understand, you might have other/deeper issues.
  • 0 Votes
    8 Posts
    5k Views
    olivierlambertO
    Any of the host: if they are in the same pool, that's logical. Only the master is needed to be reach. XAPI will probably be in "Starting state" as long as all SR aren't plugged. If you have the SR on a VM on another host than the master, reboot the master only, you should be able to connect sooner Alternatively, check https://docs.xcp-ng.org/troubleshooting/
  • One VM forcibly restarts

    5
    0 Votes
    5 Posts
    1k Views
    richiebyteR
    On this one VM yeah, all other VM's have been fine with the Citrix tools. I am not sure if the tools change anything on the VM level once installed, as the problem did continue after attaching a fresh blank virtual disk to the problem VM.
  • Ubuntu VM struck at boot

    2
    1
    0 Votes
    2 Posts
    769 Views
    planedropP
    How long have you waited for it? Like is it truly stuck or maybe just really slow to boot?