[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] RE: GPLPV on opensolaris, another try


  • To: "Fajar A. Nugraha" <fajar@xxxxxxxxx>, "Xen Users" <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
  • Date: Sat, 7 Feb 2009 09:09:55 +1100
  • Cc:
  • Delivery-date: Fri, 06 Feb 2009 14:10:56 -0800
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AcmISZov/yc6e7OtSUqyIWxrE4dK/AAXadKg
  • Thread-topic: GPLPV on opensolaris, another try

> Hi James,
> 
> I've just updated my Opensolaris installation to the latest build
> available (snv_106), and want to test GPLPV on it again. David
> Edmondson from Sun also has expressed his interest in helping to get
> GPLPV working on Opensolaris dom0
> 
> http://opensolaris.org/jive/thread.jspa?messageID=335550
> 
> So here goes. As it stands right now :
> - driver installation is succesful
> - boot with /NOGPLV both disk and network works correctly.
> - boot WITHOUT /NOGPLV disk driver works correctly. Network icon shows
> connected, but no traffic is getting through.
> 
> Here's what I get from tcpdump on dom0 during a ping test from domU
> 
> # tcpdump -n -i bnx0 src or dst 192.168.129.1
> tcpdump: verbose output suppressed, use -v or -vv for full protocol
decode
> listening on bnx0, link-type EN10MB (Ethernet), capture size 96 bytes
> 17:28:43.080609 arp who-has 192.168.129.1 tell 192.168.129.99
> 17:28:43.081106 arp reply 192.168.129.1 is-at 00:16:3e:df:d5:c0
> 17:28:48.480171 arp who-has 192.168.129.1 tell 192.168.129.99
> 17:28:48.480607 arp reply 192.168.129.1 is-at 00:16:3e:df:d5:c0
> 
> 192.168.129.99 is domU's ip address, 192.168.129.1 is the router, bnx0
> is physical interface on dom0. Both arp request and reply passes
> through dom0 just fine, but it seems that domU isn't getting the arp
> reply.
> 
> Any ideas on how to get this working?
> 

That seems to be working a bit better than last time, I think the
network never even connected.

Can you try disabling all offloads in Windows (checksum and large send)?

Also try running wireshark or another traffic capture routine and see
what that picks up. It could be getting corrupt packets or no packets at
all.

There could maybe be something wrong with broadcast packets... try
adding an arp entry manually in Dom0 for DomU and then try pinging it.

James

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.