RE: [Xen-devel] Some issues in recent ChangeSet.

["Zheng, Jeff" <jeff.zheng@xxxxxxxxx>]

OK. Following two issues are invalid/trivial:
+ 32 SMP Guest only see about 900M memory when assign 1.5G memory
This is because 32bit guest was built without enable HIGH_MEM.
+ Bootup 64bit guest with pae=0 in configure file, guest will
   complain "Your CPU does not support long mode"
64bit guest assumes pae=1

And following issues still exist:
+ (up/SMP) pae guest cannot bootup on 32pae/64bit platform. Vista guest 
   cannot bootup either.
+ Boot 32 guest will hang 32pae xen0 with balloon driver: If I do not set
   a fixed size memory using "dom0_mem=" option in grub.conf for dom0,
   dom0 will hang after a vmx guest is created.
+ 64bit guest shows cpu-specific performance downgrad
+ FC5 IA32 VMX Guest crash when try to boot SMP Guest: set vcpus=2
   acpi=1 apic=1 pae=1 in configure file and create SMP FC5 IA32 VMX
   guest, guest wil crash
+ 32pae SMP guest with 1500MB memory will cause 64bit xen0 reboot
+ Creating PAE SMP base kernel in VMX causes 32pae xen0 reboot(xen0_crash.1)
+ VNIF does not work

Bests
Jeff 

>-----Original Message-----
>From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
>[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Zheng, Jeff
>Sent: 2006年8月25日 23:15
>To: Keir Fraser; Steven Hand
>Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
>Subject: RE: [Xen-devel] Some issues in recent ChangeSet.
>
>Yes. LTP math issue & "kerne panic - not sync" issue resolved.
>
>Resolved issues contain:
>32bit HV/xen0:
>2. 4 LTP math cases(float_bessel, float_exp_log, float_power and
>   float_trigo) sometime fail. (775)
>3. Kernel build in VMX may meet kernel panic. It complains like: "<0>
>   Kernel panic - not syncing: kernel/sched.c:460:
>   spin_lock(kernel/sched.c:c03ea120) already locked by
>   kernel/sched.c/2689"
>IA32E HV/xen0
>8. 64bit SMP VMX can not be up, if acpi=0 : If try with acpi=0 apic=1
>   vcpus=2 pae=1 to create FC3 IA32e guest, Guest will kernel 
>panic when
>   booting.
>
>
>But following issues still exist:
>1. Reboot fail in Guest OS: Reboot in guest will close current qemu
>   windows but does not create a new qemu window to restart
>
>32bit PAE HV/xen0:
>4. Cannot bootup pae SMP VMX domain.  guest crashed with attached
>   output.
>5. Create 32 guest with balloon driver will hang xen0: If I do not set
>   a fixed size memory using "dom0_mem=" option in grub.conf for dom0,
>   dom0 will hang after a vmx guest is created.
>6. 32 SMP Guest only see about 900M memory when assign 1.5G memory for
>   the guest: If I assign 1.5G memory in vmx config file and 
>boot up the
>   guest, I still can only see 903256KB memory using "cat 
>/proc/meminfo"
>   in the guest, though I can see 1.5G memory allocated to the guest.
>
>IA32E HV/xen0
>7. 64bit guest shows io-specific performance improvement but 
>cpu-specific
>    performance downgrad 
>9. FC5 IA32 VMX Guest crash when try to boot SMP Guest: set vcpus=2
>   acpi=1 apic=1 pae=1 in configure file and create SMP FC5 IA32 VMX
>   guest, guest wil crash with attached output.
>10. 32pae SMP guest with 1500MB memory will cause xen0 reboot
>11. Bootup 64bit guest with pae=0 in configure file, guest will
>   complain "Your CPU does not support long mode"
>
>
>Bests
>Jeff 
>
>>-----Original Message-----
>>From: Keir Fraser [mailto:Keir.Fraser@xxxxxxxxxxxx] 
>>Sent: 2006年8月24日 16:53
>>To: Keir Fraser; Zheng, Jeff; Steven Hand
>>Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
>>Subject: Re: [Xen-devel] Some issues in recent ChangeSet.
>>
>>
>>
>>
>>On 24/8/06 8:20 am, "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx> wrote:
>>
>>>> No. The issue still exists. We also found that "kernel 
>>panic - not sync:
>>>> kernel/sched.c" issue in kernel build at CS11246.
>>> 
>>> Ok, I see why the 'better' patch 11243 doesn't in fact work. 
>>It's good to
>>> hear that 11242 worked okay for you though. We'll sort out a 
>>real, final,
>>> proper fix today!
>>
>>Hopefully 11249:1ff4cc298bec is a final solution to this issue.
>>
>> -- Keir
>>
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-devel
>

Attachment: xen0_crash.1
Description: xen0_crash.1

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