Jump To: Support > KB > Citrix > XenServer > Upgrade9

XenServer 9 upgrade issues

USB memory stick kills multipath SCSI SRs if plugged in at boot time

If you have a USB memory stick plugged in, it kills multipathing on the whole system. The USB memory stick appears as a SCSI device, but does not have a recognised vendor, so multipathing fails to initialise:

# multipath -ll
sde: broken device without vendor ID
# multipath -v9
[snip]
596.213238 | sde: vendor = UNKNOWN
596.213281 | sde: product = USB DISK 3.0
596.213323 | sde: rev = PMAP
596.214049 | find_hwe: found 0 hwtable matches for UNKNOWN:USB DISK 3.0:PMAP

Blank screen as installer boots

Likely to be down to a hard requirement for x86-64-v3 which excludes older CPUs (such as Sandy Bridge (gen 2) E5-2620 CPUs).

Check if avx2, bmi2 and fma are present in /proc/cpuinfo as these are necessary for XenServer 9.

Reference:

• https://www.linkedin.com/pulse/part-1-xenserver-9-x86-64-v3-wall-artur-ogloza-e8n8f/

Pre-upgrade checks fails with The following feature is not available on the target version: AUTO_UPDATE_SECUREBOOT_CERTIFICATE=1.0.0

Ensure you are using the latest XenServer 9 installation image (2026-07-16 or later, problems have been seen with 2026-06-23). You should also ensure your current XenServer 8.4 installation is fully-patched.

For completeness, you should also update the secure boot certificates on any VMs or templates and remove any snapshots that are not up-to-date. The following commands will lists all the affected VMs, templates and snapshots:

xe vm-list params=name-label,uuid secureboot-certificates-state=update_available
xe template-list params=name-label,uuid secureboot-certificates-state=update_available
xe snapshot-list params=name-label,uuid,snapshot-of secureboot-certificates-state=update_available

For each VM that needs updating, mark it to be updated on next reboot:

xe vm-update-secureboot-certificates-on-boot uuid=<VMUUID> mark=true

The status will then change to update_on_boot, e.g.:

[root@xenserver01 ~]# xe vm-list params=name-label,uuid,secureboot-certificates-state uuid=454274a3-f69e-f916-dc7d-831319a5c911
uuid ( RO)                             : 454274a3-f69e-f916-dc7d-831319a5c911
                       name-label ( RW): DC01
    secureboot-certificates-state ( RO): update_on_boot

After rebooting the VM, the status will change to ok, e.g.:

[root@xenserver01 ~]# xe vm-list params=name-label,uuid,secureboot-certificates-state uuid=454274a3-f69e-f916-dc7d-831319a5c911
uuid ( RO)                             : 454274a3-f69e-f916-dc7d-831319a5c911
                       name-label ( RW): DC01
    secureboot-certificates-state ( RO): ok

For templates, you will need to create a VM from the template, update its certificates and then create a new template after deleting the old.

For snapshots, delete any that are present.