Applies to Fedora 17 too. +++ This bug was initially created as a clone of Bug #866981 +++ > Description of problem: tcm_vhost is not enabled in 3.6 kernels. > Version-Release number of selected component (if applicable): kernel 3.6.1-1.fc17. > How reproducible: Always. > Steps to Reproduce: 1. $ grep -r CONFIG_TCM_VHOST /usr/src/kernels/3.6.1-1.fc17.x86_64/.config > Actual results: # CONFIG_TCM_VHOST is not set > Expected results: CONFIG_TCM_VHOST=m > Additional info: http://lwn.net/Articles/508788/
For future reference, it would be good if you actually said why you want a module enabled. There's nothing at all about why this should be enabled in the report. I did it anyway since Justin already did a similar commit for F18.
(In reply to comment #1) > For future reference, it would be good if you actually said why you want a > module enabled. There's nothing at all about why this should be enabled in > the report. Sorry Josh, motivation is to be able to use virtio-scsi with the tcm_vhost fabric to allow SCSI commands sent from KVM guests to reach the backing store. http://wiki.qemu.org/Features/VirtioSCSI/TCM_Overview For example, using virtio-scsi with tcm_vhost and target_core_pscsi (SCSI pass-through backing store) allows KVM guests to send TRIM commands to the underlying device (e.g. a SSD drive).
(In reply to comment #2) > (In reply to comment #1) > > For future reference, it would be good if you actually said why you want a > > module enabled. There's nothing at all about why this should be enabled in > > the report. > > Sorry Josh, motivation is to be able to use virtio-scsi with the tcm_vhost > fabric to allow SCSI commands sent from KVM guests to reach the backing > store. > http://wiki.qemu.org/Features/VirtioSCSI/TCM_Overview > > For example, using virtio-scsi with tcm_vhost and target_core_pscsi (SCSI > pass-through backing store) allows KVM guests to send TRIM commands to the > underlying device (e.g. a SSD drive). Awesome. Thanks for the quick info! It's always good to have reasoning documented for why something was enabled.
kernel-3.6.3-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/kernel-3.6.3-1.fc17
Package kernel-3.6.3-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kernel-3.6.3-1.fc17' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-16669/kernel-3.6.3-1.fc17 then log in and leave karma (feedback).
kernel-3.6.3-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.