The issue of the static ip address is bug #446031, so I'm using dhcp on the servers now. I was also using a separate /boot that added to the confusion. (bug #462961, now fixed.) Setting the NFS clients to dhcp did solve this issue! I rechecked by setting a static ip again.
I will use this as a workaround now, but I'd prefer the servers to use static ip's. Using dhcp will make sure the computer boots and NFS mounts are available, but the list of error messages remain during boot: One or more of the mounts listed in /etc/fstab cannot yet be mounted: (ESC for recovery shell) etc.... This slows down the boot process. Also, when a netfs storage pool is defined for libvirtd, libvirtd does not succeed in starting that pool at boot. Could this be related? (restarting the libvirtd service after boot will mount the drives) -- karmic: nfs shares are not mounted at boot https://bugs.launchpad.net/bugs/461133 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
