Bug#686636: Please backport virtio-scsi to wheezy
On Fri, 2014-07-25 at 23:17 +0200, Cyril Brulebois wrote: Control: tag -1 patch Ron r...@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. signature.asc Description: This is a digitally signed message part
Bug#686636: Please backport virtio-scsi to wheezy
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. Thanks! Ron -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686636: Please backport virtio-scsi to wheezy
Control: tag -1 patch Ron r...@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 Mraw, KiBi. Index: debian/installer/modules/virtio-modules === --- debian/installer/modules/virtio-modules (revision 21632) +++ debian/installer/modules/virtio-modules (working copy) @@ -1,6 +1,7 @@ virtio_net virtio_blk virtio_balloon +virtio_scsi # Some architectures do not have PCI bus virtio_pci ? Index: debian/changelog === --- debian/changelog (revision 21632) +++ debian/changelog (working copy) @@ -67,6 +67,9 @@ - drm/vmwgfx: Fix incorrect write to read-only register v2: - drm/radeon: stop poisoning the GART TLB + [ Cyril Brulebois ] + * Add virtio_scsi to the virtio-modules udeb (Closes: #686636). + -- Ben Hutchings b...@decadent.org.uk Mon, 21 Jul 2014 02:42:10 +0100 linux (3.2.60-1+deb7u2) wheezy-security; urgency=medium signature.asc Description: Digital signature
Bug#686636: Please backport virtio-scsi to wheezy
Package: linux Version: 3.2.23-1 Severity: wishlist Virtio SCSI a new driver/transport for block storage for paravirtualized systems. It replaces the older limited in many ways virtio-blk and is implemented by basically passing through SCSI over virtio. Hence devices appear as regular SCSI devices like /dev/sda instead of /dev/vda, SCSI passthrough can be easily implemented, multiple LUNs can be supported without provisioning a PCI card for each etc. http://wiki.qemu.org/Features/VirtioSCSI On the host side, virtio-scsi is supported by qemu(-kvm) = 1.1 (in wheezy) or by a kernel vhost driver for LIO which is still experimental and merged in v3.6 as a staging driver. virtio-scsi is the guest driver for supporting such devices, i.e. it's needed in a guest system configured with one or more virtio-scsi devices. It was first included in Linux v3.4 with some features/bugfixes in v3.6: 59057fb [SCSI] virtio-scsi: Add vdrv-scan for post VIRTIO_CONFIG_S_DRIVER_OK LU 365a715 [SCSI] virtio-scsi: hotplug support for virtio-scsi 2bd37f0 [SCSI] virtio-scsi: split scatterlist per target bce750b [SCSI] virtio-scsi: release sg_lock after add_buf 139fe45 [SCSI] virtio-scsi: split locking per vq b5ee8f2 [SCSI] virtio-scsi: unlock during kick e4594bb [SCSI] virtio_scsi: fix TMF use-after-free 4fe74b1 [SCSI] virtio-scsi: SCSI driver for QEMU based virtual machines (the last two are v3.4, the rest are v3.6) I believe it's important for wheezy to support being a guest in such configurations, as I expect virtio-scsi to be gradually adopted during the wheezy lifecycle. The driver is mostly self-contained and straightforward to backport (I wouldn't ask otherwise): The above commits cherry-picked against v3.2.28 result in the following: drivers/scsi/Kconfig|8 + drivers/scsi/Makefile |1 + drivers/scsi/virtio_scsi.c | 803 + drivers/virtio/virtio.c |5 +- include/linux/virtio.h |1 + include/linux/virtio_ids.h |1 + include/linux/virtio_scsi.h | 123 + 7 files changed, 941 insertions(+), 1 deletion(-) The v3.6 could be risky, considering they haven't been released yet and haven't seen much testing. If you prefer merging just v3.4's 4fe74b1/e4594bb instead, the stat is: drivers/scsi/Kconfig|8 + drivers/scsi/Makefile |1 + drivers/scsi/virtio_scsi.c | 596 + include/linux/virtio_ids.h |1 + include/linux/virtio_scsi.h | 114 +++ 5 files changed, 720 insertions(+) Thanks, Faidon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
