]> git.ipfire.org Git - thirdparty/libvirt.git/commit
Check whether pools are already active upon libvirtd startup
authorDaniel P. Berrange <berrange@redhat.com>
Thu, 11 Nov 2010 20:09:20 +0000 (20:09 +0000)
committerDaniel P. Berrange <berrange@redhat.com>
Tue, 23 Nov 2010 15:00:35 +0000 (15:00 +0000)
commit1b7e0b1a9c3e94e77b2d9b09d6002167f02ad25e
treed81ff67f1a2cb6aaf2d0a90cfb3bd37a600b415e
parent4d0350fc38acc650595d8c1f53b80cfd44150172
Check whether pools are already active upon libvirtd startup

When libvirt starts up all storage pools default to the inactive
state, even if the underlying storage is already active on the
host. This introduces a new API into the internal storage backend
drivers that checks whether a storage pool is already active. If
the pool is active at libvirtd startup, the volume list will be
immediately populated.

* src/storage/storage_backend.h: New internal API for checking
  storage pool state
* src/storage/storage_driver.c: Check whether a pool is active
  upon driver startup
* src/storage/storage_backend_fs.c, src/storage/storage_backend_iscsi.c,
  src/storage/storage_backend_logical.c, src/storage/storage_backend_mpath.c,
  src/storage/storage_backend_scsi.c: Add checks for pool state
src/storage/storage_backend.h
src/storage/storage_backend_fs.c
src/storage/storage_backend_iscsi.c
src/storage/storage_backend_logical.c
src/storage/storage_backend_mpath.c
src/storage/storage_backend_scsi.c
src/storage/storage_driver.c