Categories

  • All news regarding Xen and XCP-ng ecosystem

    142 Topics
    4k Posts
    rzrR
    XCP-ng is back to FOSDEM again for the 10th time, come to visit the Xen/XCP-ng stands ! https://fosdem.org/2026/stands/ Check Vates announcement at: https://vates.tech/blog/fosdem-2026/ If any interest we can setup a community gathering. ps: Post to be updated before the event for up to date info [image: wide.png]

  • Everything related to the virtualization platform

    1k Topics
    14k Posts
    M
    @stormi Well I only reboot our XCP-ng hosts after updates have been applied. I configured remote syslog at the beginning of december as an attempt to fix /var/log partition reaching 100& usage (as described in this thread). Remote syslog was working fine at that point. When you guys released the december round of patches I applied them and as a result rebooted all hosts of the pool. After checking our graylog server I can confirm that the XCP-ng pool stopped sending remote syslog data after the hosts had been rebooted. I then searched the forum, found this thread, was able to get remote syslog working again by re-applying the remote syslog IP addresses via XO as described by other users some time ago. Due to the fact that the behavior of the systems looked exactly as what had been described in this thread earlier I assumed that the issue may not have been investigated / fixed yet. //EDIT: regarding the question of package versions: I applied everything that you guys released in the december round of pachtes and had a patched system prior you releasing them.

  • All Xen Orchestra related questions/reports

    3k Topics
    27k Posts
    TeddyAstieT
    @dcskinner @olivierlambert You can read key/values from the xenstore, and write some (from VM to outside), but you cannot write values "in live" from outside the VM to the inside. It is, but XAPI doesn't provide a interface for it. do the guest tools quiesce the filesystems before snapshotting? Tools are aware of a snapshot so you don't have blocks in flight. do the guest tools quiesce the filesystems before snapshotting? Guests kernel are aware, as it is them that are performing a "suspend" on toolstack request (thus quiece filesystems); although "tools" can only observe that the system has been suspended after the fact by measuring side effects, and not orchestrate it. It's because suspend/resume operation doesn't come from "guest tools" actually, but instead from the kernel drivers. So userland tools has no say on it.

  • Our hyperconverged storage solution

    40 Topics
    715 Posts
    I
    @ronan-a Thanks

  • Non-English speakers

    31 Topics
    90 Posts
    olivierlambertO
    Yes, account aren't related