brad's life - Xen3 and NFS in dom0 [entries|archive|friends|userinfo]
Brad Fitzpatrick

[ website | bradfitz.com ]
[ userinfo | livejournal userinfo ]
[ archive | journal archive ]

Xen3 and NFS in dom0 [Aug. 5th, 2006|09:43 am]
Previous Entry Share Next Entry
[Tags|, ]

Dear Xen3 users,

Why doesn't my nfs (nfs-kernel-server) work with Xen3 (in Debian) in dom0 anymore? Reboot into non-Xen kernel, no problem. Reboot into Xen3 kernel, nothing. I recall Xen2 worked on this box with NFS fine.

I imagine something w/ the new bridging/etc in Xen3?

Relevant export:
/raid 10.0.0.11(rw,no_root_squash,async,insecure)

Last thing seen in daemon.log:

sammy:/home/bradfitz# tail -f /var/log/daemon.log
....
Aug 5 09:37:55 sammy mountd[5473]: authenticated mount request from 10.0.0.11:1000 for /raid (/raid)

But then the NFS client (OS X) just hangs connecting.

sammy:/home/bradfitz# brctl show
bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.feffffffffff       no              peth0
                                                        vif0.0
sammy:/home/bradfitz# ifconfig 
eth0      Link encap:Ethernet  HWaddr 00:0C:F1:79:11:8D  
          inet addr:10.0.0.81  Bcast:10.0.0.255  Mask:255.255.255.0
          inet6 addr: fe80::20c:f1ff:fe79:118d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:8113378 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5072717 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1544598861 (1.4 GiB)  TX bytes:2697956600 (2.5 GiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:48382 errors:0 dropped:0 overruns:0 frame:0
          TX packets:48382 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:14529786 (13.8 MiB)  TX bytes:14529786 (13.8 MiB)

peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF  
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:17971320 errors:255 dropped:0 overruns:0 frame:142
          TX packets:5071782 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:2963190338 (2.7 GiB)  TX bytes:2720549245 (2.5 GiB)
          Base address:0xac00 Memory:ff4e0000-ff500000 

vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF  
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5072717 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8113382 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:2697956600 (2.5 GiB)  TX bytes:1544599169 (1.4 GiB)

xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF  
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2254417 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:136905335 (130.5 MiB)  TX bytes:468 (468.0 b)


Any ideas?

We're having a party later and would like music, but this is a blocker, as Slimserver need access. I could do some DAVFS mount or something I suppose, but that's kinda whack.
LinkReply

Comments:
[User Picture]From: scsi
2006-08-05 06:02 pm (UTC)

(Link)

you want to connect your slim client to my slimserver?
[User Picture]From: taral
2006-08-05 07:21 pm (UTC)

(Link)

You could switch to the userspace daemon temporarily. If you really want to debug it, you'll want to post a tcpdump -w trace.
[User Picture]From: brad
2006-08-05 09:02 pm (UTC)

(Link)

Tried that briefly a few weeks ago without success, but I don't remember why not.
[User Picture]From: xlerb
2006-08-05 08:54 pm (UTC)

(Link)

Could it be some flavor of the tx checksumming problems I was reading about the other day?
[User Picture]From: cjcollier
2006-08-06 11:19 am (UTC)

(Link)

I've been required to run

make ARCH=xen menuconfig


many times to enable bits that I expected would be included by default (such as USB support). Perhaps NFS is one of the things that the Xen configuration folks just didn't turn on by default.

Worth a try, maybe.
From: (Anonymous)
2006-08-20 02:24 pm (UTC)

(Link)

Where did you get the hypervisor and dom0 from - binary from xensource, from debian, or built it yourself from source?
[User Picture]From: brad
2006-08-20 08:00 pm (UTC)

(Link)

xen-3.0.2-install-x86_32.tgz from XenSource.