[Bug 351307] Re: Libvirt NFS mount on boot.

[Clint Byrum]

Since libvirt-bin.conf comes up a runlevel [2345] .. its possible that
the network is not up yet.

This is because runlevel 2 is triggered when all automount filesystems
are mounted, and the loopback is up.

You can probably correct this issue by changing libvirt-bin.conf to be

start on net-device-up IFACE=eth0

But I don't think we could make that a generic change, since many
(most?) libvirt users will be just fine with runlevel 2.

We could do

start on runlevel [2345] or net-device-up IFACE=eth0

But that assumes that it fails to start when the network is
unavailable.. does it fail to start, or just start without the NFS
storage pool?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
https://bugs.launchpad.net/bugs/351307

Title:
  Libvirt NFS mount on boot.