1. Home
  2. XCP-ng

Subcategories

  • All Xen related stuff

    583 Topics
    6k Posts
    olivierlambertO
    Thanks @dinhngtu and @stormi

  • The integrated web UI to manage XCP-ng

    23 Topics
    339 Posts
    C
    @lsouai-vates Great! Thanks for addressing this

  • Section dedicated to migrations from VMWare, HyperV, Proxmox etc. to XCP-ng

    104 Topics
    1k Posts
    olivierlambertO
    We made a patch release of XOA, improving some aspects. Have you tried it?

  • Hardware related section

    125 Topics
    1k Posts
    K
    @DustinB Hmm - just got done running mem86+ - 4 passes -- all 14 tests. No RAM errors. I wonder the what would cause this error? I'll probably just save config and reinstall. So strange.

  • The place to discuss new additions into XCP-ng

    242 Topics
    3k Posts
    F
    Hello everyone, I absolutely understand the point regarding datacenters. I am using xcp-ng for years in smaller - non datacenter - environments and its great. Therefore I added the nut packages (8.2 and 8.3) and it works like a charm. It's installation is well explained in: https://xcp-ng.org/forum/topic/4300/performing-automated-shutdown-during-a-power-failure-using-a-usb-ups-with-nut-xcp-ng-8-2/13?_=1742229073030 However, I agree with @Kajetan321 that it would be great if the nut package could be included in the standard "updated" packages repo since its added quite some benefits (imho) for "smaller" IT environments. However, I do not know how much effort it takes to maintain that.
Log in to post
Load new posts
  • G

    Migration woes - SR_BACKEND_FAILURE_78

    13
    0 Votes
    13 Posts
    1k 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
  • J

    Pool master and slaves cannot communicate with each other but can reach everything else

    7
    0 Votes
    7 Posts
    999 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
  • J

    This topic is deleted!

    1
    0 Votes
    1 Posts
    2 Views
    No one has replied
  • X

    XCP-ng Center 20.04.01 - console no "remote desktop RDP" on Windows 11 VM

    Solved
    15
    0 Votes
    15 Posts
    2k Views
    olivierlambertO
    Perfect!
  • kasn_codeK

    Multiple PCI-E passthrough problem

    3
    0 Votes
    3 Posts
    448 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.
  • B

    This topic is deleted!

    1
    0 Votes
    1 Posts
    2 Views
    No one has replied
  • N

    Upgrade from 8.1 to 8.2

    Solved
    12
    1
    0 Votes
    12 Posts
    987 Views
    olivierlambertO
    Thanks a lot for your feedback!
  • B

    Ubuntu desktop issue

    1
    0 Votes
    1 Posts
    199 Views
    No one has replied
  • D

    Host dbsync failed and XAPI restart everytime after patches installation

    4
    0 Votes
    4 Posts
    313 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.
  • S

    Error: Connection refused (calling connect ) (XCP-ng toolstack hang on boot)

    8
    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/
  • richiebyteR

    One VM forcibly restarts

    5
    0 Votes
    5 Posts
    581 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.
  • S

    Ubuntu VM struck at boot

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