From: George Dunlap <george.dunlap@eu.citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Roger Pau Monne <roger.pau@citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen 4.3 development update RC2 imminent
Date: Mon, 20 May 2013 12:32:23 +0100 [thread overview]
Message-ID: <519A09C7.8010502@eu.citrix.com> (raw)
In-Reply-To: <1369048572.10868.15.camel@zakaz.uk.xensource.com>
On 20/05/13 12:16, Ian Campbell wrote:
> On Mon, 2013-05-20 at 12:09 +0100, George Dunlap wrote:
>> I think long-term we probably want to sort out the "right" way to do
>> this -- ideally I think we'd like there to be a "config on next reboot"
>> that one could manipulate while the VM is running -- manually changing
>> such things as the number of vcpus or amount of memory, automatically
>> updating things like the cdrom and the mac address.
> We already have the manual version via "xl config-update", but that's
> really just a workaround for the cdrom/mac address issues.
Then is the problem:
1. The randomly generated mac is not being stored automatically in the
config?
2. The mac is being clobbered when re-loading the config file on reboot?
If it's #1, it seems like it should be relatively straightforward to
sort out.
-George
next prev parent reply other threads:[~2013-05-20 11:32 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 10:33 Xen 4.3 development update RC2 imminent George Dunlap
2013-05-20 10:36 ` George Dunlap
2013-05-20 17:12 ` Keir Fraser
2013-05-21 8:13 ` Tim Deegan
2013-05-21 10:22 ` Jan Beulich
2013-05-21 8:19 ` Jan Beulich
2013-05-21 8:22 ` George Dunlap
2013-05-21 8:25 ` Jan Beulich
2013-05-20 10:51 ` Wei Liu
2013-05-20 11:09 ` George Dunlap
2013-05-20 11:16 ` Ian Campbell
2013-05-20 11:32 ` George Dunlap [this message]
2013-05-20 11:46 ` Ian Campbell
2013-05-20 13:42 ` George Dunlap
2013-05-20 11:15 ` Ian Campbell
2013-05-20 11:22 ` George Dunlap
2013-05-20 11:26 ` Ian Campbell
2013-05-20 11:28 ` George Dunlap
2013-05-20 11:48 ` Ian Campbell
2013-05-21 14:06 ` Anthony PERARD
2013-05-21 14:31 ` Andrew Cooper
2013-05-21 14:49 ` George Dunlap
2013-05-21 14:55 ` Jan Beulich
2013-05-21 14:58 ` Andrew Cooper
2013-05-21 15:07 ` Jan Beulich
2013-05-21 16:13 ` George Dunlap
2013-05-21 16:16 ` George Dunlap
2013-05-22 12:49 ` Fabio Fantoni
2013-05-22 12:58 ` Andrew Cooper
2013-05-22 15:05 ` George Dunlap
2013-05-22 16:30 ` Pasi Kärkkäinen
2013-05-22 16:54 ` George Dunlap
2013-05-23 7:39 ` Jan Beulich
2013-05-23 10:36 ` Fabio Fantoni
2013-05-23 10:39 ` Andrew Cooper
2013-05-23 10:54 ` George Dunlap
2013-05-23 14:17 ` Fabio Fantoni
2013-05-23 14:26 ` George Dunlap
2013-05-23 14:35 ` George Dunlap
2013-05-23 14:58 ` Fabio Fantoni
2013-05-23 15:10 ` Pasi Kärkkäinen
2013-05-23 16:10 ` George Dunlap
2013-05-23 16:07 ` George Dunlap
2013-05-24 13:56 ` Fabio Fantoni
2013-05-24 13:59 ` George Dunlap
2013-05-24 14:53 ` Fabio Fantoni
2013-05-24 15:52 ` George Dunlap
2013-05-23 14:32 ` George Dunlap
2013-05-23 10:48 ` Jan Beulich
2013-05-23 10:31 ` Fabio Fantoni
2013-05-23 14:01 ` Pasi Kärkkäinen
2013-05-22 12:48 ` Fabio Fantoni
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=519A09C7.8010502@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=roger.pau@citrix.com \
--cc=wei.liu2@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).