|
|
|
|
|
|
|
|
|
|
xen-devel
RE: [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
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- RE: [Xen-devel] [PATCH][RESEND]Nvram patch for IA64, Yu, Ke
- RE: [Xen-devel] [PATCH][RESEND]Nvram patch for IA64, Yu, Ke
- RE: [Xen-devel] [PATCH][RESEND]Nvram patch for IA64, Ian Pratt
- RE: [Xen-devel] [PATCH][RESEND]Nvram patch for IA64, Yu, Ke
- RE: [Xen-devel] [PATCH][RESEND]Nvram patch for IA64, Yu, Ke
- RE: [Xen-devel] [PATCH][RESEND]Nvram patch for IA64, Ian Pratt
- RE: [Xen-devel] [PATCH][RESEND]Nvram patch for IA64, Ian Pratt
- RE: [Xen-devel] [PATCH][RESEND]Nvram patch for IA64, Yu, Ke
- RE: [Xen-devel] [PATCH][RESEND]Nvram patch for IA64,
Ian Pratt <=
|
|
|
|
|