RE: [Xen-devel] Modules in domU kernel config?

["Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>]

 > I noticed the follow options compiled as modules in the xenU_x86_32
> defconfig:
> 
> CONFIG_BLK_DEV_LOOP=m
> CONFIG_BLK_DEV_NBD=m
> CONFIG_SCSI=m
> CONFIG_BLK_DEV_SD=m
> CONFIG_FAT_FS=m
> CONFIG_MSDOS_FS=m
> CONFIG_VFAT_FS=m
> CONFIG_CRYPTO_MD5=m
> CONFIG_CRYPTO_CRC32C=m
> CONFIG_LIBCRC32C=m
> 
> Is this intentional?  I would expect DEV_LOOP=y and would not 
> expect CONFIG_SCSI to be in there at all (if it's loaded, 
> it'll take over major
> 8 and cause problems if you attempt to expose /dev/sda?).

I think we've always had iscsi as a module, mainly for folks using iscsi
from domU.

These days, most of the testing is on -xen kernels rather than -xen0/U.

Ian
 
> The last time the config was touched was 
> 690fc13948db7651eabbce8cc4b963342c8634dd which was updating 
> to subarch layout.
> 
> Regards,
> 
> Anthony Liguori
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
> 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel