It would start but without the network. On 12/16/2010 01:40 AM, Clint Byrum wrote: > 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/351307 Title: Libvirt NFS mount on boot. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
