RE: [Xen-ia64-devel] New tree issues (domU restart anddomVTibootissues)

[Alex Williamson <alex.williamson@xxxxxx>]

On Thu, 2007-06-14 at 12:30 +0800, Zhang, Xing Z wrote:
> 
> >-----Original Message-----
> >> [Zhang, Xing Z]
> >> It uses domain name. However, I think domain name also causes
> collision.
> >> So I intend to change it to image path. Any comment?
> >
> >   What do you mean by image path?  Can you give an example?
> >
> [Zhang, Xing Z] 
> For example, if your image path in configure file is "disk =
> ['file:/root/win2k3.img,had,w']". Then name of NVRAM file is
> "nvram_root_win2k3_img".

   What if you have multiple vbds exported to the domain?  Exporting a
CD is an obvious case where you'll have to parse the disk list to guess
a unique path.  What if you boot multiple guests from the same
read-only, live image (like a knoppix copied to disk)?  This seems more
troublesome than naming the nvram file using the domain name.  What
collisions do you foresee with domain names?  Seems like the ideal
scenario would be to save the nvram on the EFI partition
(/efi/xen/nvram).  Maybe the libfsimage functionality used by pygrub
would make this possible.

   BTW, why does my Madison processor system (that can obviously only
run PV domains) have so many error messages in xend.log and
xen-debug.log about not being able to get nvram data from the GFW?  Why
is manipulating nvram even being attempted on a PV guest?  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