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 12:10:13 +0200 Message-ID: <4F02D405.3030809@redhat.com> References: <1B4B44D9196EFF41AE41FDA404FC0A10F980@SHSMSX101.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "kvm@vger.kernel.org" , ftpadmin To: "Ren, Yongjie" Return-path: Received: from mx1.redhat.com ([209.132.183.28]:60965 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752125Ab2ACKKU (ORCPT ); Tue, 3 Jan 2012 05:10:20 -0500 In-Reply-To: <1B4B44D9196EFF41AE41FDA404FC0A10F980@SHSMSX101.ccr.corp.intel.com> Sender: kvm-owner@vger.kernel.org List-ID: On 01/03/2012 05:02 AM, Ren, Yongjie wrote: > Hi folks, > I reported some kvm kernel bugs at "bugzilla.kernel.org" before the kernel.org was attacked. > Though kernel.org resumes, its bugzilla can't be accessed so far. > So, where should I report a kvm kernel bug? I mean not just reporting in this mailing list but in a bugzilla to track. > Or, could I report kvm kernel bug at qemu's bugzilla (https://bugs.launchpad.net/qemu) for tracking? > I'm surprised bugzilla.kernel.org isn't responding. Copying ftpadmin@kernel.org for ETA (though that address isn't responding, either). -- error compiling committee.c: too many arguments to function