Skip to content

L
libvirt

openeuler / libvirt

通知 3
Star 0
Fork 0
L
libvirt

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 16 5月, 2018 11 次提交
  3. 07 5月, 2018 1 次提交
  5. 04 5月, 2018 1 次提交
  7. 11 4月, 2018 1 次提交
  9. 01 2月, 2018 2 次提交
  11. 30 1月, 2018 1 次提交
    • P
      storage: util: Properly ignore errors when backing volume is inaccessible · b2c5f28a
      由 Peter Krempa 提交于 
      Commit 000e9504 tried to fix improper bracketing when refreshing disk
volume stats for a backing volume. Unfortunately the condition is still
wrong as in cases as the backing store being inaccessible
storageBackendUpdateVolTargetInfo returns -2 if instructed to ignore
errors. The condition does not take this into account.

Dumping XML of a volume which has inacessible backing store would then
result into:

 # virsh vol-dumpxml http.img --pool default
 error: An error occurred, but the cause is unknown

Properly ignore -2 for backing volumes.

Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1540022
      b2c5f28a
  13. 03 1月, 2018 1 次提交
  15. 27 10月, 2017 5 次提交
  17. 17 10月, 2017 1 次提交
    • P
      util: storagefile: Add helpers to check presence of backing store · 0a294a8e
      由 Peter Krempa 提交于 
      Add helpers that will simplify checking if a backing file is valid or
whether it has backing store. The helper virStorageSourceIsBacking
returns true if the given virStorageSource is a valid backing store
member. virStorageSourceHasBacking returns true if the virStorageSource
has a backing store child.

Adding these functions creates a central points for further refactors.
      0a294a8e
  19. 06 10月, 2017 1 次提交
  21. 05 10月, 2017 1 次提交
  23. 27 9月, 2017 1 次提交
    • J
      virStorageFileResize: fallocate the whole capacity · 3f702f5a
      由 Ján Tomko 提交于 
      We have been trying to implement the ALLOCATE flag to mean
"the volume should be fully allocated after the resize".

Since commit b0579ed9 we do not allocate from the existing
capacity, but from the existing allocation value.
However this value is a total of all the allocated bytes,
not an offset.

For a sparsely allocated file:
$ perl -e 'print "x"x8192;' > vol1
$ fallocate -p -o 0 -l 4096 vol1
$ virsh vol-info vol1 default
Capacity:       8.00 KiB
Allocation:     4.00 KiB

Treating allocation as an offset would result in an incompletely
allocated file:
$ virsh vol-resize vol1 --pool default 16384 --allocate
Capacity:       16.00 KiB
Allocation:     12.00 KiB

Call fallocate from zero on the whole requested capacity to fully
allocate the file. After that, the volume is fully allocated
after the resize:
$ virsh vol-resize vol1 --pool default 16384 --allocate
$ virsh vol-info vol1 default
Capacity:       16.00 KiB
Allocation:     16.00 KiB
      3f702f5a
  25. 19 9月, 2017 1 次提交
    • J
      storage: Introduce storage volume add, delete, count APIs · 40630a8e
      由 John Ferlan 提交于 
      Create/use virStoragePoolObjAddVol in order to add volumes onto list.

Create/use virStoragePoolObjRemoveVol in order to remove volumes from list.

Create/use virStoragePoolObjGetVolumesCount to get count of volumes on list.

For the storage driver, the logic alters when the volumes.obj list grows
to after we've fetched the volobj. This is an optimization of sorts, but
also doesn't "needlessly" grow the volumes.objs list and then just decr
the count if the virGetStorageVol fails.
Signed-off-by: NJohn Ferlan <jferlan@redhat.com>
      40630a8e
  27. 31 8月, 2017 1 次提交
  29. 22 7月, 2017 1 次提交
  31. 18 5月, 2017 2 次提交
    • M
      Introduce virStorageVol{Download,Upload}Flags · 1f43aa67
      由 Michal Privoznik 提交于 
      These flags to APIs will tell if caller wants to use sparse
stream for storage transfer. At the same time, it's safe to
enable them in storage driver frontend and rely on our backends
checking the flags. This way we can enable specific flags only on
some specific backends, e.g. enable
VIR_STORAGE_VOL_DOWNLOAD_SPARSE_STREAM for filesystem backend but
not iSCSI backend.
Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      1f43aa67
    • M
      fdstream: Implement sparse stream · 89547964
      由 Michal Privoznik 提交于 
      Basically, what is needed here is to introduce new message type
for the messages passed between the event loop callbacks and the
worker thread that does all the I/O. The idea is that instead of
a queue of read buffers we will have a queue where "hole of size
X" messages appear. That way the event loop callbacks can just
check the head of the queue and see if the worker thread is in
data or a hole section and how long the section is.
Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      89547964
  33. 26 4月, 2017 2 次提交
    • J
      storage: Introduce virStorageBackendZeroPartitionTable · e8b02124
      由 John Ferlan 提交于 
      Create a wrapper/helper that can be used to call the storage backend
wipe helper - storageBackendVolWipeLocalFile for future use by logical
and disk backends to clear out the partition table rather than having
each open code the same algorithm.
      e8b02124
    • J
      storage: Modify storageBackendWipeLocal to allow zero from end of device · 859a2d16
      由 John Ferlan 提交于 
      Add bool 'zero_end' and logic that would allow a caller to wipe specific
portions of a target device either from the beginning (the default) or
from the end when zero_end is true.

This will allow for this code to wipe out partition table information
from a device.
      859a2d16
  35. 07 4月, 2017 2 次提交
  37. 06 4月, 2017 1 次提交
  39. 04 4月, 2017 3 次提交