From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: KVM in -next is somewhat busted Date: Mon, 08 Feb 2010 16:41:33 +0200 Message-ID: <4B70229D.4080603@redhat.com> References: <20100208142752.2e859b7d@lxorguk.ukuu.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: linux-kernel@vger.kernel.org, KVM list , Adam Litke To: Alan Cox Return-path: In-Reply-To: <20100208142752.2e859b7d@lxorguk.ukuu.org.uk> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org (fixed kvm@ address) On 02/08/2010 04:27 PM, Alan Cox wrote: > Reliably at boot time with todays -next I get the following: > > BUG: unable to handle kernel paging request at 0000000000001028 > IP: [] balloon+0x1a1/0x309 [virtio_balloon] > PGD 2cd42067 PUD 3b9dc067 PMD 0 > Oops: 0000 [#1] SMP > last sysfs file: /sys/devices/virtio-pci/virtio4/block/vdd/removable > CPU 3 > Pid: 511, comm: vballoon Not tainted 2.6.33-rc7-next-20100208+ #51 / > RIP: 0010:[] [] balloon+0x1a1/0x309 [virtio_balloon] > Looks like the guest is broken, not the host. Do things work if you leave out CONFIG_VIRTIO_BALLOON? Copying Adam Litke, who's name is on the latest balloon changes. -- error compiling committee.c: too many arguments to function