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-users

RE: [Xen-users] Stop 8E with GPL PV Drivers

To: "Nick Couchman" <Nick.Couchman@xxxxxxxxx>
Subject: RE: [Xen-users] Stop 8E with GPL PV Drivers
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Fri, 31 Oct 2008 13:35:24 +1100
Cc: Pekka.Panula@xxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 30 Oct 2008 19:36:03 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4909604E.87A6.0099.1@xxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4907DA23020000A6000061B2@xxxxxxxxxxxxxxxxxxxxx> <490813E10200009900030756@xxxxxxxxxxxxxxxxxxxxx> <490813E10200009900030756@xxxxxxxxxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D0154FA0C@trantor> <4909604E.87A6.0099.1@xxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Ack6knWkCxMpfuryTRihhEeqKKGUDgAbcwiw
Thread-topic: [Xen-users] Stop 8E with GPL PV Drivers
> 
> Okay, attached is the output from the debug session - looks like
there's
> some more info there.  Also, FYI, the file you uploaded isn't a zip
file,
> it's the actual .sys file.  I kept getting a message about a corrupt
> archive file and finally used the "file" command on Linux and
determined
> that the zip file wasn't actually a zip file.  I was still able to use
it,
> but just thought I'd let you know.
> 

D'oh. Yes I must have goofed somewhere. Pity, the version you used
didn't have one extra debug statement in it. I have just uploaded update
5, but maybe wait a bit and I'll have a proper fix for you.

The data that did come out tells me that there were 4 buffers supplied:
14 bytes (Ethernet header)
20 bytes (IP header)
8 bytes (? - normally this would be the ICMP/TCP/UDP header, but I guess
you are using another protocol)
0 bytes (???)

I'm pretty sure I can see the problem - the original failing ASSERT was
to make sure that there was no data left over after we processed the
expected data in the buffers. I did that by checking for another buffer
on the end. In your case though, even though there is another buffer on
the end, it has no data in it, so my check was making an invalid
assumption.

James

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

<Prev in Thread] Current Thread [Next in Thread>