Categories

  • All news regarding Xen and XCP-ng ecosystem

    140 Topics
    4k Posts
    B
    I made a first "demonstrator" preview release for macOS, will upload .deb and .rpm packages as well: https://github.com/benapetr/XenAdminQt/releases/tag/v0.0.1-alpha
  • Everything related to the virtualization platform

    1k Topics
    14k Posts
    nikadeN
    @vague said in Bitten by XSA-474: starting up database engine D:2a59ed50ccb5 failed with exception Xmlm.Error(2:317874, "malformed character stream") My guess is that your xapi database has been corrupted, if you dont have a backup this will be a rough one. To add some content I'll summarize what you wrote on IRC: You got an error, it was not resolved. You then decided to start upgrading your xcp installation Now the database is corrupt, not sure it it was already or if it happend in step 2.
  • 3k Topics
    27k Posts
    W
    Version: XO: From: Xen Orchestra, commit 0a28a To: Xen Orchestra, commit b89c2 XCP-ng: From: 8.3 loaded from ISO: xcp-ng-8.3.0-rc1.iso To: 8.3 loaded from ISO: xcp-ng-8.3.0-20250606.iso and haven't update it since until there is a major version release. Issue: Orphan VDIs in XO show health problem for my "base copy" snapshots as it can't find the VDIs anymore for some reason? Note: I have clone of before the XO update and have both XO commit 0a28a and commit b89c2 running that's why I was able to take snapshots below so not everything is all lost and done for... From: (before update) [image: 1767585474960-2ab15d5a-9bf5-40e8-ba1b-82496ae817fb-image.png] [image: 1767585728990-f01117f6-91b1-41c9-944a-6351fcd7d2b9-image.png] To: (after update) [image: 1767585262413-3daec9f7-6e48-4071-b9cc-01a7254ab234-image.png] [image: 1767585769101-442119c6-bced-4526-91e9-24218fd1112b-image.png] Is it ok to delete it seem like I can't delete it... in fear of breaking all my VMs.
  • Our hyperconverged storage solution

    39 Topics
    703 Posts
    snk33S
    @ronan-a said in XOSTOR hyperconvergence preview: @peter_webbird We've already had feedback on CBT and LINSTOR/DRBD, we don't necessarily recommend enabling it. We have a blocking dev card regarding a bug with LVM lvchange command that may fail on CBT volumes used by a XOSTOR SR. We also have other issues related to migration with CBT. Is the problem still occurring on latest XCP-ng / XOSTOR version ? Not being able to use CBT on XOSTOR is a big issue for backup/replication.
  • 31 Topics
    90 Posts
    olivierlambertO
    Yes, account aren't related