Description of problem: I have a 8 processor opteron system running fedora 12 as a KVM host. Sometimes, when I boot a KVM machine the /proc/cpuinfo in the KVM shows up saying 0.000 MHz (it apparently picks them at random, though I think I've only seen it on KVMs running a 32 bit kernel) Version-Release number of selected component (if applicable): qemu-kvm-0.11.0-12.fc12.x86_64 kernel-2.6.31.6-166.fc12.x86_64 How reproducible: It happens every so often, but is random. Steps to Reproduce: 1.boot KVM 2.look at /proc/cpuinfo 3. Actual results: zero MHz Expected results: sane MHz No special messages show up in the qemu log. Here's the entry from the above boot: LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/bin/qemu-kvm -S -M pc-0.11 -m 1024 -smp 1 -name ubuntu8d10i -uuid daafb9fa-5c6c-4bc0-92fd-efe78dc397af -monitor unix:/var/lib/libvirt/qemu/ubuntu8d10i.monitor,server,nowait -boot c -drive file=/guest4/ubuntu8d10i.img,if=ide,index=0,boot=on,format=raw -drive file=,if=ide,media=cdrom,index=2 -net nic,macaddr=00:16:3e:54:44:f5,vlan=0,name=nic.0 -net tap,fd=24,vlan=0,name=tap.0 -serial pty -parallel none -usb -vnc 127.0.0.1:6 -vga cirrus char device redirected to /dev/pts/6 Additional info: Here's a log file from one I caught in the act: 2009-12-19 20:44:13 starting: ./scripts/new-test 20091220014412 2009-12-19 20:44:13 Exited with status 0 2009-12-19 20:44:13 starting: ./scripts/xen/bootup-kvm ubuntu8d10i Domain ubuntu8d10i started processor : 0 vendor_id : AuthenticAMD cpu family : 6 model : 2 model name : QEMU Virtual CPU version 0.11.0 stepping : 3 cpu MHz : 0.000 cache size : 512 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 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 pni bogomips : 2326.52 clflush size : 64 power management: ubuntu8d10i.ccur.kvm does not have sane cpu MHz in /proc/cpuinfo cpu MHz : 0.000 KVM is not sane 2009-12-19 20:45:27 Exited with status 2 2009-12-19 20:45:27 starting: ./scripts/xen/shutdown-kvm ubuntu8d10i Sending shutdown -h now command to ubuntu8d10i... Here's the smolt profile of the KVM host machine: http://www.smolts.org/client/show/pub_fde3037c-3bfd-4a28-9f73-601d559b6567
Just a new data point: I've now seen it happen on a 64 bit guest as well, so the 32 bit comment above was based on a sample size that was too small :-).
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
The exact same results happen randomly with the KVM host now upgraded to fedora 13, so the bug (if it is a bug and not simply some weird side effect with other kernels running under KVM) still exists.
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.