RE: [Xen-devel] vmx status report against cset 14912 - 1 fixedissue, 4 old issues

["You, Yongkang" <yongkang.you@xxxxxxxxx>]

>> [Yunfeng] The guest was booted with a 2.16.16 smp kernel which we built
>> for PV test. It only happens on SMP HVM linux guest.I also saw the same
>> issue on some SLES SMP HVM guests with SLES release kernel and PV
>> drivers.
>
>It would be interesting to see what happens if the platform-pci interrupt is
>pinned strictly to vcpu0. So, what happens if you boot the guest with
>'acpi=0'? Or, what about if you kill any irqbalance programs that are
>running after boot, then 'cat /proc/interrupts' to find the xen-platform-pci
>interrupt number (x) and then 'echo 1 >/proc/irq/<x>/smp_affinity'?
>
>I couldn't repro just with SpecJBB but it's quite possible the kernel build
>is really required to repro. Specjbb itself does very little I/O.
>

Hi Keir, 

Which kernel and guest did you use? I meet issues in 2.6.16 kernel (I build a 
new kernel for the guest). Both UP and SMP has VBD problem in 64bit system. But 
IA32 kernel (2.6.16) is okay.

I tried your suggestion way in SMP system. I notice after doing kernel build 
for a while, the interrupts number won't increase any more, and the kernel 
build command is hung there. 

When I tried UP 64bit guest, the command hang when doing mount VBD disk.

Would it be the issue of guest kernel? I rebuild a 2.6.16 Linux kernel and used 
it in RHEL4U3. 

Best Regards,
Yongkang (Kangkang) 永康

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