RE: [Xen-ia64-devel] New tree issues (domU restart and domVTi bootissues)

[Alex Williamson <alex.williamson@xxxxxx>]

On Thu, 2007-06-14 at 10:42 +0800, Zhang, Xing Z wrote:
>       Current NVRAM design uses "name" field of configure file as
> NVRAM file name.
> For example, if your guest named "HVM", then you can find the
> corresponding NVRAM file at /usr/lib/xen/boot/nvram_HVM. So if you have
> two guests with same name, the one booted afterward would read NVRAM
> data of previous one. This may cause some un-expected things such as
> can't find disk. A workaround method is makes all guests have different
> name and rm all existing NVRAM files and boot them again. I will send a
> patch to use image patch as NVRAM file name later on, which reduces
> collision. Sorry for inconvenient.

  The nvram store is based on the config file name or the domain name?
Xen 2.0 used to make it really easy to launch multiple domains using the
same config file w/ a %vid (iirc) variable in the config file.  Is this
still possible in Xen 3.x?  It would seem logical that the nvram store
should be based on the domain name, since that already has a requirement
to be unique.  Thanks,

        Alex

-- 
Alex Williamson                             HP Open Source & Linux Org.


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