@r1 modinfo displays a huge number of aliases (abrieviated, but can include the entire list if helpful at all):
root@xenserver class]# modinfo cdc-acm.ko
filename:       /lib/modules/4.4.0+10/extra/class/cdc-acm.ko
alias:          char-major-166-*
license:        GPL
description:    USB Abstract Control Model driver for USB modems and ISDN adapters
author:         Armin Fuerst, Pavel Machek, Johannes Erdfelt, Vojtech Pavlik, David Kubicek, Johan Hovold
srcversion:     4DA17ECECFACCD02EC1D87C
alias:          usb:v1519p0452d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v*p*d*dc*dsc*dp*ic02isc02ip06in*
alias:          usb:v*p*d*dc*dsc*dp*ic02isc02ip05in*
alias:          usb:v*p*d*dc*dsc*dp*ic02isc02ip04in*
alias:          usb:v*p*d*dc*dsc*dp*ic02isc02ip03in*
alias:          usb:v*p*d*dc*dsc*dp*ic02isc02ip02in*
alias:          usb:v*p*d*dc*dsc*dp*ic02isc02ip01in*
alias:          usb:v*p*d*dc*dsc*dp*ic02isc02ip00in*
alias:          usb:v058Bp0041d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v04E8p685Dd*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v04D8p000Bd*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v03EBp0030d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v04E7p6651d*dc*dsc*dp*ic02isc02ipFFin*
...
...
...
alias:          usb:v22B8p7000d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0ACEp1611d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0ACEp1608d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0ACEp1602d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v079Bp000Fd*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0482p0203d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0E8Dp3329d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0E8Dp0003d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0870p0001d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v17EFp7000d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v076Dp0006d*dc*dsc*dp*ic*isc*ip*in*
depends:
vermagic:       4.4.0+10 SMP mod_unload modversions
[root@xenserver class]#
insmod fails with similar error messages.
insmod: ERROR: could not insert module cdc-acm.ko: Invalid module format 
[root@xenserver class]# dmesg | tail -n 5                                
[529766.051521] cdc_acm: no symbol version for module_layout             
[529886.114801] cdc_acm: no symbol version for module_layout             
[530436.174773] cdc_acm: no symbol version for module_layout             
[593078.042958] cdc_acm: no symbol version for module_layout             
[593101.361321] cdc_acm: no symbol version for module_layout             
What I don't understand is why this module built using the docker container for XCP 7.5 would fail, unless the kernel was different.
[root@xenserver class]# uname -a
Linux xenserver 4.4.0+10 #1 SMP Thu Aug 9 14:42:20 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
[root@xenserver class]# md5sum /boot/initrd-4.4.0+10.img
def1ea3930f11bb46abfec42c3b9d6ec  /boot/initrd-4.4.0+10.img
[root@xenserver class]# file /boot/vmlinuz-4.4.0+10                                                                                                                               
/boot/vmlinuz-4.4.0+10: Linux kernel x86 boot executable bzImage, version 4.4.0+10 (mockbuild@6fb104f99393) #1 SMP Thu Aug 9 14:42:20 UTC, RO-rootFS, swap_dev 0x4, Normal VGA    
[root@xenserver class]# md5sum /boot/vmlinuz-4.4.0+10                                                                                                                             
d5de46e85a4047faf427932ecc41969f  /boot/vmlinuz-4.4.0+10                                                                                                                          
Any ideas? Is my kernel not actually 4.4.0+10? What I don't understand is why it is v4.4.0+10, but the rpm source package lists it as 4.4.52-4.0.7. Can there be 2 different versions of the same build somehow?
Thanks,
Eric