All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: James Harper <james.harper@bendigoit.com.au>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Cc: Steven Smith <Steven.Smith@eu.citrix.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>
Subject: Re: How to determine memory size in HVM
Date: Tue, 09 Jun 2009 06:38:50 +0100	[thread overview]
Message-ID: <C653B3FA.D0B7%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D016DD675@trantor>

On 09/06/2009 02:59, "James Harper" <james.harper@bendigoit.com.au> wrote:

> Thanks for that.
> 
> Another question, if I do 'xm mem-set' (without any handling of the
> memory/target value) and then reboot, the system reboots with the new
> target memory value, making it impossible to add memory to the system
> again (under Windows at least). The only way I can think of fixing that
> is to write back to memory/target with the original value just before
> rebooting, but even that could be prone to errors in case of an unclean
> reboot or something... any way around this?

The new HVM populate-on-demand memory support should be able to help. I
suppose also some tools changes may be necessary in conjunction with this.
Or domain config changes. George Dunlap and Steven Smith can probably
advise.

 -- Keir

  reply	other threads:[~2009-06-09  5:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-08 14:12 How to determine memory size in HVM James Harper
2009-06-08 14:32 ` Keir Fraser
2009-06-09  1:59   ` James Harper
2009-06-09  5:38     ` Keir Fraser [this message]
2009-06-10 10:47       ` George Dunlap
2009-06-09  7:42   ` James Harper
2009-06-10  8:24     ` Keir Fraser
2009-06-10  9:39       ` James Harper
2009-06-10 13:07         ` Keir Fraser
2009-06-10 13:28           ` James Harper
2009-06-10 13:54             ` Keir Fraser

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=C653B3FA.D0B7%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Steven.Smith@eu.citrix.com \
    --cc=james.harper@bendigoit.com.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.