Categories

  • All news regarding Xen and XCP-ng ecosystem

    143 Topics
    4k Posts
    A
    Hello @igorglock, Damien is in holiday this week but he identified the issue and a patch should be tested for the next release of SM.
  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    M
    Sorry to necro-post this but I thought I'd come back and let you know that the new (finally signed) guest drivers for Windows resolved the problems I had been having with "inaccessible boot device" whenever I tried to install the Xen guest drivers while also using PCI-Passthrough to pass a nvme drive directly to the VM. The VM now boots perfectly fine with the boot disk being a virtual drive while allowing me to use the passthrough nvme as a data disk to which most of the software and my Steam library is installed. And ever since my virtual gaming rig has been stable and performing as I have expected.
  • 3k Topics
    28k Posts
    poddingueP
    Hi! I think what you're seeing may be stale entries in the XAPI database, ghost records that can survive upgrades or host reconfigurations. From what I've read, xe vm-destroy uuid=<vm-uuid> removes the record without touching any storage, which seems like what you need here; the xe CLI reference confirms storage is left intact. I think you can get the UUID first with xe vm-list name-label="Before Ubuntu Update" (replacing the name with whichever one you're after). I'm not entirely sure why xsconsole would show them but XO wouldn't, so if the VMs don't turn up in xe vm-list, it might be worth a mention to Team-XAPI-Network, they'll know the right way to dig into XAPI state.
  • Our hyperconverged storage solution

    47 Topics
    743 Posts
    olivierlambertO
    Adding @Team-Storage in the loop
  • 34 Topics
    102 Posts
    B
    La remarque a été intégrée dans l'article: https://www.myprivatelab.tech/xcp_lab_v2_ha#perte-master Merci encore pour le retour.