"Xenserver 8" with PVS Accelerator showing Full Orphan VDIs

infecticide

PVS Accelerator in the Citrix product uses tmpfs / MemorySR VDIs to cache disk blocks in Dom0 RAM for use with their Provisioning Services product.

It might be worth hiding them in XOA for Xenserver users since these will always show "Orphaned" and "Full".

You can see these under "Dashboard" --> "Health"

"Name" and "Description" is always "PVS cache VDI"

Melissa FR

Hi @infecticide, the fix for this issue has been been merged and will be available in the next release (5.100.1)

olivierlambert

Indeed, can you show the detailed VDI record? (xe vdi-param-list uuid=<UUID>)

infecticide

[root@REG-CXS-101-T ~]# xe vdi-param-list uuid=5db5b077-15ed-43c6-b19e-25a3ae4b5f44
uuid ( RO)                    : 5db5b077-15ed-43c6-b19e-25a3ae4b5f44
              name-label ( RW): PVS cache VDI
        name-description ( RW): PVS cache VDI
           is-a-snapshot ( RO): false
             snapshot-of ( RO): <not in database>
               snapshots ( RO):
           snapshot-time ( RO): 19700101T00:00:00Z
      allowed-operations (SRO): update; forget; destroy; copy
      current-operations (SRO):
                 sr-uuid ( RO): fe73433c-df41-9c1a-f305-4659789bb13f
           sr-name-label ( RO): tmpfs SR plugin
               vbd-uuids (SRO):
         crashdump-uuids (SRO):
            virtual-size ( RO): 25769803776
    physical-utilisation ( RO): 25769803776
                location ( RO): 5db5b077-15ed-43c6-b19e-25a3ae4b5f44
                    type ( RO): User
                sharable ( RO): false
               read-only ( RO): false
            storage-lock ( RO): false
                 managed ( RO): true
     parent ( RO) [DEPRECATED]: <not in database>
                 missing ( RO): false
            is-tools-iso ( RO): false
            other-config (MRW):
           xenstore-data (MRO):
               sm-config (MRO):
                 on-boot ( RW): persist
           allow-caching ( RW): false
         metadata-latest ( RO): false
        metadata-of-pool ( RO): <not in database>
                    tags (SRW):
             cbt-enabled ( RO): false



[root@REG-CXS-101-T ~]# xe vdi-param-list uuid=d18ce3b9-f147-40ea-bfb3-c55bad41b039
uuid ( RO)                    : d18ce3b9-f147-40ea-bfb3-c55bad41b039
              name-label ( RW): PVS cache VDI
        name-description ( RW): PVS cache VDI
           is-a-snapshot ( RO): false
             snapshot-of ( RO): <not in database>
               snapshots ( RO):
           snapshot-time ( RO): 19700101T00:00:00Z
      allowed-operations (SRO): update; forget; destroy; copy
      current-operations (SRO):
                 sr-uuid ( RO): 9cd30aca-9bee-f0fe-3b36-aa01ddcc60e6
           sr-name-label ( RO): MemorySR
               vbd-uuids (SRO):
         crashdump-uuids (SRO):
            virtual-size ( RO): 25769803776
    physical-utilisation ( RO): 25769803776
                location ( RO): d18ce3b9-f147-40ea-bfb3-c55bad41b039
                    type ( RO): User
                sharable ( RO): false
               read-only ( RO): false
            storage-lock ( RO): false
                 managed ( RO): true
     parent ( RO) [DEPRECATED]: <not in database>
                 missing ( RO): false
            is-tools-iso ( RO): false
            other-config (MRW):
           xenstore-data (MRO):
               sm-config (MRO):
                 on-boot ( RW): persist
           allow-caching ( RW): false
         metadata-latest ( RO): false
        metadata-of-pool ( RO): <not in database>
                    tags (SRW):
             cbt-enabled ( RO): false

olivierlambert

Okay so indeed there's 0 info outside a specific name/description. I suppose this can't be changed right?

infecticide

@olivierlambert no, other than the size parameter this is all configured automatically by the PVS Accelerator software in Xencenter / Xenserver 8.

I suspect all you have to determine it's identity is:

If (name-label -AND name-description eq "PVS cache VDI"); then "hide"

olivierlambert

Issue created, we should have a fix for a next release (likely September release)

Melissa FR

Hi @infecticide, the fix for this issue has been been merged and will be available in the next release (5.100.1)