[Expired for libvirt (Ubuntu) because there has been no activity for 60
days.]
** Changed in: libvirt (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
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
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:
I upgraded a karmic machine with libvirt and a netfs storage pool.
It's still reproducible. The pool is not activated at boot.
** Tags added: lucid
--
Libvirt NFS mount on boot.
https://bugs.launchpad.net/bugs/351307
You received this bug notification because you are a member of Ubuntu
Server
I recently migrated libvirt to use Upstart for boot.
Can you still reproduce this bug in Lucid?
--
Libvirt NFS mount on boot.
https://bugs.launchpad.net/bugs/351307
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
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.
--
Libvirt NFS mount on boot.
https://bugs.launchpad.net/bugs/351307
You
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
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.
--
Libvirt NFS mount on boot.
https://bugs.launchpad.net/bugs/351307
You received this bug notification because you are a
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!
--
Libvirt NFS mount on boot.
https://bugs.launchpad.net/bugs/351307
You received this bug notification because you are a member of
Hi,
I was wondering if this is still a problem for you?
Regards
chuck
** Changed in: libvirt (Ubuntu)
Importance: Undecided = Low
** Changed in: libvirt (Ubuntu)
Status: New = Incomplete
--
Libvirt NFS mount on boot.
https://bugs.launchpad.net/bugs/351307
You received this bug
10 matches
Mail list logo
