xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Christian Samsel <csamsel@gmxpro.de>
To: xen-devel@lists.xensource.com
Cc: Bastian de Groot <degroot@univention.de>
Subject: Re: large overhead with blktap2/vhd
Date: Thu, 24 Jun 2010 10:41:30 +0200	[thread overview]
Message-ID: <201006241041.30901.csamsel@gmxpro.de> (raw)
In-Reply-To: <201006231726.06620.degroot@univention.de>

Am Mittwoch, 23. Juni 2010, 17:26:05 schrieb Bastian de Groot:
> Hi everybody,
> 
> I am searching for a copy-on-write solution for Xen and tested blktap2 with
> the vhd backend.
> 
> My Test:
> 
> I've created a master-image with "dd" and installed WindowsXP on the image.
> Then I used vhd-util to create a copy-on-write-image for the master-image.
> 
> After booting the VM and logging in the, the cow-image had a size of 260
> MB. That's a little bit weird, because I didn't really changend any data.
Just one word: swap.

Christian

  reply	other threads:[~2010-06-24  8:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-23 15:26 large overhead with blktap2/vhd Bastian de Groot
2010-06-24  8:41 ` Christian Samsel [this message]
2010-06-24 11:15   ` Bastian de Groot

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=201006241041.30901.csamsel@gmxpro.de \
    --to=csamsel@gmxpro.de \
    --cc=degroot@univention.de \
    --cc=xen-devel@lists.xensource.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).