Hello,
after reading the "invitation" for some one-off questions without
subscribing excuse my disturbing, please.
At first my setup of host:
* in general Debian Wheezy
* Kernel: 3.11-0.bpo.2-amd64
(http://packages.debian.org/wheezy-backports/linux-image-3.11-0.bpo.2-amd64)
* LVM 2.02.98 (http://packages.debian.org/jessie/lvm2)
* thin-provisioning-tools 0.2.8-1
(http://packages.debian.org/jessie/thin-provisioning-tools)
* Qemu-KVM: 1.7.0 (http://packages.debian.org/jessie/qemu-kvm)
The new kernel and dirty things from Jessie are for working thin volumes
with discard on my ssd. Everything's fine up to this point.
Afterwards I start a guest (also Debian Wheezy) over the following
command (over libvirt) as root (for test only):
kvm [...] -drive
file=/dev/ssd0/sarabi,if=none,id=drive-scsi0-0-0-0,format=raw,discard=unmap
-device
scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
[...]
Neither lsblk -D nor the try of fstrim ends positive. Both say that
discard is not supported.
I read that guests need at least kernel 3.4 to support discard (and
virtio-scsi). But the same backports kernel 3.11 did not changed anything.
Did I understand something wrong? Is the command wrong? Are any
requirements not met?
Bye Markus
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html