On Mon, 2006-07-10 at 13:22 -0600, Jeffrey Law wrote: > On Mon, 2006-07-10 at 20:09 +0100, Mark McLoughlin wrote: > > > > > > The easy workaround is to just disable DHCP on that interface, but then > > > > the lease will never be renewed and you have a configuration difference > > > > based on whether the image is used for NFS root or not. > > > NetworkManager should be handling this for us which makes these issues > > > go away without significant mucking around. > > > > Yes, "make NetworkManager work" is another possible solution to the > > problem. But NetworkManager will also use DHCP, and NetworkManager will > > also need the lease obtained by the initrd code. It's the same problem. > > I wasn't aware NetworkManager was going to need whatever lease was > obtained in the initrd code. Out of curiosity, did you try NetworkManager with NFS root? And if it worked, are you sure NetworkManager actually did something with the device? Curious, because it sounds like it might have worked fine for you but, for me, as soon as I convinced[1] NetworkManager to manage my device, it did this: NetworkManager: <information> Now managing wired Ethernet (802.3) device 'eth0'. NetworkManager: <information> Deactivating device eth0. nfs: RPC call returned error 101 Haven't poked further, but I expect we'll just be able to pass it the lease too. Cheers, Mark. [1] - https://bugs.freedesktop.org/show_bug.cgi?id=7521 and http://lists.xensource.com/archives/html/xen-devel/2006-07/msg00475.html