|
|
|
|
|
|
|
|
|
|
xen-devel
RE: [Xen-devel] VMX status report 11394:96a4379be74a
> We have tested the latest xen on VT platform with Intel 915/E8500
> chipset.
>
> Three platforms(32/pae/32e) test all are based on SMP, It means that
we
> boot up SMP guest OS in VMX.
>
> Here is the test summary:
>
> Issues:
> - Creating 4 VMX simutaneously on 32 platform will hang xen0
Does it reboot or just hang? Is dom0 pingable? Is the text console
alive?
Xen0 just hangs, not reboot. And dom0 is unpingable.
Although the cursor is blinking in text console, but it is
uncontrollable.
If you're in a text mode console, do you get an oops message printed?
Exactly what kind of guests are you starting simultaneously, and on what
hypervisor (e.g. PAE?).
we start ia32 non-pae smp guest OS on ia32 hypervisor.
You say that you're using an SMP kernel, and since in most distros the
SMP kernel also implies guest PAE support, I assume you're using pae=1
guests?
We build ia32 non-pae smp kernel by ourselves, so we use pae=0
smp guests.
> - Sometimes build base kernel 2.6.16 in IA32SMP guest fails on 32bit
> platform.
In what way does it fail? Does the guest VM crash? Does the make
segfault?
Guest didn't crash. See attachment "kb_ia32_smp_failed_1.JPG,
kb_ia32_smp_failed.JGP" for some error messages from building kernel. In
fact, we get various error messages. Build kernel in IA32PAE SMP VMX
domain and IA32E SMP VMX domain are ok.
http://losvmm-bridge.sh.intel.com/bugzilla/show_bug.cgi?id=788
Thanks,
Ian
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
four_VMX
Description: four_VMX
four_VMX.JPG
Description: four_VMX.JPG
kb_ia32_smp_failed_1.JPG
Description: kb_ia32_smp_failed_1.JPG
kb_ia32_smp_failed.JPG
Description: kb_ia32_smp_failed.JPG
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] VMX status report 11394:96a4379be74a, Zheng, Jeff
- RE: [Xen-devel] VMX status report 11394:96a4379be74a,
Ye, Yuanqing <=
- RE: [Xen-devel] VMX status report 11394:96a4379be74a, Ian Pratt
- RE: [Xen-devel] VMX status report 11394:96a4379be74a, You, Yongkang
- RE: [Xen-devel] VMX status report 11394:96a4379be74a, You, Yongkang
- RE: [Xen-devel] VMX status report 11394:96a4379be74a, Yu, Ping Y
- RE: [Xen-devel] VMX status report 11394:96a4379be74a, Yu, Ping Y
|
|
|
|
|