(2015/01/26 19:33), Kevin Wolf wrote:
Am 26.01.2015 um 10:52 hat Teruaki Ishizaki geschrieben:
Hi, Kevin
Thanks for your review!
(2015/01/23 22:53), Kevin Wolf wrote:
Am 23.01.2015 um 09:24 hat Teruaki Ishizaki geschrieben:
Previously, qemu block driver of sheepdog used hard-coded VDI object
Am 26.01.2015 um 10:52 hat Teruaki Ishizaki geschrieben:
> Hi, Kevin
>
> Thanks for your review!
>
> (2015/01/23 22:53), Kevin Wolf wrote:
> >Am 23.01.2015 um 09:24 hat Teruaki Ishizaki geschrieben:
> >>Previously, qemu block driver of sheepdog used hard-coded VDI object size.
> >>This patch enab
Hi, Kevin
Thanks for your review!
(2015/01/23 22:53), Kevin Wolf wrote:
Am 23.01.2015 um 09:24 hat Teruaki Ishizaki geschrieben:
Previously, qemu block driver of sheepdog used hard-coded VDI object size.
This patch enables users to handle "block_size_shift" value for
calculating VDI object siz
Kevin Wolf writes:
> Am 23.01.2015 um 09:24 hat Teruaki Ishizaki geschrieben:
>> Previously, qemu block driver of sheepdog used hard-coded VDI object size.
>> This patch enables users to handle "block_size_shift" value for
>> calculating VDI object size.
>>
>> When you start qemu, you don't need
Am 23.01.2015 um 09:24 hat Teruaki Ishizaki geschrieben:
> Previously, qemu block driver of sheepdog used hard-coded VDI object size.
> This patch enables users to handle "block_size_shift" value for
> calculating VDI object size.
>
> When you start qemu, you don't need to specify additional comma
Previously, qemu block driver of sheepdog used hard-coded VDI object size.
This patch enables users to handle "block_size_shift" value for
calculating VDI object size.
When you start qemu, you don't need to specify additional command option.
But when you create the VDI which doesn't have default
