xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: David Markey <admin@dmarkey.com>
To: Dave Scott <Dave.Scott@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: XCP: RFC: compressing VM exports by default
Date: Tue, 22 Jun 2010 15:17:39 +0100	[thread overview]
Message-ID: <AANLkTimns2BGdEe0_SW1HHPVRRlaMO5IEjFi8oyni4im@mail.gmail.com> (raw)
In-Reply-To: <81A73678E76EA642801C8F2E4823AD218080C98A1E@LONPMAILBOX01.citrite.net>


[-- Attachment #1.1: Type: text/plain, Size: 1279 bytes --]

Hmm could increase Dom0 load during an export.

I think its a good idea overall however.

On 22 June 2010 15:08, Dave Scott <Dave.Scott@eu.citrix.com> wrote:

> Hi,
>
> In XCP a VM "export" is a serialized VM, including metadata and usually raw
> disk blocks. The format is a very simple tar file (really stream) with an
> XML file at the front containing version information and metadata.
>
> Unfortunately VM exports containing raw disk blocks can be very large and
> their size makes them difficult to store and distribute over the network. I
> propose to turn on compression by default by filtering the exports through
> gzip and to auto-detect both compressed and uncompressed exports on import.
>
> I've written up my proposal on the wiki:
>
> http://wiki.xensource.com/xenwiki/Compressing_VM_exports
>
> One implication is that new (compressed) exports will fail to import on
> older servers. However (a) there's an easy workaround (gunzip); and (b) I
> think being able to import an old (uncompressed) export on a new server is
> more important than the other way around.
>
> Comments appreciated!
>
> Cheers,
> Dave
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>

[-- Attachment #1.2: Type: text/html, Size: 1831 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  reply	other threads:[~2010-06-22 14:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-22 14:08 XCP: RFC: compressing VM exports by default Dave Scott
2010-06-22 14:17 ` David Markey [this message]
2010-07-14 14:20   ` Dave Scott

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=AANLkTimns2BGdEe0_SW1HHPVRRlaMO5IEjFi8oyni4im@mail.gmail.com \
    --to=admin@dmarkey.com \
    --cc=Dave.Scott@eu.citrix.com \
    --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).