XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    • Profile
    • Following 0
    • Followers 0
    • Topics 17
    • Shares 0
    • Posts 44
    • Groups 0
    okynnorO Offline
    1. Home
    2. okynnor
    3. Posts

    Posts

    Recent Best Controversial
    • RE: iscsi shows "No Storage Repositories Detected"

      I have since tried a little more digging, The error seems to suggest that the block drive SR is not available/file not found?
      The iscsi block drive is sitting inside a TrueNAS scale server snapshot backups too.

      But let me know if I"m doing this correctly as per the command below to try to use the

      xe pbd-plug
      

      command to solve this issue or not:

      [15:25 xenserver-tiger ~]# xe sr-list name-label="iSCSI virtual disk storage2"
      uuid ( RO)                : 7f968d45-56dd-a6aa-83d2-bd33dd2a8e5f
                name-label ( RW): iSCSI virtual disk storage2
          name-description ( RW): 
                      host ( RO): xenserver-tiger
                      type ( RO): lvmoiscsi
              content-type ( RO): user
      
      
      [15:27 xenserver-tiger ~]# xe pdb-list sr-uuid=7f968d45-56dd-a6aa-83d2-bd33dd2a8e5f
      Unknown command: pdb-list
      For usage run: 'xe help'
      [15:28 xenserver-tiger ~]# xe pbd-list sr-uuid=7f968d45-56dd-a6aa-83d2-bd33dd2a8e5f
      uuid ( RO)                  : d4050fae-ec84-efac-62a1-d3d62b4fb879
                   host-uuid ( RO): 3986c16a-a9e0-4ebf-83a0-4438d8bd5916
                     sr-uuid ( RO): 7f968d45-56dd-a6aa-83d2-bd33dd2a8e5f
               device-config (MRO): SCSIid: 36589cfc000000dca3287604eb99e625a; targetIQN: iqn.2005-10.org.freenas.ctl:scuzzy-ng2; target: 192.168.1.5; port: 3260
          currently-attached ( RO): false
      
      
      [15:28 xenserver-tiger ~]# xe pbd-plug uuid=d4050fae-ec84-efac-62a1-d3d62b4fb879
      Error code: SR_BACKEND_FAILURE_47
      Error parameters: , The SR is not available [opterr=no such volume group: VG_XenStorage-7f968d45-56dd-a6aa-83d2-bd33dd2a8e5f], 
      [15:29 xenserver-tiger ~]# tail -n 50 /var/log/SMlog | grep -i -E "error|exception|47|opterr"
      Nov 20 15:29:46 xenserver-tiger SM: [70710][MainThread] FileNotFoundError: [Errno 2] No such file or directory: '/dev/disk/by-scsid/36589cfc000000dca3287604eb99e625a'
      Nov 20 15:29:46 xenserver-tiger SM: [70710][MainThread] ): EXCEPTION <class 'FileNotFoundError'>, [Errno 2] No such file or directory: '/dev/disk/by-scsid/36589cfc000000dca3287604eb99e625a'
      Nov 20 15:29:46 xenserver-tiger fairlock[3380]: /run/fairlock/devicemapper sent '70710 - 10994.070830647'
      Nov 20 15:29:46 xenserver-tiger SM: [70710][MainThread] Error in SR.after_master_attach Input/output error
      Nov 20 15:29:46 xenserver-tiger SM: [70710][MainThread] ***** generic exception: sr_attach: EXCEPTION <class 'xs_errors.SROSError'>, The SR is not available [opterr=no such volume group: VG_XenStorage-7f968d45-56dd-a6aa-83d2-bd33dd2a8e5f]
      Nov 20 15:29:46 xenserver-tiger SM: [70710][MainThread]     opterr='no such volume group: %s' % self.vgname)
      Nov 20 15:29:46 xenserver-tiger SM: [70710][MainThread] ***** LVM over iSCSI: EXCEPTION <class 'xs_errors.SROSError'>, The SR is not available [opterr=no such volume group: VG_XenStorage-7f968d45-56dd-a6aa-83d2-bd33dd2a8e5f]
      Nov 20 15:29:46 xenserver-tiger SM: [70710][MainThread]     opterr='no such volume group: %s' % self.vgname)
      
      posted in Compute
      okynnorO
      okynnor
    • RE: iscsi shows "No Storage Repositories Detected"

      @DustinB Wowsers! Thank you 🙌 ...I got my metadata back!

      I got a new problem...when I try to turn on my VMs, they are reporting

      NO_HOSTS_AVAILABLE()
      

      Also, while iSCSI is listed under Storage, and reports usage and free space, it's showing as disconnected.

      I suspect that the fact that iSCSI is disconnected leads me to believe that the VMs are not starting.

      When I look into the iScsi repository under XSCONSOLE, it's saying

      This Storage Repository is unplugged and not usable by this host. 
      

      When I look at the iSCSI setup under TrueNAS Scale, it's showing as running.

      I'm on a roll thanks you guys...just need one more push!

      Screenshot 2026-11-20 at 1.30.32 PM.png

      posted in Compute
      okynnorO
      okynnor
    • RE: iscsi shows "No Storage Repositories Detected"

      @poddingue Thank you so much for reassuring me that my SR is still intact. I wasn't sure.

      I'm getting quite desperate because all my VMs are down for more than 24hours...

      I do have metadata backup from XO (sadly XO was one of the VMs that are sitting in the SR). I also have a metadata backup created from XSCONSOLE.

      So to get things going, I was going to restore the metadata saved by xsconsole. When I did it, it complained of two things:

      "This MAC seed is already in use by a VM in the pool" and "Error code: VDI_CONTENT_ID_MISSING "

      it sounds like I need to delete the MAC addresses, which I took as I need to delete all entries for each VM currency showing in xsconsole. So I did. Nothing. Next, I tried to do it by running

      xe vm-param-remove uuid=<existing-vm-uuid> param-name=other-config param-key=mac_seed. 
      

      nothing, It didn't work.

      I then tried to take the backup metafiles and put them into a new machine with a fresh install of xcp-ng. It's the exact same hardware! Yet, the restore complained that the ethernet names don't match. I could try to rename them all from ETH1-ETH5 to ETH6-ETH9. But after doing that, will I see the same problems I did above? After all there's no SR for iSCSI that can be reattached.

      Or, will be easier to just get the XOA appliance?
      A negative comment is that the old XOA was great but this one seems to be quite feature missing. Is there a way to get the XOA appliance please?

      posted in Compute
      okynnorO
      okynnor
    • iscsi shows "No Storage Repositories Detected"

      I have a nasty problem of my own creation. I hope the community can help me as I have a lot of data stored in this iscsi repository.

      It all started because my hardware RAID had failed on my Dell PowerEdge R630. I decided to restart the server. It didn't fix the problem, of course. But the server did work with just one 1 remaining drive. Thinking that I need to rebuilt the RAID array, I put two new SSDs in and proceeded to format them to use Software RAID (after setting HBA & ACHI on then PowerEdge). No problem...the reinstall went well.

      Now, when I tried to reattach the iScsi repository, it showed me that there was "No Storage Repository Detected".

      I then went to the Terminal in XCP-NG to run the following command to see if the iscsi repository was still available (I didn't reformat the repository)

      [17:31 xenserver-tiger ~]# iscsiadm -m discovery -t sendtargets -p 192.168.1.5
      192.168.1.5:3260,1 iqn.2005-10.org.freenas.ctl:scuzzy-ng2
      172.16.0.1:3260,1 iqn.2005-10.org.freenas.ctl:scuzzy-ng2
      [17:31 xenserver-tiger ~]# 
      

      That would tell me that the repository still exists (I think)

      I've tried every thing that I can think of to reconnect them. I do not want to lose all my VMs that are inside that iScsi repository.

      Is there a way to reattach them from the Terminal?

      Other things d

      posted in Compute
      okynnorO
      okynnor
    • RE: [SOLVED] Just FYI: current update seams to break NUT dependancies

      I second this request.

      posted in XCP-ng
      okynnorO
      okynnor
    • xcp-ng patches install fail

      Hi,

      I'm trying to install some patches for xcp-ng but they all failed to install. I even tried to do it from the shell by using

      yum clean all
      

      From running yum update, I get this:

      [21:42 xenserver-tiger ~]# yum update
      Loaded plugins: fastestmirror
      Loading mirror speeds from cached hostfile
      Excluding mirror: updates.xcp-ng.org
       * xcp-ng-base: mirrors.xcp-ng.org
      Excluding mirror: updates.xcp-ng.org
       * xcp-ng-updates: mirrors.xcp-ng.org
      Resolving Dependencies
      --> Running transaction check
      ---> Package bind-libs-lite.x86_64 32:9.9.4-61.el7_5.1 will be updated
      ---> Package bind-libs-lite.x86_64 32:9.9.4-63.1.xcpng8.3 will be an update
      ---> Package bind-license.noarch 32:9.9.4-61.el7_5.1 will be updated
      ---> Package bind-license.noarch 32:9.9.4-63.1.xcpng8.3 will be an update
      ---> Package blktap.x86_64 0:3.55.5-6.1.xcpng8.3 will be updated
      ---> Package blktap.x86_64 0:3.55.5-6.3.xcpng8.3 will be an update
      ---> Package broadcom-bnxt-en.x86_64 0:1.10.3_232.0.155.5-1.xcpng8.3 will be updated
      ---> Package broadcom-bnxt-en.x86_64 0:1.10.3_237.1.20.0-8.1.xcpng8.3 will be an update
      ---> Package coreutils.x86_64 0:8.22-21.el7 will be updated
      ---> Package coreutils.x86_64 0:8.22-22.xcpng8.3 will be an update
      ---> Package createrepo_c.x86_64 0:0.10.0-6.el7 will be updated
      ---> Package createrepo_c.x86_64 0:0.21.1-3.xcpng8.3 will be an update
      ---> Package createrepo_c-libs.x86_64 0:0.10.0-6.el7 will be updated
      ---> Package createrepo_c-libs.x86_64 0:0.21.1-3.xcpng8.3 will be an update
      ---> Package curl.x86_64 0:8.9.1-5.1.xcpng8.3 will be updated
      ---> Package curl.x86_64 0:8.9.1-5.2.xcpng8.3 will be an update
      ---> Package device-mapper.x86_64 7:1.02.149-18.2.1.xcpng8.3 will be updated
      ---> Package device-mapper.x86_64 7:1.02.149-18.3.1.xcpng8.3 will be an update
      ---> Package device-mapper-event.x86_64 7:1.02.149-18.2.1.xcpng8.3 will be updated
      ---> Package device-mapper-event.x86_64 7:1.02.149-18.3.1.xcpng8.3 will be an update
      ---> Package device-mapper-event-libs.x86_64 7:1.02.149-18.2.1.xcpng8.3 will be updated
      ---> Package device-mapper-event-libs.x86_64 7:1.02.149-18.3.1.xcpng8.3 will be an update
      ---> Package device-mapper-libs.x86_64 7:1.02.149-18.2.1.xcpng8.3 will be updated
      ---> Package device-mapper-libs.x86_64 7:1.02.149-18.3.1.xcpng8.3 will be an update
      ---> Package forkexecd.x86_64 0:25.33.1-2.3.xcpng8.3 will be updated
      ---> Package forkexecd.x86_64 0:26.1.3-1.3.xcpng8.3 will be an update
      ---> Package gnutls.x86_64 0:3.3.29-9.el7_6 will be updated
      ---> Package gnutls.x86_64 0:3.3.29-10.1.xcpng8.3 will be an update
      ---> Package gnutls-dane.x86_64 0:3.3.29-9.el7_6 will be obsoleted
      ---> Package gnutls-devel.x86_64 0:3.3.29-10.1.xcpng8.3 will be obsoleting
      --> Processing Dependency: pkgconfig(hogweed) for package: gnutls-devel-3.3.29-10.1.xcpng8.3.x86_64
      --> Processing Dependency: pkgconfig(libtasn1) for package: gnutls-devel-3.3.29-10.1.xcpng8.3.x86_64
      --> Processing Dependency: pkgconfig(nettle) for package: gnutls-devel-3.3.29-10.1.xcpng8.3.x86_64
      --> Processing Dependency: pkgconfig(p11-kit-1) for package: gnutls-devel-3.3.29-10.1.xcpng8.3.x86_64
      --> Processing Dependency: pkgconfig(zlib) for package: gnutls-devel-3.3.29-10.1.xcpng8.3.x86_64
      ---> Package gnutls-utils.x86_64 0:3.3.29-9.el7_6 will be updated
      ---> Package gnutls-utils.x86_64 0:3.3.29-10.1.xcpng8.3 will be obsoleting
      ---> Package gpumon.x86_64 0:24.1.0-71.1.xcpng8.3 will be updated
      ---> Package gpumon.x86_64 0:24.1.0-83.2.xcpng8.3 will be an update
      ---> Package intel-i40e.x86_64 0:2.25.11-2.xcpng8.3 will be updated
      ---> Package intel-i40e.x86_64 0:2.25.11-4.xcpng8.3 will be an update
      ---> Package intel-ixgbe.x86_64 0:5.18.6-1.xcpng8.3 will be updated
      ---> Package intel-ixgbe.x86_64 0:6.2.5-1.xcpng8.3 will be an update
      ---> Package intel-microcode.noarch 0:20251029-1.xcpng8.3 will be updated
      ---> Package intel-microcode.noarch 0:20260115-1.xcpng8.3 will be an update
      ---> Package ipmitool.x86_64 0:1.8.18-7.el7 will be updated
      ---> Package ipmitool.x86_64 0:1.8.19-11.1.xcpng8.3 will be an update
      ---> Package iputils.x86_64 0:20160308-10.el7 will be updated
      ---> Package iputils.x86_64 0:20160308-10.1.xcpng8.3 will be an update
      ---> Package krb5-libs.x86_64 0:1.15.1-19.el7 will be updated
      ---> Package krb5-libs.x86_64 0:1.15.1-22.1.xcpng8.3 will be an update
      ---> Package libarchive.x86_64 0:3.3.3-1.1.xcpng8.3 will be updated
      ---> Package libarchive.x86_64 0:3.6.1-4.1.xcpng8.3 will be an update
      ---> Package libcurl.x86_64 0:8.9.1-5.1.xcpng8.3 will be updated
      ---> Package libcurl.x86_64 0:8.9.1-5.2.xcpng8.3 will be an update
      ---> Package libevent.x86_64 0:2.0.21-4.el7 will be updated
      ---> Package libevent.x86_64 0:2.0.21-4.1.xcpng8.3 will be an update
      --> Processing Dependency: libcrypto.so.10(libcrypto.so.10)(64bit) for package: libevent-2.0.21-4.1.xcpng8.3.x86_64
      --> Processing Dependency: libssl.so.10(libssl.so.10)(64bit) for package: libevent-2.0.21-4.1.xcpng8.3.x86_64
      --> Processing Dependency: libcrypto.so.10()(64bit) for package: libevent-2.0.21-4.1.xcpng8.3.x86_64
      --> Processing Dependency: libssl.so.10()(64bit) for package: libevent-2.0.21-4.1.xcpng8.3.x86_64
      ---> Package libsmbclient.x86_64 0:4.10.16-25.2.xcpng8.3 will be updated
      ---> Package libsmbclient.x86_64 0:4.10.16-25.3.xcpng8.3 will be an update
      ---> Package libssh2.x86_64 0:1.4.3-10.el7_2.1 will be updated
      ---> Package libssh2.x86_64 0:1.11.0-1.xcpng8.3 will be an update
      ---> Package libtpms.x86_64 0:0.9.6-3.xcpng8.3 will be updated
      ---> Package libtpms.x86_64 0:0.9.6-3.1.xcpng8.3 will be an update
      ---> Package libwbclient.x86_64 0:4.10.16-25.2.xcpng8.3 will be updated
      ---> Package libwbclient.x86_64 0:4.10.16-25.3.xcpng8.3 will be an update
      ---> Package lvm2.x86_64 7:2.02.180-18.2.1.xcpng8.3 will be updated
      ---> Package lvm2.x86_64 7:2.02.180-18.3.1.xcpng8.3 will be an update
      ---> Package lvm2-libs.x86_64 7:2.02.180-18.2.1.xcpng8.3 will be updated
      ---> Package lvm2-libs.x86_64 7:2.02.180-18.3.1.xcpng8.3 will be an update
      ---> Package mdadm.x86_64 0:4.0-13.el7 will be updated
      ---> Package mdadm.x86_64 0:4.2-5.xcpng8.3 will be an update
      ---> Package message-switch.x86_64 0:25.33.1-2.3.xcpng8.3 will be updated
      ---> Package message-switch.x86_64 0:26.1.3-1.3.xcpng8.3 will be an update
      ---> Package net-snmp.x86_64 1:5.7.2-52.1.xcpng8.3 will be updated
      ---> Package net-snmp.x86_64 1:5.9.3-8.1.xcpng8.3 will be an update
      ---> Package net-snmp-agent-libs.x86_64 1:5.7.2-52.1.xcpng8.3 will be updated
      ---> Package net-snmp-agent-libs.x86_64 1:5.9.3-8.1.xcpng8.3 will be an update
      ---> Package net-snmp-libs.x86_64 1:5.7.2-52.1.xcpng8.3 will be updated
      --> Processing Dependency: libnetsnmp.so.31()(64bit) for package: nut-2.8.0-2.el7.x86_64
      ---> Package net-snmp-libs.x86_64 1:5.9.3-8.1.xcpng8.3 will be an update
      ---> Package openssl.x86_64 1:1.0.2k-26.2.xcpng8.3 will be updated
      ---> Package openssl.x86_64 1:3.0.9-2.0.1.3.xcpng8.3 will be an update
      ---> Package openssl-libs.x86_64 1:1.0.2k-26.2.xcpng8.3 will be updated
      ---> Package openssl-libs.x86_64 1:3.0.9-2.0.1.3.xcpng8.3 will be obsoleting
      ---> Package openssl-perl.x86_64 1:1.0.2k-26.2.xcpng8.3 will be updated
      ---> Package openssl-perl.x86_64 1:3.0.9-2.0.1.3.xcpng8.3 will be an update
      --> Processing Dependency: perl-interpreter for package: 1:openssl-perl-3.0.9-2.0.1.3.xcpng8.3.x86_64
      ---> Package openvswitch.x86_64 0:2.17.7-2.1.xcpng8.3 will be updated
      ---> Package openvswitch.x86_64 0:2.17.7-4.1.xcpng8.3 will be an update
      ---> Package python.x86_64 0:2.7.5-90.el7 will be updated
      ---> Package python.x86_64 0:2.7.5-92.1.xcpng8.3 will be an update
      ---> Package python-libs.x86_64 0:2.7.5-90.el7 will be updated
      ---> Package python-libs.x86_64 0:2.7.5-92.1.xcpng8.3 will be an update
      ---> Package python-pycurl.x86_64 0:7.19.0-19.el7 will be updated
      ---> Package python-pycurl.x86_64 0:7.19.0-19.1.xcpng8.3 will be an update
      ---> Package python3.x86_64 0:3.6.8-18.el7 will be updated
      ---> Package python3.x86_64 0:3.6.8-20.xcpng8.3 will be an update
      ---> Package python3-libs.x86_64 0:3.6.8-18.el7 will be updated
      ---> Package python3-libs.x86_64 0:3.6.8-20.xcpng8.3 will be an update
      ---> Package qcow-stream-tool.x86_64 0:25.33.1-2.3.xcpng8.3 will be updated
      ---> Package qcow-stream-tool.x86_64 0:26.1.3-1.3.xcpng8.3 will be an update
      ---> Package qemu.x86_64 2:4.2.1-5.2.15.2.xcpng8.3 will be updated
      ---> Package qemu.x86_64 2:4.2.1-5.2.17.1.xcpng8.3 will be an update
      ---> Package rrdd-plugins.x86_64 0:25.33.1-2.3.xcpng8.3 will be updated
      ---> Package rrdd-plugins.x86_64 0:26.1.3-1.3.xcpng8.3 will be an update
      ---> Package rsync.x86_64 0:3.4.1-1.1.xcpng8.3 will be updated
      ---> Package rsync.x86_64 0:3.4.1-1.2.xcpng8.3 will be an update
      ---> Package samba-client.x86_64 0:4.10.16-25.2.xcpng8.3 will be updated
      ---> Package samba-client.x86_64 0:4.10.16-25.3.xcpng8.3 will be an update
      ---> Package samba-client-libs.x86_64 0:4.10.16-25.2.xcpng8.3 will be updated
      ---> Package samba-client-libs.x86_64 0:4.10.16-25.3.xcpng8.3 will be an update
      ---> Package samba-common.noarch 0:4.10.16-25.2.xcpng8.3 will be updated
      ---> Package samba-common.noarch 0:4.10.16-25.3.xcpng8.3 will be an update
      ---> Package samba-common-libs.x86_64 0:4.10.16-25.2.xcpng8.3 will be updated
      ---> Package samba-common-libs.x86_64 0:4.10.16-25.3.xcpng8.3 will be an update
      ---> Package samba-common-tools.x86_64 0:4.10.16-25.2.xcpng8.3 will be updated
      ---> Package samba-common-tools.x86_64 0:4.10.16-25.3.xcpng8.3 will be an update
      ---> Package samba-libs.x86_64 0:4.10.16-25.2.xcpng8.3 will be updated
      ---> Package samba-libs.x86_64 0:4.10.16-25.3.xcpng8.3 will be an update
      ---> Package samba-winbind.x86_64 0:4.10.16-25.2.xcpng8.3 will be updated
      ---> Package samba-winbind.x86_64 0:4.10.16-25.3.xcpng8.3 will be an update
      ---> Package samba-winbind-clients.x86_64 0:4.10.16-25.2.xcpng8.3 will be updated
      ---> Package samba-winbind-clients.x86_64 0:4.10.16-25.3.xcpng8.3 will be an update
      ---> Package samba-winbind-modules.x86_64 0:4.10.16-25.2.xcpng8.3 will be updated
      ---> Package samba-winbind-modules.x86_64 0:4.10.16-25.3.xcpng8.3 will be an update
      ---> Package sm.x86_64 0:3.2.12-16.1.xcpng8.3 will be updated
      ---> Package sm.x86_64 0:3.2.12-17.1.xcpng8.3 will be an update
      ---> Package sm-cli.x86_64 0:25.33.1-2.3.xcpng8.3 will be updated
      ---> Package sm-cli.x86_64 0:26.1.3-1.3.xcpng8.3 will be an update
      ---> Package sm-fairlock.x86_64 0:3.2.12-16.1.xcpng8.3 will be updated
      ---> Package sm-fairlock.x86_64 0:3.2.12-17.1.xcpng8.3 will be an update
      ---> Package squeezed.x86_64 0:25.33.1-2.3.xcpng8.3 will be updated
      ---> Package squeezed.x86_64 0:26.1.3-1.3.xcpng8.3 will be an update
      ---> Package ssmtp.x86_64 0:2.64-14.el7 will be updated
      ---> Package ssmtp.x86_64 0:2.64-14.1.xcpng8.3 will be an update
      ---> Package stunnel.x86_64 0:5.60-4.xcpng8.3 will be updated
      ---> Package stunnel.x86_64 0:5.60-5.xcpng8.3 will be an update
      ---> Package sudo.x86_64 0:1.9.15-4.1.xcpng8.3 will be updated
      ---> Package sudo.x86_64 0:1.9.15-5.1.xcpng8.3 will be an update
      ---> Package swtpm.x86_64 0:0.7.3-12.xcpng8.3 will be updated
      ---> Package swtpm.x86_64 0:0.7.3-12.1.xcpng8.3 will be an update
      ---> Package swtpm-libs.x86_64 0:0.7.3-12.xcpng8.3 will be updated
      ---> Package swtpm-libs.x86_64 0:0.7.3-12.1.xcpng8.3 will be an update
      ---> Package swtpm-tools.x86_64 0:0.7.3-12.xcpng8.3 will be updated
      ---> Package swtpm-tools.x86_64 0:0.7.3-12.1.xcpng8.3 will be an update
      ---> Package tcpdump.x86_64 14:4.9.2-3.el7 will be updated
      ---> Package tcpdump.x86_64 14:4.9.2-3.1.xcpng8.3 will be an update
      ---> Package trousers.x86_64 0:0.3.14-2.el7 will be updated
      ---> Package trousers.x86_64 0:0.3.15-11.1.xcpng8.3 will be an update
      --> Processing Dependency: trousers-lib(x86-64) = 0.3.15-11.1.xcpng8.3 for package: trousers-0.3.15-11.1.xcpng8.3.x86_64
      ---> Package varstored.x86_64 0:1.2.0-3.5.xcpng8.3 will be updated
      ---> Package varstored.x86_64 0:1.3.1-2.1.xcpng8.3 will be an update
      ---> Package varstored-guard.x86_64 0:25.33.1-2.3.xcpng8.3 will be updated
      ---> Package varstored-guard.x86_64 0:26.1.3-1.3.xcpng8.3 will be an update
      ---> Package varstored-tools.x86_64 0:1.2.0-3.5.xcpng8.3 will be updated
      ---> Package varstored-tools.x86_64 0:1.3.1-2.1.xcpng8.3 will be an update
      ---> Package vhd-tool.x86_64 0:25.33.1-2.3.xcpng8.3 will be updated
      ---> Package vhd-tool.x86_64 0:26.1.3-1.3.xcpng8.3 will be an update
      ---> Package wget.x86_64 0:1.14-15.el7_4.1 will be updated
      ---> Package wget.x86_64 0:1.21.4-1.1.xcpng8.3 will be an update
      ---> Package wsproxy.x86_64 0:25.33.1-2.3.xcpng8.3 will be updated
      ---> Package wsproxy.x86_64 0:26.1.3-1.3.xcpng8.3 will be an update
      ---> Package xapi-core.x86_64 0:25.33.1-2.3.xcpng8.3 will be updated
      ---> Package xapi-core.x86_64 0:26.1.3-1.3.xcpng8.3 will be an update
      ---> Package xapi-nbd.x86_64 0:25.33.1-2.3.xcpng8.3 will be updated
      ---> Package xapi-nbd.x86_64 0:26.1.3-1.3.xcpng8.3 will be an update
      ---> Package xapi-rrd2csv.x86_64 0:25.33.1-2.3.xcpng8.3 will be updated
      ---> Package xapi-rrd2csv.x86_64 0:26.1.3-1.3.xcpng8.3 will be an update
      ---> Package xapi-storage-script.x86_64 0:25.33.1-2.3.xcpng8.3 will be updated
      ---> Package xapi-storage-script.x86_64 0:26.1.3-1.3.xcpng8.3 will be an update
      ---> Package xapi-tests.x86_64 0:25.33.1-2.3.xcpng8.3 will be updated
      ---> Package xapi-tests.x86_64 0:26.1.3-1.3.xcpng8.3 will be an update
      ---> Package xapi-xe.x86_64 0:25.33.1-2.3.xcpng8.3 will be updated
      ---> Package xapi-xe.x86_64 0:26.1.3-1.3.xcpng8.3 will be an update
      ---> Package xcp-featured.x86_64 0:1.1.8-3.xcpng8.3 will be updated
      ---> Package xcp-featured.x86_64 0:1.1.8-6.xcpng8.3 will be an update
      ---> Package xcp-networkd.x86_64 0:25.33.1-2.3.xcpng8.3 will be updated
      ---> Package xcp-networkd.x86_64 0:26.1.3-1.3.xcpng8.3 will be an update
      ---> Package xcp-ng-release.x86_64 0:8.3.0-36 will be updated
      ---> Package xcp-ng-release.x86_64 0:8.3.0-37 will be an update
      ---> Package xcp-ng-release-config.x86_64 0:8.3.0-36 will be updated
      ---> Package xcp-ng-release-config.x86_64 0:8.3.0-37 will be an update
      ---> Package xcp-ng-release-presets.x86_64 0:8.3.0-36 will be updated
      ---> Package xcp-ng-release-presets.x86_64 0:8.3.0-37 will be an update
      ---> Package xcp-rrdd.x86_64 0:25.33.1-2.3.xcpng8.3 will be updated
      ---> Package xcp-rrdd.x86_64 0:26.1.3-1.3.xcpng8.3 will be an update
      ---> Package xen-dom0-libs.x86_64 0:4.17.5-23.2.xcpng8.3 will be updated
      ---> Package xen-dom0-libs.x86_64 0:4.17.6-4.1.xcpng8.3 will be an update
      ---> Package xen-dom0-tools.x86_64 0:4.17.5-23.2.xcpng8.3 will be updated
      ---> Package xen-dom0-tools.x86_64 0:4.17.6-4.1.xcpng8.3 will be an update
      ---> Package xen-hypervisor.x86_64 0:4.17.5-23.2.xcpng8.3 will be updated
      ---> Package xen-hypervisor.x86_64 0:4.17.6-4.1.xcpng8.3 will be an update
      ---> Package xen-libs.x86_64 0:4.17.5-23.2.xcpng8.3 will be updated
      ---> Package xen-libs.x86_64 0:4.17.6-4.1.xcpng8.3 will be an update
      ---> Package xen-tools.x86_64 0:4.17.5-23.2.xcpng8.3 will be updated
      ---> Package xen-tools.x86_64 0:4.17.6-4.1.xcpng8.3 will be an update
      ---> Package xenopsd.x86_64 0:25.33.1-2.3.xcpng8.3 will be updated
      ---> Package xenopsd.x86_64 0:26.1.3-1.3.xcpng8.3 will be an update
      ---> Package xenopsd-cli.x86_64 0:25.33.1-2.3.xcpng8.3 will be updated
      ---> Package xenopsd-cli.x86_64 0:26.1.3-1.3.xcpng8.3 will be an update
      ---> Package xenopsd-xc.x86_64 0:25.33.1-2.3.xcpng8.3 will be updated
      ---> Package xenopsd-xc.x86_64 0:26.1.3-1.3.xcpng8.3 will be an update
      ---> Package xo-lite.noarch 0:0.17.0-1.xcpng8.3 will be updated
      ---> Package xo-lite.noarch 0:0.19.0-1.xcpng8.3 will be an update
      ---> Package xs-openssl-libs.x86_64 1:1.1.1k-12.1.xcpng8.3 will be obsoleted
      --> Running transaction check
      ---> Package libtasn1-devel.x86_64 0:4.10-1.el7 will be installed
      ---> Package net-snmp-libs.x86_64 1:5.7.2-52.1.xcpng8.3 will be updated
      --> Processing Dependency: libnetsnmp.so.31()(64bit) for package: nut-2.8.0-2.el7.x86_64
      ---> Package nettle-devel.x86_64 0:2.7.1-9.el7_9 will be installed
      --> Processing Dependency: gmp-devel(x86-64) for package: nettle-devel-2.7.1-9.el7_9.x86_64
      ---> Package openssl-compat-10-libs.x86_64 0:1.0.2k-26.2.1.xcpng8.3 will be installed
      ---> Package p11-kit-devel.x86_64 0:0.23.5-3.el7 will be installed
      ---> Package perl-interpreter.noarch 4:5.16.3-6.el7 will be installed
      ---> Package trousers-lib.x86_64 0:0.3.15-11.1.xcpng8.3 will be installed
      ---> Package zlib-devel.x86_64 0:1.2.7-17.el7 will be installed
      --> Running transaction check
      ---> Package gmp-devel.x86_64 1:6.0.0-15.el7 will be installed
      ---> Package net-snmp-libs.x86_64 1:5.7.2-52.1.xcpng8.3 will be updated
      --> Processing Dependency: libnetsnmp.so.31()(64bit) for package: nut-2.8.0-2.el7.x86_64
      --> Finished Dependency Resolution
      Error: Package: nut-2.8.0-2.el7.x86_64 (@epel)
                 Requires: libnetsnmp.so.31()(64bit)
                 Removing: 1:net-snmp-libs-5.7.2-52.1.xcpng8.3.x86_64 (@xcp-ng-updates)
                     libnetsnmp.so.31()(64bit)
                 Updated By: 1:net-snmp-libs-5.9.3-8.1.xcpng8.3.x86_64 (xcp-ng-updates)
                    ~libnetsnmp.so.40()(64bit)
                 Available: 1:net-snmp-libs-5.7.2-33.el7_5.2.x86_64 (xcp-ng-base)
                     libnetsnmp.so.31()(64bit)
                 Available: 1:net-snmp-libs-5.7.2-51.1.xcpng8.3.x86_64 (xcp-ng-base)
                     libnetsnmp.so.31()(64bit)
                 Available: 1:net-snmp-libs-5.7.2-51.2.xcpng8.3.x86_64 (xcp-ng-base)
                     libnetsnmp.so.31()(64bit)
                 Available: 1:net-snmp-libs-5.7.2-51.3.xcpng8.3.x86_64 (xcp-ng-base)
                     libnetsnmp.so.31()(64bit)
       You could try using --skip-broken to work around the problem
       You could try running: rpm -Va --nofiles --nodigest
      
      

      From Xen-Orchestra, I get this:

      1(Command '['yum', 'update', '--disablerepo=*', '--enablerepo=xcp-ng-base,xcp-ng-updates', '-y']' failed with code: 1, stdout: 'Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile Excluding mirror: updates.xcp-ng.org * xcp-ng-base: mirrors.xcp-ng.org Excluding mirror: updates.xcp-ng.org * xcp-ng-updates: mirrors.xcp-ng.org Resolving Dependencies --> Running transaction check ---> Package bind-libs-lite.x86_64 32:9.9.4-61.el7_5.1 will be updated ---> Package bind-libs-lite.x86_64 32:9.9.4-63.1.xcpng8.3 will be an update ---> Package bind-license.noarch 32:9.9.4-61.el7_5.1 will be updated ---> Package bind-license.noarch 32:9.9.4-63.1.xcpng8.3 will be an update ---> Package blktap.x86_64 0:3.55.5-6.1.xcpng8.3 will be updated ---> Package blktap.x86_64 0:3.55.5-6.3.xcpng8.3 will be an update ---> Package broadcom-bnxt-en.x86_64 0:1.10.3_232.0.155.5-1.xcpng8.3 will be updated ---> Package broadcom-bn
      

      I thought of just downloading the ISO for xcp-ng 8.3 to apply this update and see if it fixes what could be a repo problem.

      I hope you guy can help me figure this out.

      posted in XCP-ng
      okynnorO
      okynnor
    • RE: No mem stats under Windows Server

      @dinhngtu You are correct - it is a domain controller running on Windows Server 2022.

      The XenOchestra commit is at 1c01f

      Should I try to reinstall the Xen Tools? I suspect that it is going to be a futile attempt though.

      --Update:
      I went ahead and removed XenTools. Reboots. Reinstalled XenTools. But this time, I selected the second options -- to allow XenTools I/O Tools to automatically update when the "Manage Citrix PV drivers via Windows Update" is turned off (which it is)....Windows Server didn't prompt for a reboot. When I checked XenOrchestra, boom!, the Memory usage was there!!

      That second option did the trick.

      posted in Management
      okynnorO
      okynnor
    • No mem stats under Windows Server

      I have an issue where there is no mem stats showing for my Windows server 2022. I don't know if it's isolated with this or all windows workstation or server clients.

      I have installed Xen Tools 9.4.1. Yet, it is not displaying the memory stats.

      Then, I also tried by uninstalling Xen Tools 9.4.1 and used Manage Citrix PV drivers via Windows Update. But that also didn't work.

      Lastly, I updated Xen Orchestra to the latest build (i.e. all commits) as of this post date, that didn't work either.

      Screenshot 2025-09-20 at 8.37.00 PM.png

      Thanks for your help & insights.

      posted in Management
      okynnorO
      okynnor
    • RE: windows 11 Support

      @Andrew So I need to run xcp-ng 8.3 in order to get vTPM.

      For those still running xcp ng v8.2.1 in production, would you recommend upgrading production to 8.3beta1? From the xcp-ng post, it seems to be very solid with some outstanding issues?

      Also, xenserver is also available. Any thoughts on interoperability of Xenserver and xcp-ng and XO from sources?

      posted in XCP-ng
      okynnorO
      okynnor
    • windows 11 Support

      I'm sure that by now, we should have Windows 11 vTPM support (& guest tools) on xcp-ng and Xen Ochestra, right? The last thread I found about this topic was from 2021.

      posted in XCP-ng
      okynnorO
      okynnor
    • How to restore vm and xo metadata from backups?

      I have experienced a catastrophic disaster while I tried to upgrade my rack servers. At first it worked very well by using the migration of VMs to the new server then assigning the new server as the master. Then, I decided that it was time to change the DHCP assigned address to take the place of the static ip , replacing the old server. Then all hell broke loose.

      the xsconsole no longer saw the pms, yet the vms were still running!

      decided to reboot the server to see if it's xsconsole not reading something and a reboot would solved it.

      That's when I realized that all my metadata were gone! the vms were gone. the storage repositories were gone.

      Yet, I know that the iSCSI repository, which stores all the vms, was still intact by looking at the mount of free vs. total space as presented in TrueNAS Core.

      After many tries, I was able to reattach the iSCSI repository to the new server running, of course, xcp-ng. But there were no VMs presented in presented in a new instance of Xen Orchestra (CE). I thought that if there's a way to restore the meta-data for XO config and XO backup, I would be able to restore everything. The data has been downloaded off TrueNAS and into my MacBook Pro. It seems that these strategies aren't working.

      I googled around to find out best practice or solutions to no avail.

      I hope that you can help me please! These VMs are business critical. If someone can help me, the business won't be burning come Monday morning.

      posted in Xen Orchestra
      okynnorO
      okynnor
    • RE: How do I backup XCP-ng Configuration to migrate to a SSD?

      @chon It's Jun 3, 2023. After three years, I'm going to finally do the migration to a new Dell server hardware. I'll update this thread for those who are interested. thanks.

      posted in Compute
      okynnorO
      okynnor
    • System Load: How to read colour coding

      Hi there,

      I am checking to see how loaded my servers are. When go to Dashboard >> Statistics and point to show me the "load", I'm shown mostly yellow with rare patches of green blocks.

      When I look at the hosts themselves at Home >> Hosts >> Stats, the graphical CPU visualization, shows the CPUs are all running under 12% usage.

      I've created a video to show you.

      posted in Xen Orchestra
      okynnorO
      okynnor
    • RE: cpu cores reported mismatched

      @olivierlambert Thanks. I understand Dom0 and VM0 principles. I didn't know that exited in
      xsconsole, resulting terminal being a VM.

      posted in Xen Orchestra
      okynnorO
      okynnor
    • RE: cpu cores reported mismatched

      @Andrew If I am understanding your reply on dom0 correctly, does this mean that when I into the xcp-ng terminal and type htop and lscpu and they are both reporting 8 cores instead of 24, that's correct?

      I have two identical servers. The other server, reports the right number of cores though.

      How do I reconcile the difference between the two servers?

      The only difference between them is the amount of ECC RAM (24GB vs 64GB) but I doubt that it would make a difference on this topi c.

      posted in Xen Orchestra
      okynnorO
      okynnor
    • cpu cores reported mismatched

      Hi,

      There is a weird issue happening because the number of cores reported between XO, Xcp-ng and lscpu + htop are different.

      XO and xcp-ng report that there are 24 logical cores. Great. Also the BIOS sees 2 physical CPUs x 6 physical cores = 24 logical cores.

      However, when I run lscpu and htop from the command line, they report that there are only 8 logical cores or 4 physical cores.

      Has anyone bumped into this issue before?

      are there 24 or 8 cores?

      posted in Xen Orchestra
      okynnorO
      okynnor
    • nVidia Tesla P4 for vgpu and Plex encoding

      Does anyone have experience with nVidia Tesla P4 with XCP-ng with XO and Plex Media Server running in a VM with transcoding enabled.

      posted in Compute vgpu
      okynnorO
      okynnor
    • RE: A Differential Restore in XO failed and I don't know why. Please help

      @danp Yes, all my VMs are up-to-date.
      Yes, I am running XO, the free and open sourced version.

      In addition, this happens to all my 11 VMs.

      posted in Xen Orchestra
      okynnorO
      okynnor
    • A Differential Restore in XO failed and I don't know why. Please help

      Hi,

      I was trying to restore one of four available differential backups. When I picked on and the location to restore, I was encountered with the following cryptic error. I hope someone can help me understand and solve this error.

      The error was in the logs under the Message column.

      Much appreciated.

      Values have same structure but are not reference-equal:
      
      Buffer(16) [Uint8Array] [
        11,
        238,
        222,
        110,
        103,
        86,
        77,
        110,
        169,
        135,
        15,
        157,
        26,
        10,
        151,
        26
      

      I should advise that doing a restore straight from the VM was successful. However, when done from the Backup -- Restore --> choose a VM and a differential backup, that fails.

      posted in Xen Orchestra
      okynnorO
      okynnor