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

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

>- domU restart.
>  DomU can't be restarted again. This is because nvram patch.
>  It is already fixed in upstream tree by c/s 15265:634b7f7f8584.
>
[Zhang, Xing Z] 
        I will look into this.
>- domVTi guest firmware can't load elilo.
>  domVTi boots and then efi shell shows up. But it can't load anything.
>  'dblk blk0' shows all zero.
>  I haven't dug into it yet. Is this my local issue or does anyone hit
this?
>
[Zhang, Xing Z] 
        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.

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