Subcategories

  • All Xen related stuff

    595 Topics
    6k Posts
    P
    @Bill.Oliver license-wise should be the same. now I think virtualisation gurus here could try to explain you what are the challenges with numa and dual sockets i have notions, but couldnt explain quite the optimisation in xen
  • The integrated web UI to manage XCP-ng

    25 Topics
    343 Posts
    P
    @mx234 I'm running netbird with an exit node and I get access to my LAN. Everything works great
  • Section dedicated to migrations from VMWare, HyperV, Proxmox etc. to XCP-ng

    109 Topics
    1k Posts
    T
    Did some more testing over the weekend and got some cleaner logs that are fully matched up. We ran the command 'journalctl -u xo-server -f -n 50' and see these to entries: Nov 15 14:26:10 xoa xo-server[552]: 2025-11-15T19:26:10.935Z xo:vmware-explorer:esxi INFO nbdkit logs of [WE-DS] WE-FS1/WE-FS1.vmdk are in /tmp/xo-serverGKTRzl Nov 15 14:26:10 xoa xo-server[552]: 2025-11-15T19:26:10.943Z xo:vmware-explorer:esxi INFO nbdkit logs of [WE-DS] WE-FS1/WE-FS1_1.vmdk are in /tmp/xo-serverCFf19t The log files were fairly large, wouldn't allow me to attach them, so i have provided them in a zip on dropbox if you want to take a look. From what I can pick out in the log files it appears that the transfer from VMware is complete or so it looks that way. After that I ran these two commands against the import tasks: xo-cli rest get tasks/0mi0ogg5f xo-cli rest get tasks/0mi0ogg5g The output for those is also attached. The one thing that stands out is in the "importing vms 17" is that WE-FS1.vmdk shows 'success' and WE-FS1_1.vmdk shows 'pending' Finally, I attached the logs from the host as well. I'm not seeing anything that jumps out at me as being wrong there either. Zip file of logs: https://www.dropbox.com/scl/fi/glxm5tvebf5vjizpnfvmx/Package-of-Logs.zip?rlkey=uyl0kltxhfnfcq0carbrg0lrv&e=1&dl=0
  • Hardware related section

    142 Topics
    1k Posts
    marcoiM
    @Joe_dev I have a MF unit with similar igpu. I was not able to get it working under any virtualization platform. There is something about amd igpu that makes passing it hard. I believe some have had it working under proxmox with custom kernel and video bios. I never bothered trying all that out so i just gave up on the unit.
  • The place to discuss new additions into XCP-ng

    244 Topics
    3k Posts
    henri9813H
    Hello, Thanks for your work ! We have some hypervisors of tests at Gladhost, we can use them with pleasure to test your work on xcp-ng 8.3 ! Best regards
  • 1 Votes
    6 Posts
    1k 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
    2k 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
    558 Views
    olivierlambertO
    Ah that makes sense then
  • Migration woes - SR_BACKEND_FAILURE_78

    13
    0 Votes
    13 Posts
    2k 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
    1k 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
    3k Views
    olivierlambertO
    Perfect!
  • Multiple PCI-E passthrough problem

    3
    0 Votes
    3 Posts
    514 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
    1k Views
    olivierlambertO
    Thanks a lot for your feedback!
  • Ubuntu desktop issue

    1
    0 Votes
    1 Posts
    234 Views
    No one has replied
  • Host dbsync failed and XAPI restart everytime after patches installation

    4
    0 Votes
    4 Posts
    388 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
    3k 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
    732 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
    427 Views
    planedropP
    How long have you waited for it? Like is it truly stuck or maybe just really slow to boot?