WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] [PATCH][RESEND]Nvram patch for IA64

To: "Yu, Ke" <ke.yu@xxxxxxxxx>, "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, "Christian Limpach" <christian.limpach@xxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH][RESEND]Nvram patch for IA64
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Tue, 31 Oct 2006 15:32:41 -0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, "Huang, Xinmei" <xinmei.huang@xxxxxxxxx>
Delivery-date: Thu, 02 Nov 2006 13:58:42 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <117E3EB5059E4E48ADFF2822933287A4F92D81@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acbwn3GTeQX7YqjuSrWHsAKaEOOOQwANzaogAF+2ZZACaGUm0AAEkMSwAAbrrDAAAklb1wAAHUJQABe5ZSAAFQfgUAAC850gAANOseAAAH1PUAABJGTg
Thread-topic: [Xen-devel] [PATCH][RESEND]Nvram patch for IA64
> > But do all installs of the same OS have the same variable contents?
> > That was the question.
> 
> Oh, I misunderstand your question. Yes. The same OS installation have
same
> variable contents.

In which case, wouldn't it just be a whole lot simpler to have qemu-dm
know about these constants and just have a configuration parameter to
cause it to serve up the right one when asked? 

We probably should have a 'guest_type' field in the guest config anyway
as we'll likely want to use this for enabling/tuning various
optimizations.

I know this isn't ideal from a purist virtualization point of view, but
it seems like a practical solution.
 
> OK. then the xensotor content will looks like this:
> nvram = " "                                          # nvram dir
>    vti-domain1 = " "                               # domain name
>        0 = "xxxxxxxxxxxxxxxxxxxxxxxxxxxxx"  # 128 characters, data
offset =
> 0*64
>        1 = "xxxxxxxxxxxxxxxxxxxxxxxxxxxxx"  # 128 characters, data
offset =
> 1*64
>        .........                                          # skip data
block
> of all 0xff
>    vti-domain2 = " "
>        ..........

We'll have to think about how this data gets persisted (I'd trigger a
watcher and store it outside of xenstore). Look at the xen-api.hg tree
to see how stuff gets persisted.

Ian



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