From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935604AbXFGTQT (ORCPT ); Thu, 7 Jun 2007 15:16:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1762358AbXFGTQL (ORCPT ); Thu, 7 Jun 2007 15:16:11 -0400 Received: from nz-out-0506.google.com ([64.233.162.230]:44088 "EHLO nz-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1762152AbXFGTQK (ORCPT ); Thu, 7 Jun 2007 15:16:10 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=VXSjk8BMUf071SnnGlgkSvoRWSJX3FN7nELVs7+xXKNi15GPVMaEBMt2ozjXcwMCC9b2m6r+5CVUrHW4PnwmdY1Yv2Oe0fxC+PwfvP9GkzpOWVLEf+mt5V5LpkOqN776vNo+PlBNHiE6F60jHT/AXV4qQaoABBPGYSciSKiFRlI= Message-ID: <68676e00706071216i4bd051c5hb1c114f3c13ab97f@mail.gmail.com> Date: Thu, 7 Jun 2007 21:16:08 +0200 From: Luca To: "Avi Kivity" Subject: Re: [kvm-devel] [BUG] Oops with KVM-27 Cc: kvm-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org In-Reply-To: <46651069.5040003@qumranet.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070603213432.GA3075@dreamland.darkstar.lan> <4663DCE9.3000107@qumranet.com> <20070604202248.GA18668@dreamland.darkstar.lan> <46647B3E.2090205@qumranet.com> <20070604212207.GA22365@dreamland.darkstar.lan> <46651069.5040003@qumranet.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On 6/5/07, Avi Kivity wrote: > Luca Tettamanti wrote: > > Il Mon, Jun 04, 2007 at 11:51:10PM +0300, Avi Kivity ha scritto: > > > >>> While doing repeated tests with the installer I ran into another > >>> (unrelated) problem. Sometimes the guest kernel hangs at boot at: > >>> > >>> NET: Registered protocol family 2 > >>> > >>> with any kind of networking options (except for -net none, which works). > >>> With -no-kvm it boots with any networking option. > >>> > >>> > >>> > >> Can you try to pin the guest on a single core with taskset: > >> > >> taskset 1 qemu ... > >> > > > > Doesn't help. What works is 'nolapic', i.e. disabling the local APIC on > > the guest kernel. > > I've also tried disabling TSC (notsc) and forcing PIT as the clocksource > > (clocksouce=pit clock=pit); neither of them helped. > > > > > > Is this a regression relative to a previous kvm version? Hello, sorry for the delay, I was having troubles compiling older KVMs with a recent kernel... The last version that works is kvm-21; starting from kvm-22 the VM hangs during network initialization (now always, but pretty often). This only occurs when the guest is Fedora7 setup ISO. The regular boot (i.e. from the hd) seems unaffected. Luca