On Fri, 2014-07-25 at 23:17 +0200, Cyril Brulebois wrote: > Control: tag -1 patch > > Ron <ron@debian.org> (2014-07-26): > > Hi, > > > > The virtio_scsi module got backported to the 3.2.39-1 kernel, > > but it appears it didn't get added to the virtio-modules udeb > > for the wheezy kernels -- which means you can switch to using > > it for an already installed wheezy guest in a VM, but you can't > > install a new VM configured to use it with the wheezy installer. > > > > Please consider adding this to virtio-modules for the wheezy > > branch to complete this (very welcome!) backport. > > Looking at the sid package, this module was added to the virtio-modules > package unconditionally (doesn't depend on the arch, as opposed to the > pci one); that happened in r20402, in preparation for 3.10.1-1. > > I've just looked at all linux-image-* binaries built from linux > 3.2.60-1+deb7u1, and all contain that module but two[*], so I'm not > entirely sure about its arch-independence. The attached patch (against > the wheezy svn branch) might do the work, or might need an extra '?'. > > [*] The two packages are the s390* -tape variants, which were dropped in > the meanwhile: > linux-image-3.2.0-4-s390x-tape_3.2.60-1+deb7u1_s390.deb > linux-image-3.2.0-4-s390x-tape_3.2.60-1+deb7u1_s390x.deb Those packages don't have *any* modules! I forget how they work - possibly they have the same release string as the regular package and can share their modules? Anyway, I think your patch will work. Ben. -- Ben Hutchings Always try to do things in chronological order; it's less confusing that way.
Attachment:
signature.asc
Description: This is a digitally signed message part