xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Don Slutz <dslutz@verizon.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen 4.4 development update: Code freezing point reached
Date: Mon, 18 Nov 2013 19:59:19 -0500	[thread overview]
Message-ID: <528AB7E7.6070904@terremark.com> (raw)
In-Reply-To: <CAFLBxZYH7_CicH2W7b17LbPiKLuScDmYVEf5CQV7ZpPrWCC4ow@mail.gmail.com>


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

On 11/18/13 13:19, George Dunlap wrote:
> This information will be mirrored on the Xen 4.4 Roadmap wiki page:
>   http://wiki.xen.org/wiki/Xen_Roadmap/4.4
[snip]

I realize that I did not send anything to you before this.  However:

http://lists.xen.org/archives/html/xen-devel/2013-10/msg01117.html
http://lists.xen.org/archives/html/xen-devel/2013-11/msg02352.html
http://lists.xen.org/archives/html/xen-devel/2013-11/msg02569.html

Is about a new minor feature.  Clearly I would like it in 4.4.  This is 
close to:

    xl dump-core <Domain> <filename>
    crash <filename>

But does not require the disk space, nor the delay while writing the 
file.  For me it took ~2 minutes to write out a 3G core file.
     -Don Slutz

> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel


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

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

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

  parent reply	other threads:[~2013-11-19  0:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-18 18:19 Xen 4.4 development update: Code freezing point reached George Dunlap
2013-11-18 18:52 ` Dario Faggioli
2013-11-18 19:22 ` Pasi Kärkkäinen
2013-11-19 16:18   ` George Dunlap
2013-11-19  0:59 ` Don Slutz [this message]
2013-11-19 17:46   ` George Dunlap
2013-11-19 10:50 ` Roger Pau Monné
2013-11-19 11:06   ` George Dunlap
2013-11-19 11:31     ` Roger Pau Monné
2013-11-19 14:00 ` Ian Campbell
2013-11-19 14:40 ` Konrad Rzeszutek Wilk
2013-11-19 14:54   ` Jan Beulich
2013-11-19 15:11     ` Konrad Rzeszutek Wilk
2013-11-19 17:52   ` George Dunlap
2013-11-19 19:40     ` Konrad Rzeszutek Wilk
2013-11-20  3:17   ` Zhenzhong Duan

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=528AB7E7.6070904@terremark.com \
    --to=dslutz@verizon.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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).