Kouya Shimura wrote:
>> Is this related to Cset#17600: "[IA64] fix restoring HVM domain
>> with PV driver"? Thank you very much!
>
> No, probably due to the cset 17531:18727843db60.
>
> changeset: 17531:18727843db60
> user: Keir Fraser <keir.fraser@xxxxxxxxxx>
> date: Fri Apr 25 13:44:45 2008 +0100
> summary: x86, hvm: Guest CPUID configuration.
>
> There is no xc_cpuid_apply_policy() function for ia64 yet.
>
> From xend.log:
> [2008-05-14 17:27:04 4600] ERROR (XendDomain:1144) Restore failed
> Traceback (most recent call last):
> File "//usr/lib/python/xen/xend/XendDomain.py", line 1136, in
> domain_restore_\ fd
> return XendCheckpoint.restore(self, fd, paused=paused,
> relocating=relocatin\ g)
> File "//usr/lib/python/xen/xend/XendCheckpoint.py", line 312, in
> restore restore_image.setCpuid()
> File "//usr/lib/python/xen/xend/image.py", line 557, in setCpuid
> xc.domain_set_policy_cpuid(self.vm.getDomid())
> AttributeError: domain_set_policy_cpuid
>
> Thanks,
> Kouya
>
Yes, my xend.log reported the same with you. Thank you very much!
> Zhang, Jingke writes:
>> Hi all,
>> This is today's Xen/IPF nightly test report against Cset#17602.
>> One new issue was found in "VTI restore". That is to say VTI guest
>> can be saved successfully, but it will fail to be restored. By
>> /var/log/xen/xend-debug.log, we can see:
>> ==========================
>> Enabling Linux guest OS optimizations
>> Nvram save successful!
>> ERROR Internal error: Nvram not initialized. Nvram save failed!
>> (2 = No such file or directory)
>> ==========================
>> Is this related to Cset#17600: "[IA64] fix restoring HVM domain
>> with PV driver"? Thank you very much!
>>
Thanks,
Zhang Jingke
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
Home