Re: strange guest slowness after some time

["David S. Ahern" <daahern@cisco.com>]

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