RE: [Xen-ia64-devel] IA64 using Redhat 5.1: xm createfails:Hotplugscripts not working.

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

Forget post the reason. Complement below:
Nvram saving is always executed even if a domain is destroyed by a
configuration parameter error.  In this case, Nvram saving function
will get a bad address for the NVRAM data and save garbage into the
NVRAM file. Configuring a wrong vif parameter can expose this issue.

Good good study,day day up ! ^_^
-Wing(zhang xin)

OTC,Intel Corporation

>-----Original Message-----
>From: Zhang, Xing Z
>Sent: 2007?11?14? 14:14
>To: 'Tristan Gingold'; You, Yongkang
>Cc: xen-ia64-devel
>Subject: RE: [Xen-ia64-devel] IA64 using Redhat 5.1: xm
>createfails:Hotplugscripts not working.
>
>>Subject: Re: [Xen-ia64-devel] IA64 using Redhat 5.1: xm
>>createfails:Hotplugscripts not working.
>>
>>On Wed, Nov 14, 2007 at 01:59:29PM +0800, You, Yongkang wrote:
>>> Also found following line in Kayvna's original email:
>>> >> ==> xend-debug.log <==
>>> >> ERROR Internal error: Invalid nvram signature. Nvram save
>>failed!
>>> >>  (11 = Resource temporarily unavailabl)
>>>
>>> Does the guest firmware is the correct one, which is installed
>>from
>>> Supplymentary CD?
>>
>>Isn't this message expected at the first creation ?
>>
>
>No, this is a mechanism which keeps from garbage NVRAM data.
>See this thread:
>http://xenbits.xensource.com/ext/ia64/xen-unstable.hg?diff/
>38d061886873/tools/libxc/ia64/xc_ia64_hvm_build.c

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