From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: where should I report kvm kernel bug? Date: Tue, 03 Jan 2012 19:08:10 +0200 Message-ID: <4F0335FA.4080600@redhat.com> References: <1B4B44D9196EFF41AE41FDA404FC0A10F980@SHSMSX101.ccr.corp.intel.com> <4F02D405.3030809@redhat.com> <1325608111.31426.2.camel@i5.mricon.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: "Ren, Yongjie" , "kvm@vger.kernel.org" , ftpadmin To: Konstantin Ryabitsev Return-path: Received: from mx1.redhat.com ([209.132.183.28]:36249 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754154Ab2ACRIP (ORCPT ); Tue, 3 Jan 2012 12:08:15 -0500 In-Reply-To: <1325608111.31426.2.camel@i5.mricon.com> Sender: kvm-owner@vger.kernel.org List-ID: On 01/03/2012 06:28 PM, Konstantin Ryabitsev wrote: > On Tue, 2012-01-03 at 12:10 +0200, Avi Kivity wrote: > > I'm surprised bugzilla.kernel.org isn't responding. Copying > > ftpadmin@kernel.org for ETA (though that address isn't responding, either). > > Hi, Avi and Ren: > > Unfortunately, we don't currently have an ETA for bringing up > bugzilla.kernel.org. We are still awaiting some hardware deliveries > before we can recover that service. The KVM developers suggest a virtual machine in the meantime? > I suggest you ask KVM developers > where they would prefer to have the bug reported. Ren, please use the qemu bug tracker temporarily, just make sure to mark it as a kernel bug. > Sorry for lack of responses -- the holidays always make it more > difficult to respond in time. > Thanks. -- error compiling committee.c: too many arguments to function