On Tue, Aug 23, 2011 at 12:25 PM, Kevin Wolf wrote:
> Am 22.08.2011 23:01, schrieb Anthony Liguori:
>> On 08/22/2011 03:48 PM, Ryan Harper wrote:
>>> * Stefan Hajnoczi [2011-08-22 15:32]:
We wouldn't rm -rf block/* because we still need qemu-nbd. It
probably makes sense to keep what we
Am 22.08.2011 23:01, schrieb Anthony Liguori:
> On 08/22/2011 03:48 PM, Ryan Harper wrote:
>> * Stefan Hajnoczi [2011-08-22 15:32]:
>>> We wouldn't rm -rf block/* because we still need qemu-nbd. It
>>> probably makes sense to keep what we have today. I'm talking more
>>> about a shift from writi
On Mon, Aug 22, 2011 at 04:01:08PM -0500, Anthony Liguori wrote:
> On 08/22/2011 03:48 PM, Ryan Harper wrote:
> >* Stefan Hajnoczi [2011-08-22 15:32]:
> >>We wouldn't rm -rf block/* because we still need qemu-nbd. It
> >>probably makes sense to keep what we have today. I'm talking more
> >>about
On 08/22/2011 03:48 PM, Ryan Harper wrote:
* Stefan Hajnoczi [2011-08-22 15:32]:
We wouldn't rm -rf block/* because we still need qemu-nbd. It
probably makes sense to keep what we have today. I'm talking more
about a shift from writing our own image format to integrating
existing storage supp
* Stefan Hajnoczi [2011-08-22 15:32]:
> On Mon, Aug 22, 2011 at 8:04 PM, Anthony Liguori
> wrote:
> > On 08/22/2011 08:34 AM, Stefan Hajnoczi wrote:
> >>
> >> At KVM Forum Kevin, Christoph, and I had an opportunity to get
> >> together for a Block Layer BoF. We went through the recent "roadmap"
On Mon, Aug 22, 2011 at 8:04 PM, Anthony Liguori wrote:
> On 08/22/2011 08:34 AM, Stefan Hajnoczi wrote:
>>
>> At KVM Forum Kevin, Christoph, and I had an opportunity to get
>> together for a Block Layer BoF. We went through the recent "roadmap"
>> mailing list thread and touched on each proposed
On 08/22/2011 08:34 AM, Stefan Hajnoczi wrote:
At KVM Forum Kevin, Christoph, and I had an opportunity to get
together for a Block Layer BoF. We went through the recent "roadmap"
mailing list thread and touched on each proposed feature.
Here is the block layer roadmap wiki page:
http://wiki.qem
On Mon, Aug 22, 2011 at 09:27:12AM -0500, Ryan Harper wrote:
> * Stefan Hajnoczi [2011-08-22 08:35]:
> > At KVM Forum Kevin, Christoph, and I had an opportunity to get
> > together for a Block Layer BoF. We went through the recent "roadmap"
> > mailing list thread and touched on each proposed fea
* Stefan Hajnoczi [2011-08-22 08:35]:
> At KVM Forum Kevin, Christoph, and I had an opportunity to get
> together for a Block Layer BoF. We went through the recent "roadmap"
> mailing list thread and touched on each proposed feature.
>
> Here is the block layer roadmap wiki page:
> http://wiki.q
At KVM Forum Kevin, Christoph, and I had an opportunity to get
together for a Block Layer BoF. We went through the recent "roadmap"
mailing list thread and touched on each proposed feature.
Here is the block layer roadmap wiki page:
http://wiki.qemu.org/BlockRoadmap
Kevin: I have moved the runti
Frediano suggested:
Enhanced volume key in qcow3
* luks-like key scheme that allows changing passphrase without
re-encrypting image data
On Thu, Jul 28, 2011 at 2:10 PM, Kevin Wolf wrote:
> Am 28.07.2011 14:54, schrieb Stefan Hajnoczi:
>> On Thu, Jul 28, 2011 at 1:35 PM, Kevin Wolf wrote:
>>> Am 28.07.2011 14:09, schrieb Christoph Hellwig:
On Wed, Jul 27, 2011 at 01:37:31PM +0100, Stefan Hajnoczi wrote:
> Coroutines in th
Am 28.07.2011 14:54, schrieb Stefan Hajnoczi:
> On Thu, Jul 28, 2011 at 1:35 PM, Kevin Wolf wrote:
>> Am 28.07.2011 14:09, schrieb Christoph Hellwig:
>>> On Wed, Jul 27, 2011 at 01:37:31PM +0100, Stefan Hajnoczi wrote:
Coroutines in the block layer [Kevin]
* Programming model to simplif
On Thu, Jul 28, 2011 at 1:35 PM, Kevin Wolf wrote:
> Am 28.07.2011 14:09, schrieb Christoph Hellwig:
>> On Wed, Jul 27, 2011 at 01:37:31PM +0100, Stefan Hajnoczi wrote:
>>> Coroutines in the block layer [Kevin]
>>> * Programming model to simplify block drivers without blocking QEMU threads
>>
>>
On 07/28/2011 07:09 AM, Christoph Hellwig wrote:
On Wed, Jul 27, 2011 at 01:37:31PM +0100, Stefan Hajnoczi wrote:
Coroutines in the block layer [Kevin]
* Programming model to simplify block drivers without blocking QEMU threads
Can anyone explain what the whole point of this is? It really j
Am 28.07.2011 14:09, schrieb Christoph Hellwig:
> On Wed, Jul 27, 2011 at 01:37:31PM +0100, Stefan Hajnoczi wrote:
>> Coroutines in the block layer [Kevin]
>> * Programming model to simplify block drivers without blocking QEMU threads
>
> Can anyone explain what the whole point of this is? It re
Am 28.07.2011 14:08, schrieb Christoph Hellwig:
> On Thu, Jul 28, 2011 at 12:05:43PM +0200, Kevin Wolf wrote:
>> Another item that just came up on IRC again: Allow guests to toggle WCE,
>> so that we finally can get rid of the cache=writethrough default. We
>> should definitely get this done before
On Thu, Jul 28, 2011 at 02:15:38PM +0200, Frediano Ziglio wrote:
>
> This has nothing (or few) to do with threads. Instead of splitting
> functions in callbacks at every synchronous function it allow to write
> more readable code.
Thanks for repeating my statement that it doesn't fix the real thi
2011/7/28 Christoph Hellwig :
> On Wed, Jul 27, 2011 at 01:37:31PM +0100, Stefan Hajnoczi wrote:
>> Coroutines in the block layer [Kevin]
>> * Programming model to simplify block drivers without blocking QEMU threads
>
> Can anyone explain what the whole point of this is? It really just is
> a bi
On Wed, Jul 27, 2011 at 01:37:31PM +0100, Stefan Hajnoczi wrote:
> Coroutines in the block layer [Kevin]
> * Programming model to simplify block drivers without blocking QEMU threads
Can anyone explain what the whole point of this is? It really just is
a bit of syntactic sugar for the current as
On Thu, Jul 28, 2011 at 12:05:43PM +0200, Kevin Wolf wrote:
> Another item that just came up on IRC again: Allow guests to toggle WCE,
> so that we finally can get rid of the cache=writethrough default. We
> should definitely get this done before 1.0.
Guest toggling is nice and cool, but the real
On Wed, Jul 27, 2011 at 1:37 PM, Stefan Hajnoczi wrote:
> =Changes where I am not aware of firm plans=
qcow2 online resize
* Handle snapshots
* Support shrinking
qed online resize
* Support shrinking
Am 27.07.2011 14:37, schrieb Stefan Hajnoczi:
> Hi,
> Here is a list of block layer and storage changes that have been discussed.
> It
> is useful to have a roadmap of changes in order to avoid duplication, allow
> more developers to contribute, and to communicate the direction of storage in
> QE
On 07/27/2011 07:37 AM, Stefan Hajnoczi wrote:
Hi,
Here is a list of block layer and storage changes that have been discussed. It
is useful to have a roadmap of changes in order to avoid duplication, allow
more developers to contribute, and to communicate the direction of storage in
QEMU.
Than
Hi,
Here is a list of block layer and storage changes that have been discussed. It
is useful to have a roadmap of changes in order to avoid duplication, allow
more developers to contribute, and to communicate the direction of storage in
QEMU.
I suggest we first do a braindump of all changes that
25 matches
Mail list logo
