> 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
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!
>
>
> Xen/IA64 Unstable Cset #17602 Status Report
>
> ============================================================
> Test Result Summary:
> # total case: 18
> # passed case: 17
> # failed case: 1
> ============================================================
> Testing Environment:
> platform: Tiger4
> processor: Itanium 2 Processor
> logic Processors number: 8 (2 processors with Dual Core)
> pal version: 9.08
> service os: RHEL4u3 IA64 SMP with 2 VCPUs
> vti guest os: RHEL4u2 & RHEL4u3
> xenU guest os: RHEL4u2
> xen ia64 unstable tree: 17602
> xen schedule: credit
> gfw: open guest firmware Cset#122
> ============================================================
> Detailed Test Results:
>
> Passed case id Description
> VTI_PV Linux VTI PV
> Two_UP_VTI_Co2 UP_VTI (mem=256)
> One_UP_VTI 1 UP_VTI (mem=256)
> One_UP_XenU 1 UP_xenU(mem=256)
> SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP
> SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2)
> Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2)
> One_SMPVTI_4096M 1 VTI (vcpus=2, mem=4096M)
> SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping'
> SMPXenU_Network 1 XenU (vcpus=2) and 'ping'
> One_SMP_XenU 1 SMP xenU (vcpus=2)
> One_SMP_VTI 1 SMP VTI (vcpus=2)
> SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild
> UPVTI_Kernel_Build 1 UP VTI and do kernel
> build
> SMPVTI_Windows SMPVTI windows(vcpu=2)
> SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows & XenU
> VTI_Windows_PV Windows VTI PV
> ------------------------------------------------------------------------
> Failed case id Description
> Save&Restore Save&Restore
>
> ============================================================
>
>
> Thanks,
> Zhang Jingke
>
>
> _______________________________________________
> Xen-ia64-devel mailing list
> Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-ia64-devel
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|