From mboxrd@z Thu Jan 1 00:00:00 1970 From: "David S. Ahern" Subject: Re: strange guest slowness after some time Date: Thu, 19 Mar 2009 08:11:12 -0600 Message-ID: <49C25280.8020202@cisco.com> References: <49B29705.6000904@wpkg.org> <49BFF8D2.5080000@wpkg.org> <49C094D0.2070905@redhat.com> <200903191529.15081.rusty@rustcorp.com.au> <49C1D6A2.4070604@cisco.com> <49C1E17A.1090102@cisco.com> <49C1FC58.6050109@wpkg.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Rusty Russell , Avi Kivity , Felix Leimbach , kvm@vger.kernel.org, Anthony Liguori To: Tomasz Chmielewski Return-path: Received: from sj-iport-3.cisco.com ([171.71.176.72]:49060 "EHLO sj-iport-3.cisco.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753999AbZCSOLR (ORCPT ); Thu, 19 Mar 2009 10:11:17 -0400 In-Reply-To: <49C1FC58.6050109@wpkg.org> Sender: kvm-owner@vger.kernel.org List-ID: Tomasz Chmielewski wrote: > David S. Ahern schrieb: >> >> David S. Ahern wrote: >>> Rusty Russell wrote: >>>> On Wednesday 18 March 2009 16:59:36 Avi Kivity wrote: >>>>> Tomasz Chmielewski wrote: >>>>>> virtio_net virtio0: id 64 is not a head! >>>> This means that qemu said "I've finished with buffer 64" and the >>>> guest didn't >>>> know anything about buffer 64. >>>> >>>> We should not lock up, tho networking is toast: I think that qemu >>>> got upset >>>> and that caused this as well as it to chew 100% cpu. >>>> >>>> I'll see if I can reproduce with kvm-84 userspace and 2.6.27 guests, >>>> 32-bit >>>> guests on a 64-bit AMD host. What's your kvm/qemu command line? >>>> >>> I've hit this as well. >>> >>> Intel host, running RHEL5.3, x86_64 with KVM-81. >>> >>> Guest is RHEL4.7, 32-bit, with the virtio drivers from RHEL4.8 beta. >>> >>> Happens pretty darn quickly for me. >>> >>> david >>> >> >> Like I said, pretty darn quickly. > > Can you reproduce it also with e1000 instead of virtio? > > I have not had a problem with the e1000 nic. This seems to be strictly a virtio bug; I get the same messages. These are 2 separate runs, one from March 11: kernel: virtio_net virtio0: id 98 is not a head! and the other last night: kernel: virtio_net virtio0: id 6 is not a head! david