When configured with 2 CPUs vmware guest VMI ROM detection is not reported in dmesg Reproducible: Always Steps to Reproduce: 1. Build gentoo-sources-2.6.26-r3 guest kernel with CONFIG_VMI=Y 2. Configure vmware-workstation 6.5 guest to 1 CPU 3. Boot vm 4. Execute: dmesg | grep -i VMI 5. Configure vmware-workstation 6.5 guest to 2 CPUs 6. Boot vm gentoo-sources-2.6.26-gentoo-r3 7. Execute: dmesg | grep -i VMI Actual Results: 'dmesg | grep -i VMI' for two CPUs vmi: registering clock event vmi-timer. mult=12582912 shift=22 vmi: registering clock event vmi-timer. mult=12582912 shift=22 Booting paravirtualized kernel on vmi vmi: registering clock source khz=3000000 Expected Results: 'dmesg | grep -i VMI' for two CPUs VMI: Found VMware, Inc. Hypervisor OPROM, API version 3.0, ROM version 1.0 vmi: registering clock event vmi-timer. mult=12582912 shift=22 vmi: registering clock event vmi-timer. mult=12582912 shift=22 Booting paravirtualized kernel on vmi 'dmesg | grep -i VMI' for one CPU displays correctly VMI: Found VMware, Inc. Hypervisor OPROM, API version 3.0, ROM version 1.0 vmi: registering clock event vmi-timer. mult=12582912 shift=22 Booting paravirtualized kernel on vmi vmi: registering clock source khz=3000000 My consern is the VMI may not be operational in multi CPU configurations.
At 2.6.24-gentoo-r8 'dmesg | grep -i VMI' works correctly with 2 CPUs # uname -r ; dmesg | grep -i VMI ; cat /proc/cpuinfo 2.6.24-gentoo-r8-1 VMI: Found VMware, Inc. Hypervisor OPROM, API version 3.0, ROM version 1.0 vmi: registering clock event vmi-timer. mult=12582912 shift=22 vmi: registering clock event vmi-timer. mult=12582912 shift=22 Booting paravirtualized kernel on vmi vmi: registering clock source khz=3000000 Time: vmi-timer clocksource has been installed. processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 67 model name : AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ stepping : 3 cpu MHz : 3000.000 cache size : 1024 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt rdtscp 3dnowext 3dnow pni extapic ts fid vid ttp tm stc bogomips : 6031.28 clflush size : 64 processor : 1 vendor_id : AuthenticAMD cpu family : 15 model : 67 model name : AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ stepping : 3 cpu MHz : 3000.000 cache size : 1024 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt rdtscp 3dnowext 3dnow pni extapic ts fid vid ttp tm stc bogomips : 6019.09 clflush size : 64 In Summary: Bad 2.6.26-gentoo-r3 'dmesg | grep -i VMI' displays: vmi: registering clock event vmi-timer. mult=12582912 shift=22 vmi: registering clock event vmi-timer. mult=12582912 shift=22 Booting paravirtualized kernel on vmi vmi: registering clock source khz=3000000 Good 2.6.24-gentoo-r8 'dmesg | grep -i VMI' displays: VMI: Found VMware, Inc. Hypervisor OPROM, API version 3.0, ROM version 1.0 vmi: registering clock event vmi-timer. mult=12582912 shift=22 vmi: registering clock event vmi-timer. mult=12582912 shift=22 Booting paravirtualized kernel on vmi vmi: registering clock source khz=3000000 Time: vmi-timer clocksource has been installed.
Norman, please! This is the 3rd VMI related bug over a short period of time. Obviously something went wrong regarding to VMI along kernel releases ... Would you mind to assist merging some bug of your's? Cheers Axel
(In reply to comment #2) > Norman, please! > > This is the 3rd VMI related bug over a short period of time. > Obviously something went wrong regarding to VMI along kernel releases ... > > Would you mind to assist merging some bug of your's? > > Cheers > Axel Hi Axel I've raised seperate bugs because I believe the causes are, probably, unrelated. I'm not sure what you mean by 'mergeing' but will be glad to assist if I can. Norman
(In reply to comment #3) > I've raised seperate bugs because I believe the causes are, probably, > unrelated. I'm not sure what you mean by 'mergeing' but will be glad to assist > if I can. If spoken do dsd (daniel drake). It's ok, like it is right now (3 separate bugs). Though it might be interesting (while you are bisecting next time :-)) to check for both bugs, i. e. this one and the other bug (VMI ROM not initialized). BTW, meanwhile we've got response from Zachary (vmware.com) on the 1st bug (INT 14 crash).
*** This bug has been marked as a duplicate of bug 250094 ***
Caused by CONFIG_LOG_BUF_SHIFT=15. Fixed by CONFIG_LOG_BUF_SHIFT=16
