XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. Popular
    Log in to post
    • All Time
    • Day
    • Week
    • Month
    • All Topics
    • New Topics
    • Watched Topics
    • Unreplied Topics

    • All categories
    • stormiS

      XCP-ng 8.3 updates announcements and testing

      Watching Ignoring Scheduled Pinned Locked Moved News
      649
      1 Votes
      649 Posts
      513k Views
      semarieS
      @flakpyro it seems to me the proper upgrade path is: put the master in maintenance mode (xe host-disable host=$MASTER) evacuate the master (xe host-evacuate host=$MASTER) yum update the master reboot the master (xe host-reboot host=$MASTER) once done, do the same of the others hosts the VM would have been updated with the new trunks attribute when migrating to some updated host (in your case, when migrating to the master).
    • K

      Tesla xenctrlext.unix_error Device or resource is busy

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Hardware
      12
      2
      0 Votes
      12 Posts
      2k Views
      S
      For anyone who finds this in the future, I ran into a similar issue today when passing through a LSI Card, Coincidentally on Address 05:00.0, also coincidentally on a Supermicro Board (mine is X10DRH-CT, OPs was a X8DA8) I was originally writing a comment here to see if a solution had ever been found, but while taking/marking up screenshots of my Motherboards System Block Diagram, I discovered my problem... Human Error of course. Long story short, I added a PCI to 2xM.2 card, and in my BIOS, I bifurcated the wrong CPU/PCI Port. Instead of Bifurcating the M.2 Card, I accidentally Bifurcated the LSI Card, which caused the Unknown Header Error AND since there was an unknown header, the VM Would throw the "Device or Resource is busy" error when trying to start. Correcting the Bifurcation fixed the issue in my case. Not sure if that was the issue in OPs case, but this might help someone else who stumbles across this
    • S

      Sudden boot issues, emergency shell, root-lfgrma does not exist

      Watching Ignoring Scheduled Pinned Locked Moved Solved XCP-ng boot dracut
      2
      0 Votes
      2 Posts
      47 Views
      S
      After a good sleep, I resolved half of my issue. I got my LSI Cards messed up, I accidentally hidan internal LSI3108 (Address 01:00.0) instead of the PCI Card LSI3008 (Address 05:00.0)... My Boot Drives run off of the internal card. From the fallback kernel, I was able to Modify /etc/grub-efi.cfg to remove the internal card form the hidden list. I now have a separate issue, but will make another post.