WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] vmx status report against changeset 15521 - 2 new issues

To: Steven Hand <Steven.Hand@xxxxxxxxxxxx>, "Zhao, Yunfeng" <yunfeng.zhao@xxxxxxxxx>
Subject: Re: [Xen-devel] vmx status report against changeset 15521 - 2 new issues
From: Mats Petersson <mats@xxxxxxxxxxxxxxxxx>
Date: Sat, 14 Jul 2007 10:33:32 +0100
Cc: Steven Hand <steven.hand@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Steven.Hand@xxxxxxxxxxxx
Delivery-date: Tue, 17 Jul 2007 05:11:20 -0700
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=googlemail.com; s=beta; h=domainkey-signature:received:received:x-mailer:date:to:from:subject:cc:in-reply-to:references:mime-version:content-type:sender:message-id; b=IAQyH+VqAC4xDuw3LGQDiWzo8mdojyOX9OZ9CBYIl7MlS/wKdWqpCK8Gl86uvFWaVyy+YMK5KldbWUlkJD4HOilRGmkBfu9LxxAbaWFFPWfIacii1MTNXZPHyA2Ty7c2eWfbqBooCrMytt1aT19ST/yj050TW5t4TfbGIS8XRws=
Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=beta; h=received:x-mailer:date:to:from:subject:cc:in-reply-to:references:mime-version:content-type:sender:message-id; b=h1OYYERxIwlEZjybPgayUAg2jXerNPVARJBenh6Y2dBLXAjmvl+YoJDuplhx6tom7GgDBeDLoBMnJuNZPQBXwZLti25umNGjMt4Vf7CwCwKUmfzag4vLJEmJ+Kv20KihYxLfba8GsEDN+cYsCC7pXDYDlvw74zjDtMOybivJ6ac=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <E1I9FcQ-0008LZ-00@xxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <E1I9FcQ-0008LZ-00@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
At 08:31 13/07/2007, Steven Hand wrote:

>>>1) Data corrupted after copied into a 32bit win2k3 guest on 64bit
>>>hypervisor with rtl8139
>>>http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=3D1025
>>
>>Have you tried this with:
>>   - 32bit windows guest on 32bit or PAE hypervisor?
>>   - 64bit windows guest on 64bit hypervisor?
>[Yunfeng] I tried 32bit/pae and 64bit/64bit, and I cannot reproduce this
>issue on them.

Ok, that's interesting.

>>It'd also be good to know what the extent of the corruption is, e.g.
>>if it affects just certain pages, etc.
>[Yunfeng] Do you have any good way to get this kind of info?

Just comparing the source and destination file page by page (or byte
by byte) and working out the ranges of differences?


Have you tried filling the buffer in QEMU with a known pattern - from the description Steven gave, it looks like it may be using an "old" buffer, so after the buffer has been "emptied", could you fill it with something, and see if that's what occurs in the "bad packet"? [Admittedly, I don't really know if there's any easy way to know when the packet has actually been "consumed" by the driver in Windows!).

It also looked like the data in the file was code or something like that - have you tried preparing a file where it's easy to see that the bytes are in the correct order (e.g. fill a file with longwords 0, 1, 2, 3, 4, and so on). Then you should be able to see if it's a "newer" or "older" packet that is incorrectly inserted (I presume).

--
Mats


(To make this even easier, start with a known, homogenous file (e.g.
all 0xa5 or something) - on receipt check md5sum of each page, and
note any differences in pages which fail the check).

cheers,

S.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel