XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    XCP-ng 8.3 updates announcements and testing

    Scheduled Pinned Locked Moved News
    324 Posts 36 Posters 116.1k Views 53 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • O Offline
      ovicz @dinhngtu
      last edited by

      @dinhngtu no ouput from that command.

      D 1 Reply Last reply Reply Quote 0
      • D Offline
        dinhngtu Vates 🪐 XCP-ng Team @ovicz
        last edited by

        @ovicz Ok, I've contacted the storage team for a look.

        1 Reply Last reply Reply Quote 0
        • ronan-aR Offline
          ronan-a Vates 🪐 XCP-ng Team @ovicz
          last edited by

          @ovicz Can you share the /var/log/SMlog file from the master? It's quite strange considering that this driver is small and hasn't been modified.

          O 1 Reply Last reply Reply Quote 0
          • stormiS Offline
            stormi Vates 🪐 XCP-ng Team
            last edited by

            @ovicz I'd also like to have a look at /var/log/daemon.log after a failed VM startup attempt.

            O 1 Reply Last reply Reply Quote 0
            • A Online
              acebmxer
              last edited by acebmxer

              i have applied updates to my 2 amd home lab hosts. Ryzen 7700x and 7950x amd x670e mobo's. No issues to report. Windows vm migrated between hosts no isssues. No issues with windows vm booting with uefi enabled prior to update.

              1 Reply Last reply Reply Quote 1
              • O Offline
                ovicz @ronan-a
                last edited by

                @ronan-a SMlog.txt
                Attached. Please rename it as tgz and extract it as I couldn't uploaded as an archive file.

                1 Reply Last reply Reply Quote 0
                • O Offline
                  ovicz @stormi
                  last edited by ovicz

                  @stormi daemon.txt

                  Attached. Please rename it as tgz and extract it as I couldn't uploaded as an archive file.

                  Screenshot from 2025-12-17 14-04-50.png

                  Strange thing the disks don't appear in xen orchestra but they are on the drive:

                  [14:04 xcp-ng-akz zfs]# ls -l
                  total 34863861
                  -rw-r--r-- 1 root root 393216 Dec 10 11:19 2b94bb8f-b44d-4c3d-9844-0b2c80e7d11c.qcow2
                  -rw-r--r-- 1 root root 16969367552 Dec 17 09:15 37c89d4e-93d0-4f47-a340-4add9fb91307.qcow2
                  -rw-r--r-- 1 root root 5435228160 Dec 16 18:41 67d7cb86-864b-4bfc-9ec6-f54dbb9c9f45.qcow2
                  -rw-r--r-- 1 root root 10212737024 Dec 17 09:37 740d3e10-ebc9-42a3-bc7c-849f6bcc0e61.qcow2
                  -rw-r--r-- 1 root root 2685730816 Dec 16 14:52 76dc4b94-ad88-4514-87ef-99357b93daaf.qcow2
                  -rw-r--r-- 1 root root 197408 Dec 10 11:19 8158436c-327a-4dcf-ba49-56e73006ed66.qcow2
                  -rw-r--r-- 1 root root 11897602048 Dec 17 10:09 e219112b-73b7-46a4-8fcb-4ee8810b3625.qcow2
                  -rw-r--r-- 1 root root 11566120960 Dec 10 09:51 f5d157cb-39df-482b-a39d-432a90d60e89.qcow2
                  -rw-r--r-- 1 root root 1984 Dec 10 11:02 filelog.txt

                  [14:07 xcp-ng-akz zfs]# zfs list
                  NAME USED AVAIL REFER MOUNTPOINT
                  ZFS_Pool 33.3G 416G 33.2G /mnt/zfs
                  [14:07 xcp-ng-akz zfs]# zpool list
                  NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT
                  ZFS_Pool 464G 33.3G 431G - - 5% 7% 1.00x ONLINE -
                  [14:07 xcp-ng-akz zfs]# zpool status
                  pool: ZFS_Pool
                  state: ONLINE
                  config:

                  NAME        STATE     READ WRITE CKSUM
                  ZFS_Pool    ONLINE       0     0     0
                    sda       ONLINE       0     0     0
                  

                  errors: No known data errors

                  dthenotD 1 Reply Last reply Reply Quote 0
                  • dthenotD Online
                    dthenot Vates 🪐 XCP-ng Team @ovicz
                    last edited by dthenot

                    @ovicz Hello,

                    From what I saw in your logs, you have a non QCOW2 sm version, it made the QCOW2 VDIs not available to the storage stack and the XAPI lost them.
                    If you update again while enabling the QCOW2 repo:

                    yum update --enablerepo=xcp-ng-testing,xcp-ng-candidates,xcp-ng-qcow2
                    

                    A SR scan will make the VDI available to the XAPI. Though you will have to identify them and connect them to the VM manually, since this information was lost.

                    O 1 Reply Last reply Reply Quote 2
                    • stormiS Offline
                      stormi Vates 🪐 XCP-ng Team
                      last edited by

                      I added a warning to my initial announcement.

                      1 Reply Last reply Reply Quote 1
                      • O Offline
                        ovicz @dthenot
                        last edited by

                        @dthenot Screenshot from 2025-12-17 14-21-43.png

                        They appear now. I will try to identify them manually. Thanks for the tip.

                        1 Reply Last reply Reply Quote 0
                        • olivierlambertO Online
                          olivierlambert Vates 🪐 Co-Founder CEO
                          last edited by

                          Thanks for your feedback 🙂

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post