search for: virstoragevolgetpath

...Error ( virSecretDefineXML ( virSecretFree ( virSecretGetUUIDString ( virSecretGetValue ( virSecretLookupByUsage ( virSecretLookupByUUIDString ( virSecretSetValue ( virSetErrorFunc ( virStoragePoolFree ( virStoragePoolGetInfo ( virStoragePoolLookupByName ( virStorageVolFree ( virStorageVolGetInfo ( virStorageVolGetPath ( virStorageVolLookupByName ( --rbKG8BlqS9xyY7Uh--

...543de73d264943fef88f5e53403bbe32917b01/lib/launch-libvirt.c#L1372 AFAICT that way does not use the storage pool drivers. > > virStoragePoolFree ( > > virStoragePoolGetInfo ( > > virStoragePoolLookupByName ( > > virStorageVolFree ( > > virStorageVolGetInfo ( > > virStorageVolGetPath ( > > virStorageVolLookupByName ( > > So something in libguestfs is using storage pools, which would > mean you want libvirt-daemon-driver-storage-core, and one or > more of the pool impls that you use. This is when libguestfs is told to open a libvirt domain, and the disks are...

...Friday, 10 January 2020 17:34:27 CET Daniel P. Berrangé wrote: > > > > virStoragePoolFree ( > > > > virStoragePoolGetInfo ( > > > > virStoragePoolLookupByName ( > > > > virStorageVolFree ( > > > > virStorageVolGetInfo ( > > > > virStorageVolGetPath ( > > > > virStorageVolLookupByName ( > > > > > > So something in libguestfs is using storage pools, which would > > > mean you want libvirt-daemon-driver-storage-core, and one or > > > more of the pool impls that you use. > > > > This...

...ol APIs. If you're using domain <disk>s which use type=volume, then you'll need the storage pool APIs & any impls that are relevant > virStoragePoolFree ( > virStoragePoolGetInfo ( > virStoragePoolLookupByName ( > virStorageVolFree ( > virStorageVolGetInfo ( > virStorageVolGetPath ( > virStorageVolLookupByName ( So something in libguestfs is using storage pools, which would mean you want libvirt-daemon-driver-storage-core, and one or more of the pool impls that you use. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |...

...72 > > AFAICT that way does not use the storage pool drivers. YEs, that is correct. > > > virStoragePoolFree ( > > > virStoragePoolGetInfo ( > > > virStoragePoolLookupByName ( > > > virStorageVolFree ( > > > virStorageVolGetInfo ( > > > virStorageVolGetPath ( > > > virStorageVolLookupByName ( > > > > So something in libguestfs is using storage pools, which would > > mean you want libvirt-daemon-driver-storage-core, and one or > > more of the pool impls that you use. > > This is when libguestfs is told to open...

...;%s': %s"), + volume_name, err->message); + goto cleanup; + } + + debug (g, "type of libvirt volume %s: %d", volume_name, info.type); + + /* Support only file-based volumes for now. */ + if (info.type != VIR_STORAGE_VOL_FILE) + goto cleanup; + + filename = virStorageVolGetPath (vol); + if (filename == NULL) { + err = virGetLastError (); + error (g, _("cannot get the filename of the libvirt volume '%s': %s"), + volume_name, err->message); + goto cleanup; + } + + cleanup: + if (vol) virStorageVolFree (vol); + if (pool) virStorage...

...;%s': %s"), + volume_name, err->message); + goto cleanup; + } + + debug (g, "type of libvirt volume %s: %d", volume_name, info.type); + + /* Support only file-based volumes for now. */ + if (info.type != VIR_STORAGE_VOL_FILE) + goto cleanup; + + filename = virStorageVolGetPath (vol); + if (filename == NULL) { + err = virGetLastError (); + error (g, _("cannot get the filename of the libvirt volume '%s': %s"), + volume_name, err->message); + goto cleanup; + } + + cleanup: + if (vol) virStorageVolFree (vol); + if (pool) virStorage...

libguestfs usually needs qemu. However it only requires an emulator for the same architecture, not for all architectures. libvirt-daemon-kvm pulls in qemu which pulls in emulators for all architectures, as well as a bunch of other stuff we don't need at all like network interface support and nwfilter. There are no Fedora TCG-only arches, so drop the conditional section. I also made support

..., + sig => "conn, string : vol" }, + { name => "virStorageVolCreateXML", + sig => "pool, string, 0U : vol from pool" }, + { name => "virStorageVolGetXMLDesc", + sig => "vol, 0U : string" }, + { name => "virStorageVolGetPath", + sig => "vol : string" }, + { name => "virStorageVolGetKey", + sig => "vol : static string" }, + { name => "virStorageVolGetName", + sig => "vol : static string" }, + { name => "virStoragePoolLo...

...information of the libvirt volume '%s': %s"), + error (g, _("cannot get information of the libvirt volume ‘%s’: %s"), volume_name, err->message); goto cleanup; } @@ -934,7 +934,7 @@ filename_from_pool (guestfs_h *g, virConnectPtr conn, filename = virStorageVolGetPath (vol); if (filename == NULL) { err = virGetLastError (); - error (g, _("cannot get the filename of the libvirt volume '%s': %s"), + error (g, _("cannot get the filename of the libvirt volume ‘%s’: %s"), volume_name, err->message); goto c...

libvirt-ocaml is used only by virt-v2v, so move it to this repository, instead of having it around in the common submodule. The removal from common will happen later. Pino Toscano (2): common: Bundle the libvirt-ocaml library for use by virt-v2v build: switch embedded copy of libvirt-ocaml .gitignore | 2 + 3rdparty/libvirt-ocaml/Makefile.am |

Hi, this is a mostly done attempt to switch to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not

Hi, this is a mostly done attempt to switch to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not

Hi, this is a mostly done attempt to switch to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not

Hi, this series switches virt-2v to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not test all

Hi, this series switches virt-2v to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not test all