On 06/27/2011 10:48 AM, Kevin Wolf wrote:
Am 26.06.2011 14:50, schrieb Dor Laor:
On 06/24/2011 12:28 PM, Stefan Hajnoczi wrote:
On Sun, Jun 19, 2011 at 5:02 PM, Dor Laor wrote:
On 06/18/2011 12:17 PM, Stefan Hajnoczi wrote:
On Sat, Jun 18, 2011 at 10:15 AM, Stefan Hajnoczi
wrote:
On F
Am 26.06.2011 14:50, schrieb Dor Laor:
> On 06/24/2011 12:28 PM, Stefan Hajnoczi wrote:
>> On Sun, Jun 19, 2011 at 5:02 PM, Dor Laor wrote:
>>> On 06/18/2011 12:17 PM, Stefan Hajnoczi wrote:
On Sat, Jun 18, 2011 at 10:15 AM, Stefan Hajnoczi
wrote:
>
> On Fri, Jun 17, 2011
On 06/24/2011 12:28 PM, Stefan Hajnoczi wrote:
On Sun, Jun 19, 2011 at 5:02 PM, Dor Laor wrote:
On 06/18/2011 12:17 PM, Stefan Hajnoczi wrote:
On Sat, Jun 18, 2011 at 10:15 AM, Stefan Hajnoczi
wrote:
On Fri, Jun 17, 2011 at 1:31 PM, Marcelo Tosatti
wrote:
On Thu, Jun 16, 2011 at 04:30
On Sun, Jun 19, 2011 at 5:02 PM, Dor Laor wrote:
> On 06/18/2011 12:17 PM, Stefan Hajnoczi wrote:
>>
>> On Sat, Jun 18, 2011 at 10:15 AM, Stefan Hajnoczi
>> wrote:
>>>
>>> On Fri, Jun 17, 2011 at 1:31 PM, Marcelo Tosatti
>>> wrote:
On Thu, Jun 16, 2011 at 04:30:18PM +0100, Stefan Hajno
On 06/18/2011 12:17 PM, Stefan Hajnoczi wrote:
On Sat, Jun 18, 2011 at 10:15 AM, Stefan Hajnoczi wrote:
On Fri, Jun 17, 2011 at 1:31 PM, Marcelo Tosatti wrote:
On Thu, Jun 16, 2011 at 04:30:18PM +0100, Stefan Hajnoczi wrote:
On Thu, Jun 16, 2011 at 11:52:43AM -0300, Marcelo Tosatti wrote:
Th
On Sat, Jun 18, 2011 at 10:15 AM, Stefan Hajnoczi wrote:
> On Fri, Jun 17, 2011 at 1:31 PM, Marcelo Tosatti wrote:
>> On Thu, Jun 16, 2011 at 04:30:18PM +0100, Stefan Hajnoczi wrote:
>>> On Thu, Jun 16, 2011 at 11:52:43AM -0300, Marcelo Tosatti wrote:
>>> This approach does not use the backing fi
On Fri, Jun 17, 2011 at 1:31 PM, Marcelo Tosatti wrote:
> On Thu, Jun 16, 2011 at 04:30:18PM +0100, Stefan Hajnoczi wrote:
>> On Thu, Jun 16, 2011 at 11:52:43AM -0300, Marcelo Tosatti wrote:
>> This approach does not use the backing file feature?
>>
>> > blkstream block driver:
>> >
>> > - Maintai
On Fri, Jun 17, 2011 at 10:36:21AM +0200, Kevin Wolf wrote:
> Am 16.06.2011 16:52, schrieb Marcelo Tosatti:
> > On Thu, Jun 16, 2011 at 03:08:30PM +0200, Kevin Wolf wrote:
> >> Am 16.06.2011 14:49, schrieb Avi Kivity:
> >>> On 06/16/2011 03:35 PM, Kevin Wolf wrote:
> * Image streaming is a nor
On Thu, Jun 16, 2011 at 04:30:18PM +0100, Stefan Hajnoczi wrote:
> On Thu, Jun 16, 2011 at 11:52:43AM -0300, Marcelo Tosatti wrote:
> This approach does not use the backing file feature?
>
> > blkstream block driver:
> >
> > - Maintain in memory whether given block is allocated in local image,
>
On Fri, Jun 17, 2011 at 10:22 AM, Kevin Wolf wrote:
> Am 17.06.2011 10:57, schrieb Stefan Hajnoczi:
>> On Fri, Jun 17, 2011 at 9:36 AM, Kevin Wolf wrote:
>>> By the way, we'll get problems with the colon syntax. Without -blockdev
>>> we'll have to invent a new syntax, maybe with brackets:
>>>
>>>
On Fri, Jun 17, 2011 at 10:36:21AM +0200, Kevin Wolf wrote:
> Am 16.06.2011 16:52, schrieb Marcelo Tosatti:
> > On Thu, Jun 16, 2011 at 03:08:30PM +0200, Kevin Wolf wrote:
> >> Am 16.06.2011 14:49, schrieb Avi Kivity:
> >>> On 06/16/2011 03:35 PM, Kevin Wolf wrote:
> * Image streaming is a nor
On Thu, Jun 16, 2011 at 04:30:18PM +0100, Stefan Hajnoczi wrote:
> On Thu, Jun 16, 2011 at 11:52:43AM -0300, Marcelo Tosatti wrote:
> This approach does not use the backing file feature?
Not directly. For block copy, the destination (or source) images might
share the same backing file (this is a r
On 06/17/2011 03:36 AM, Kevin Wolf wrote:
Am 16.06.2011 16:52, schrieb Marcelo Tosatti:
On Thu, Jun 16, 2011 at 03:08:30PM +0200, Kevin Wolf wrote:
Over this scheme, you'd have:
1) Block copy.
Reopen image to be copied with
blkstream:/path/to/current-image:/path/to/destination-image,
background
Am 17.06.2011 10:57, schrieb Stefan Hajnoczi:
> On Fri, Jun 17, 2011 at 9:36 AM, Kevin Wolf wrote:
>> By the way, we'll get problems with the colon syntax. Without -blockdev
>> we'll have to invent a new syntax, maybe with brackets:
>>
>> blkstream:[nbd:localhost]:out.qcow2
>
> Embedding block dr
On Fri, Jun 17, 2011 at 9:36 AM, Kevin Wolf wrote:
> By the way, we'll get problems with the colon syntax. Without -blockdev
> we'll have to invent a new syntax, maybe with brackets:
>
> blkstream:[nbd:localhost]:out.qcow2
Embedding block driver options in filenames is getting worse as time
goes
Am 16.06.2011 16:52, schrieb Marcelo Tosatti:
> On Thu, Jun 16, 2011 at 03:08:30PM +0200, Kevin Wolf wrote:
>> Am 16.06.2011 14:49, schrieb Avi Kivity:
>>> On 06/16/2011 03:35 PM, Kevin Wolf wrote:
* Image streaming is a normal image file plus copy-on-read plus a
background task that copi
Am 16.06.2011 16:38, schrieb Marcelo Tosatti:
> On Thu, Jun 16, 2011 at 02:35:37PM +0200, Kevin Wolf wrote:
>> Am 14.06.2011 20:18, schrieb Stefan Hajnoczi:
>>> Overview
>>>
>>>
>>> This patch series adds image streaming support for QED image files. Other
>>> image formats can also be sup
On Thu, Jun 16, 2011 at 11:38:48AM -0300, Marcelo Tosatti wrote:
> > People seem to agree on this, and the reason that I've heard why we
> > should merge the existing code instead is downstream time pressure. That
> > may be a valid reason for downstreams to add such code, but is taking
> > such co
On Thu, Jun 16, 2011 at 02:35:37PM +0200, Kevin Wolf wrote:
> Am 14.06.2011 20:18, schrieb Stefan Hajnoczi:
> > Overview
> >
> >
> > This patch series adds image streaming support for QED image files. Other
> > image formats can also be supported in the future.
> >
> > Image streaming p
On Thu, Jun 16, 2011 at 03:08:30PM +0200, Kevin Wolf wrote:
> Am 16.06.2011 14:49, schrieb Avi Kivity:
> > On 06/16/2011 03:35 PM, Kevin Wolf wrote:
> >> * Image streaming is a normal image file plus copy-on-read plus a
> >> background task that copies data from the source image
> >
> > Or a block
On Thu, Jun 16, 2011 at 11:52:43AM -0300, Marcelo Tosatti wrote:
This approach does not use the backing file feature?
> blkstream block driver:
>
> - Maintain in memory whether given block is allocated in local image,
> if not, read from remote, write to local. Set block as local.
> Local and rem
Am 16.06.2011 15:10, schrieb Anthony Liguori:
> On 06/16/2011 07:35 AM, Kevin Wolf wrote:
>> To summarise what both things are about:
>>
>> * Image streaming is a normal image file plus copy-on-read plus a
>> background task that copies data from the source image
>> * Live block copy is a block-mir
On 06/16/2011 04:08 PM, Kevin Wolf wrote:
Am 16.06.2011 14:49, schrieb Avi Kivity:
> On 06/16/2011 03:35 PM, Kevin Wolf wrote:
>> * Image streaming is a normal image file plus copy-on-read plus a
>> background task that copies data from the source image
>
> Or a block-mirror started in degrad
On 06/16/2011 03:35 PM, Kevin Wolf wrote:
* Image streaming is a normal image file plus copy-on-read plus a
background task that copies data from the source image
Or a block-mirror started in degraded mode.
* Live block copy is a block-mirror of two normal image files plus a
background task t
Am 16.06.2011 14:49, schrieb Avi Kivity:
> On 06/16/2011 03:35 PM, Kevin Wolf wrote:
>> * Image streaming is a normal image file plus copy-on-read plus a
>> background task that copies data from the source image
>
> Or a block-mirror started in degraded mode.
At least not in the same configuratio
Am 14.06.2011 20:18, schrieb Stefan Hajnoczi:
> Overview
>
>
> This patch series adds image streaming support for QED image files. Other
> image formats can also be supported in the future.
>
> Image streaming populates the file in the background while the guest is
> running. This make
On 06/16/2011 07:35 AM, Kevin Wolf wrote:
Am 14.06.2011 20:18, schrieb Stefan Hajnoczi:
Overview
This patch series adds image streaming support for QED image files. Other
image formats can also be supported in the future.
Image streaming populates the file in the background while the
27 matches
Mail list logo