From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dor Laor Subject: Re: STOP error with virtio on KVM-79/2.6.18/Win2k3 x64 guest Date: Tue, 02 Dec 2008 00:26:40 +0200 Message-ID: <493464A0.30109@redhat.com> References: <3D753CDC7D3A054CADC4DC2DF4C9F66502027860@LGC-MX01.corp.lehighgas.local> Reply-To: dlaor@redhat.com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, Avi Kivity To: Adrian Schmitz Return-path: Received: from mx2.redhat.com ([66.187.237.31]:51043 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752728AbYLAW0c (ORCPT ); Mon, 1 Dec 2008 17:26:32 -0500 In-Reply-To: <3D753CDC7D3A054CADC4DC2DF4C9F66502027860@LGC-MX01.corp.lehighgas.local> Sender: kvm-owner@vger.kernel.org List-ID: Adrian Schmitz wrote: > Sorry for the repost.. I forgot the subject line! > Hi, I'm having problems with STOP errors (0x000000d1) under > KVM-79/2.6.18 whenever I try to use the virtio drivers. This post > (http://marc.info/?l=kvm&m=121089259211638&w=2) describes the issue > exactly, except that I'm using a Win2k3 x64 guest with the x64 > paravirtual drivers instead of 32-bit guest/drivers. I am able to > reproduce the problem reliably using iperf, the same as in the above > post. When I disable virtio, the guest is very stable. Any suggestions > are greatly appreciated. > > What driver version are you using? Version 2 is obsolete. I posted ver 3 few months ago, Avi can you please upload it to sourceforge. My old public space was blocked so I'll send you a private attachment to test. Dor. > -Adrian > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >