From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Nilsson Subject: 2003 x64 hangs on reboot on Intel E6750 CPU (Diffrent kernels, diffrent kvms) Date: Wed, 10 Dec 2008 14:53:27 +0100 Message-ID: <493FC9D7.9050407@Gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit To: kvm@vger.kernel.org Return-path: Received: from s05.axentus.se ([212.247.113.5]:1326 "EHLO s05.axentus.se" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752970AbYLJOJO (ORCPT ); Wed, 10 Dec 2008 09:09:14 -0500 Sender: kvm-owner@vger.kernel.org List-ID: Hi, I have a problem with Windows Server 2003 x64 (Standard edition) installations in a kvm instance, different versions of kvm (first try was with kvm-76 and the problem have persisted) the kernel has also changed together with kvm, when the guest is about to reboot it just hangs (server 2003 gray background no mouse response) and the kvm process uses ~100-101% cpu or it reboots and then hangs in the bios. The same kind of configuration works perfectly on other boxes, however after installing my second server with a E6750 i think i have found the cpu to be the common link? 2 boxes with Working reboot: Intel Q9450 Cpu 2 boxes with Non Working reboot: Intel E6750 Cpu i have tested to do a clean reinstall a couple of times before with no change. kvm is started with virsh but i know i have played around with different options and there where no big differences, I will test more to narrow it down if any dev wants me to (tell me the options to test with and without) the real kvm command that is executed are: /usr/bin/kvm -S -M pc -m 1024 -smp 2 -name ts2k3x64 -monitor pty -localtime -boot c -drive file=/home/kvm/kvm_ts2k3x64.qcow2,if=ide,index=0,boot=on -drive file=,if=ide,media=cdrom,index=2 -net nic,macaddr=00:16:3e:01:e7:b3,vlan=0 -net tap,fd=13,script=,vlan=0,ifname=vnet1 -serial pty -parallel none -usb -usbdevice tablet -vnc -k sv the command is almost the same for other guests on same and other host: different amount memory -smp 4 on quads -name -file and -net options differs. another host uses e1000 network, but thats about it. Anyone that has a solution, is it a bug in kvm or is it a bug in the CPUs? if there is anything that i can provide to help find the reason or solution, please let me know. Regards Christian Nilsson