https://lists.gnu.org/archive/html/qemu-devel/2012-10/msg02269.html On Wed, Feb 20, 2013 at 01:25:04AM +0400, Dmitry Krivenok wrote: > Hello, > > I encountered an odd issue with running VMWare .vmdk image inside KVM. > > I run KVM as follows > qemu-kvm -hda ./guest.vmdk -m 4096 > > and guest OS (SLES11) boots fine, but reports zero CPU freq via > /proc/cpuinfo (cpu MHz): > > > > $ cat /proc/cpuinfo > > processor : 0 > > vendor_id : GenuineIntel > > cpu family : 6 > > model : 2 > > model name : QEMU Virtual CPU version 0.15.1 > > stepping : 3 > > cpu MHz : 0.000 > > cache size : 4096 KB > > fpu : yes > > fpu_exception : yes > > cpuid level : 4 > > wp : yes > > flags : fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca > cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx lm up rep_good > nopl pni cx16 popcnt lahf_lm > > bogomips : 2088.96 > > clflush size : 64 > > cache_alignment : 64 > > address sizes : 40 bits physical, 48 bits virtual > > power management: > > $ > > > > I tried to convert .vmdk to qcow2 image and also tried different > –cpu=<MODEL> options, but I always get zero frequency in this guest. > > Another guest (Ubuntu in native qcow2 image) works fine and reports > correct cpu frequency, so I only see this problem with this particular > .vmdk image. > > > > I’m running > > QEMU emulator version 0.15.1 (kvm-0.15.1-0.17.3), Copyright (c) > 2003-2008 Fabrice Bellard > > on SLES11-SP2 host (3.0 kernel + patches). > > This problem is critical for me because by guest runs a binary which > relies on non-zero CPU freq in /proc/cpuinfo. > > > Any ideas? > > Thanks! > > -- > Sincerely yours, Dmitry V. Krivenok > e-mail: krivenok.dmitry@xxxxxxxxx > skype: krivenok_dmitry > jabber: krivenok_dmitry@xxxxxxxxx > icq: 242-526-443 > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
