From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Kuhles Subject: Re: Problems with KVM-79 Date: Sun, 07 Dec 2008 19:16:30 +0100 Message-ID: <493C12FE.1010306@aquatix.de> References: <493C09DB.7030802@aquatix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: QUOTED-PRINTABLE To: kvm@vger.kernel.org Return-path: Received: from eternity.serverbox.de ([91.200.108.23]:50356 "EHLO eternity.serverbox.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753502AbYLGSQg (ORCPT ); Sun, 7 Dec 2008 13:16:36 -0500 Received: from [192.168.2.150] (p579B0B8C.dip.t-dialin.net [87.155.11.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: web1p1) by eternity.serverbox.de (Postfix) with ESMTP id 1B85CB986BF for ; Sun, 7 Dec 2008 19:16:34 +0100 (CET) In-Reply-To: <493C09DB.7030802@aquatix.de> Sender: kvm-owner@vger.kernel.org List-ID: Hi, in addition to this, I just tried updating to the most recent developme= nt code (got it via git). The CentOS 5.2 VMs at least booted up fine, however, = the Windows 2008 Server immediately threw a bluescreen right after asking w= hether to boot regularly or in safe mode (just killed of the qemu process before)= =2E Switching back to KVM-79 again, everything ran "fine" again, except for= the problems explained below. So this is just to let you know that Win2008 = support seems broken in the current development tree. Cheers, Chris > Hi, >=20 > I was running KVM-76 with 2 CentOS 5.2 64bit VMs until a few days ago= =2E > Everything was working fine. However, I needed to install a third VM = running > Windows 2008 Server 64bit, which randomly kept crashing the host syst= em with a > kernel panic, so I thought, why not upgrade to KVM-79, wanted to do t= hat for a > while anyways. Now, Windows 2008 Server is running absolutely fine, n= o more host > crashes. However, the two CentOS VMs crash on me every once in a whil= e for no > good reason. This apparently seems to happen more often when one of t= he CentOS > VMs is under load, like compiling something. I had one of the VMs cra= sh on me > like 10 times to get a PHP 5.2.7 compile thru. I tried starting up th= e crashing > VM with -no-kvm, and the problem at least seemed to go away. I didn't= leave it > running like this too long as the VM is in production and with -no-kv= m, > everything ran terribly slow. >=20 > Here's some infos about the system I'm using: >=20 > Hardware: > - Intel Core2Quad Q6600 > - 8 GB RAM (checked with memtest86+ to make sure it's good) > - 2x 320 GB Seagate drives in a software RAID-1 >=20 > Software: > - Host system: CentOS 5.2 64bit > - VMs: 2x CentOS 5.2 64bit (same kernel as host, see below), 1x Windo= ws Server > 2008 64bit, all available updates installed > - manually compiled KVM-79 > - Host kernel version: 2.6.18-92.1.18.el5 >=20 > qemu commands: >=20 > VM1 (CentOS 5.2 64bit): > export DISPLAY=3D:1 > qemu-kvm -daemonize -localtime -no-acpi -hda /kvm/vm1.img -m 1024 -bo= ot c -net > nic,macaddr=3D52:54:00:00:01:00,model=3De1000 -net tap,ifname=3Dtap0,= script=3Dno >=20 > VM2 (Windows Server 2008 64bit): > export DISPLAY=3D:2 > qemu-kvm -daemonize -localtime -hda /kvm/vm2.img -m 2048 -boot c -net > nic,macaddr=3D52:54:00:00:01:01,model=3De1000 -net tap,ifname=3Dtap1,= script=3Dno >=20 > VM3 (CentOS 5.2 64bit): > export DISPLAY=3D:3 > qemu-kvm -daemonize -localtime -hda /kvm/vm3.img -m 1024 -boot c -net > nic,macaddr=3D52:54:00:00:01:02,model=3De1000 -net tap,ifname=3Dtap2,= script=3Dno >=20 > (qemu-kvm is a symlink to qemu-system-x86_64, inspired by the CentOS = packages > provided by lfarkas.org. Also tried those instead of compiling manual= ly, btw - > same problem.) >=20 > When the crashes happen, the qemu processes are still running on the = host, but > consume a lot of CPU. Checking the vnc console, there is no output wh= atsoever > from the VMs, just a blank, black screen that doesn't react to anythi= ng (even > tried SysRq, nothing). >=20 > Also, what I noticed is that CentOS 5.2 spits loads of errors about k= ernel > modules (don't have the exact message ready now, but I could get it l= ater on if > needed) when booting up as soon as -smp >=3D2 is used. This also did = not happen > with KVM-76. When I run with -smp 1 or leave that parameter out, ever= ything > works well - except for the random crashes. >=20 > As this did in no way happen with KVM-76, I figure there must me a bu= g in the > most recent version causing this issue. >=20 > I'd appreciate any help you could provide. If there's anything else I= can do, > like provide debugging output etc., please just let me know. >=20 --=20 Mit freundlichen Gruessen / Best regards Chris Kuhles Geschaeftsleitung / Managing Director Aquatix IT-Services e.K. Telefon: +49 69 24750456-0 M=FCnzgasse 6 Telefax: +49 69 24750456-1 60311 Frankfurt am Main E-Mail: ck@aquatix.de AG Frankfurt am Main, HRA 44038 Web: http://www.aquatix.de/