From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>,
Ronnie Sahlberg <ronniesahlberg@gmail.com>
Subject: Re: [Qemu-devel] virtio-scsi vs. virtio-blk
Date: Fri, 10 Aug 2012 12:30:35 +0200 [thread overview]
Message-ID: <5024E2CB.2050208@redhat.com> (raw)
In-Reply-To: <5024E232.5020706@profihost.ag>
Il 10/08/2012 12:28, Stefan Priebe - Profihost AG ha scritto:
> I'm using iscsi. So no raw or qcow2.
Ok, then you need to use scsi-block as your device instead of scsi-disk
or scsi-hd. This will disable the QEMU SCSI emulation and let your VM
talk directly to the NAS.
CCing Ronnie who may be interested in bug reports since I'm on holiday
starting "soon".
Paolo
>
> Thanks,
>
> Stefan
>
> Am 10.08.2012 12:20, schrieb Paolo Bonzini:
>> Il 10/08/2012 11:22, Stefan Priebe - Profihost AG ha scritto:
>>> virtio-scsi is now working fine. Could you please help me to get discard
>>> / trim running? I can't find any information what is needed to get
>>> discard / trim working.
>>
>> You need to add discard_granularity=NNN, where NNN is usually 512 for
>> raw and the cluster size (65536) for qcow2.
>>
>> However, discard is supported only for XFS on raw, and on qcow2 it will
>> not reclaim space---the space will only be reused for future qcow2
>> allocation.
>>
>> Better support for discard on raw (other filesystems + block devices),
>> and more efficient support also on other formats is on my todo list for
>> the future. However, an efficient implementation unfortunately requires
>> changes at all levels including the kernel.
>>
>> I hope to present something about it at KVM Forum.
>>
>> Paolo
>>
next prev parent reply other threads:[~2012-08-10 10:30 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 15:21 [Qemu-devel] virtio-scsi vs. virtio-blk Stefan Priebe
2012-08-08 16:17 ` Paolo Bonzini
2012-08-08 17:12 ` Stefan Priebe
2012-08-08 17:37 ` Paolo Bonzini
2012-08-09 6:13 ` Stefan Priebe
2012-08-09 7:01 ` Paolo Bonzini
2012-08-09 7:07 ` Stefan Priebe
2012-08-09 7:19 ` Paolo Bonzini
2012-08-09 7:41 ` Stefan Priebe
2012-08-09 7:53 ` Paolo Bonzini
2012-08-09 8:00 ` Stefan Priebe
2012-08-09 8:03 ` Paolo Bonzini
2012-08-09 9:18 ` Stefan Hajnoczi
2012-08-09 10:17 ` Stefan Priebe - Profihost AG
2012-08-09 11:04 ` Stefan Hajnoczi
2012-08-09 11:10 ` Paolo Bonzini
2012-08-09 11:24 ` Stefan Priebe - Profihost AG
2012-08-09 12:08 ` Stefan Priebe - Profihost AG
2012-08-09 12:19 ` Paolo Bonzini
2012-08-09 12:31 ` Stefan Priebe - Profihost AG
2012-08-09 12:44 ` Paolo Bonzini
2012-08-09 15:41 ` Stefan Priebe - Profihost AG
2012-08-09 12:52 ` ronnie sahlberg
2012-08-09 13:15 ` Paolo Bonzini
2012-08-09 13:39 ` Stefan Priebe - Profihost AG
2012-08-09 13:42 ` Paolo Bonzini
2012-08-09 13:52 ` Stefan Priebe - Profihost AG
2012-08-09 14:35 ` Paolo Bonzini
2012-08-09 14:25 ` Stefan Priebe - Profihost AG
2012-08-10 9:22 ` Stefan Priebe - Profihost AG
2012-08-10 10:20 ` Paolo Bonzini
2012-08-10 10:28 ` Stefan Priebe - Profihost AG
2012-08-10 10:30 ` Paolo Bonzini [this message]
2012-08-10 11:12 ` ronnie sahlberg
2012-08-10 11:57 ` Stefan Priebe - Profihost AG
2012-08-10 12:04 ` ronnie sahlberg
2012-08-10 12:14 ` Stefan Priebe - Profihost AG
2012-08-10 12:24 ` ronnie sahlberg
2012-08-10 12:35 ` Stefan Priebe - Profihost AG
2012-08-10 12:39 ` Paolo Bonzini
2012-08-10 12:43 ` Stefan Priebe - Profihost AG
2012-08-10 11:20 ` ronnie sahlberg
2012-08-10 11:54 ` Stefan Priebe - Profihost AG
2012-08-10 11:58 ` ronnie sahlberg
2012-08-10 12:38 ` Stefan Priebe - Profihost AG
2012-08-10 11:49 ` Stefan Priebe - Profihost AG
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5024E2CB.2050208@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=ronniesahlberg@gmail.com \
--cc=s.priebe@profihost.ag \
--cc=stefanha@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.