Libvirt NFS mount on boot.

[William King]

I have setup /etc/fstab to mount the nfs share on boot. I then realized that it wasn't being mounted on boot, but that I could mount the nfs drive with 'sudo mount -a' after boot. So I added mount -a to rc.local.

libvirt fails to start if an image is on a remote nfs drive that isn't mounted yet. especially when the virtual image is set to auto start.

[Alvin (alvind)]

Is it really the libvirt management daemon itself that does not start, or do you want libvirt to start virtual machines, as soon as the images become available?

[Chuck Short (zulcss)]

Hi,

I was wondering if this is still a problem for you?

Regards
chuck

[Chuck Short (zulcss)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Alvin (alvind)]

I can confirm that NFS mounts are not automatically mounted, when libvirtd is started during boot. I don't know if that's the actual bug, because it's new in karmic I think.

[Alvin (alvind)]

Due to bug #461133 NFS drives are not mounted at boot when using a static network interface (also see bug #446031).
There could be other reasons for not having NFS at boot.

When using autostart of virtual machines, should libvirt not wait for the netfs storage pool to become available? This would also fix bug #491273.

[Alvin (alvind)]

A workaround for this bug is restarting libvirt-bin in rc.local
However, this will also restart autostarted virtual machines (that do not reside on NFS drives), often resulting in a crash of those virtual machines.

[Dustin Kirkland  (kirkland)]

I recently migrated libvirt to use Upstart for boot.

Can you still reproduce this bug in Lucid?

[Alvin (alvind)]

I upgraded a karmic machine with libvirt and a netfs storage pool.
It's still reproducible. The pool is not activated at boot.

[Anton Altaparmakov (aia21)]

I am using a fresh install of Ubuntu 10.04 LTS Server and have used virt-manager to set up an NFS storage repository (located on another machine).

On boot the storage fails to mount.

First it was failing with "statd not running" and I fixed that by editing /etc/init/statd.conf making this change:

-start on (started portmap or mounting TYPE=nfs)
+start on ((started portmap and local-filesystems) or mounting TYPE=nfs)

Statd is now started but the NFS mount still does not happen at boot!

When I then launch virt-manager, and click on the "Play/Start" button in the Storage tab after selecting the NFS storage, it then mounts it. But I want it to be mounted automatically at boot rather than having to do it by hand each time the machine boots...

Note the server has a static (non-dhcp) IP address as all servers should have! I don't want booting to fail because the dhcp server has gone away...

Best regards,

Anton

[Clint Byrum (clint-fewbar)]

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?

[William King (quentusrex)]

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?
>

[Launchpad Janitor (janitor)]

[Expired for libvirt (Ubuntu) because there has been no activity for 60 days.]