i installed esxi, same error in ipmi after a while, talking to dell.. Marcelo Tosatti schrieb: > On Fri, Mar 06, 2009 at 06:02:00AM +0100, Johannes Baumann wrote: >> Marcelo Tosatti schrieb: >>> On Thu, Mar 05, 2009 at 11:31:35PM +0100, Johannes Baumann wrote: >>>> Ryan Harper schrieb: >>>>> * Johannes Baumann <johannes.baumann@xxxxxx> [2009-03-05 16:08]: >>>>>> Ryan Harper schrieb: >>>>>>> * Johannes Baumann <johannes.baumann@xxxxxx> [2009-03-05 15:52]: >>>>>>>> update: its not only happening with smp guest, but with non-smp guest. >>>>>>>> mcelog is empty. the commandline for a debian lenny im using is: >>>>>>>> >>>>>>>> /usr/src/kvm-84/qemu/x86_64-softmmu/qemu-system-x86_64 -S -M pc -m 512 >>>>>>>> -smp 1 -name vm03 -uuid 0b5e3a60-9111-0289-84b5-98cdf27450ac -monitor >>>>>>>> pty -boot c -drive >>>>>>>> file=/kvm/domains/linux-test/image.img,if=ide,index=0,boot=on -drive >>>>>>>> file=,if=ide,media=cdrom,index=2 -net >>>>>>>> nic,macaddr=54:52:00:0b:a1:26,vlan=0 -net >>>>>>>> tap,fd=12,script=,vlan=0,ifname=vnet0 -serial none -parallel none -usb >>>>>>>> -vnc 127.0.0.1:0 >>>>>>> you'll want -L /usr/src/kvm-84/qemu/pc-bios to ensure you use the bios >>>>>>> that came with kvm-84 instead of some other location. >>>>>> i could try but i dont think this is the point since every kvm version >>>>>> had the same problems so far. >>>>> if you don't use the right bios that comes with the kernel modules, >>>>> things _will_ break. >>>> k, trying the -L switch, with vt enabled >>>> >>>> root 6265 23.8 25.6 1100904 1039068 ? Sl 23:24 1:29 >>>> /usr/src/kvm-84/qemu/x86_64-softmmu/qemu-system-x86_64 -L >>>> /usr/src/kvm-84/qemu/pc-bios -S -M pc -m 1000 -smp 1 -name vm01 -uuid >>>> 3490fdf2-9550-4300-883a-a10fbf9b58e6 -monitor pty -localtime -boot c >>>> -drive >>>> file=/kvm/domains/windows2003-enterprise-jb/image.img,if=ide,index=0,boot=on >>>> -drive file=,if=ide,media=cdrom,index=2 -net >>>> nic,macaddr=00:16:d3:c2:36:ff,vlan=0,model=e1000 -net >>>> tap,fd=18,script=,vlan=0,ifname=vnet1 -serial none -parallel none -usb >>>> -usbdevice tablet -vnc 127.0.0.1:1 >> seems realy be guest bios related, since using the -L switch the host >> System didnt crash anymore. I got a lot of mcelogs: >> >> MCE 0 >> HARDWARE ERROR. This is *NOT* a software problem! >> Please contact your hardware vendor >> CPU 2 BANK 0 TSC 34186b6364dd >> MCG status: >> MCi status: >> Error overflow >> Uncorrected error >> Error enabled >> Processor context corrupt >> MCA:BUS Level-0 Originated-request Generic Memory-access Request-timeout >> Error >> Model: >> STATUS f200080010000800 MCGSTATUS 0 >> MCE 1 >> HARDWARE ERROR. This is *NOT* a software problem! >> Please contact your hardware vendor >> CPU 2 BANK 5 TSC 34186b6373bd >> MCG status: >> MCi status: >> Uncorrected error >> Error enabled >> Processor context corrupt >> MCA:BUS Generic Generic Generic Other-transaction Request-timeout Error >> Model: >> STATUS b200000806000e0f MCGSTATUS 0 >> MCE 2 >> HARDWARE ERROR. This is *NOT* a software problem! >> Please contact your hardware vendor >> CPU 0 BANK 5 TSC 34186b637434 >> MCG status:RIPV MCIP >> MCi status: >> Uncorrected error >> Error enabled >> Processor context corrupt >> MCA:BUS Generic Generic Generic Other-transaction Request-timeout Error >> Model:Pad state machine >> >> and so on.. >> >>> >>>> 2d | 02/19/2009 | 02:54:31 | Processor #0x0d | Transition to >>>> Non-recoverable >>>> 2e | 02/19/2009 | 02:54:32 | Processor #0x60 | IERR | Asserted >>> http://bugs.centos.org/print_bug_page.php?bug_id=2619 >>> >>> Likely to be a HW problem. >> I wasn able to reproduce without kvm running, still a hw problem? > > MCE usually indicate hardware problems. Take this to Dell support. > -- 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
