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

["Zhang, Xing Z" <xing.z.zhang@xxxxxxxxx>]

>
>   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.
[Zhang, Xing Z] 
Yes, image path makes things trouble. Thanks for your mention. The
collision only encountered when you use a same configure file to boot
different images(I am afraid people will do that in developing period).
EFI partition(/efi/xen/nvram)? I am not sure what you mean. Is it dom0's
partition?

>
>   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,

[Zhang, Xing Z] 
Could you attach me these logs?

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