search for: target_path

...e Thu Jun 30 18:41:11 2005 +++ b/tools/ioemu/target-i386-dm/Makefile Thu Jun 30 18:59:08 2005 @@ -3,12 +3,11 @@ include config.mak override TARGET_ARCH=i386 -#assume we directly put qemu code in tools/, same level as bochs dm(ioemu) -XEN_PATH=../../.. +INSTALL_DIR := $(DESTDIR)/usr/lib/xen/bin TARGET_PATH=$(SRC_PATH)/target-$(TARGET_ARCH) VPATH=$(SRC_PATH):$(TARGET_PATH):$(SRC_PATH)/hw:$(SRC_PATH)/audio -DEFINES=-I. -I$(TARGET_PATH) -I$(SRC_PATH) -I$(XEN_PATH)/xen/include/public -DEFINES+= -I$(XEN_PATH)/tools/libxc +DEFINES=-I. -I$(TARGET_PATH) -I$(SRC_PATH) -I$(XEN_ROOT)/xen/include/public +DEFINE...

...t) doesn't support taking snapshots of a live guest which has active filesystem shares (type='mount'). I get this error: Call to virDomainSaveFlags failed: internal error: unable to execute QEMU command 'migrate': Migration is disabled when VirtFS export path '${TARGET_PATH}' is mounted in the guest using mount_tag '$TAG' (Libvirt::Error) I have a use case where I very much would like this combination. It wouldn't be a problem if the filesystem shares would have to be temporarily unmounted while taking the snapshot, and mounted again after restori...

When importing from VMware via the libvirt driver, the libvirt driver can add an empty source bridge name: <interface type='bridge'> <mac address='00:01:02:03:04:05:06'/> <source bridge=''/> </interface> Replicate what we do on the -i ova path, and map these to "eth0", "eth1" etc. This also includes a bunch

This changes the infrastructure to allow the target_file to be a QEMU URI. Rich.

When I submitted the qcow2 patch for blktap, suggestions came up that the qemu block drivers should be used also for blktap to eliminate the current code duplication in ioemu and blktap. The attached patch adds support for a tap:ioemu pseudo driver. Devices using this driver won''t use tapdisk (containing the code duplication) any more, but will connect to the qemu-dm of the domain. In

This patch provides the ability to create a "dir" type storage pool, and to add and remove volumes for existing pools.

This set of patches supercedes the previous set, and has been rebased with changes from upstream.

This patch again rebases on upstream and should apply on next as of right now.

...e.value()) + else: + return True + else: + errors.append("Storage object name must be a string between 0 and 50 characters.") + elif page is POOL_DETAILS_PAGE: + result = True + if self.__config.needs_target_path(): + if utils.string_is_not_blank(self.__target_path.value()): + if self.__target_path.value()[0:1] is not '/': + errors.append("'%s' is not an absolute path." % self.__target_path.value()) + r...

This pair of patches provide a new storage admin interface. Then, on top of that, it refactors the domain administration pieces to now properly use storage pools and volumes when defining a new VM.

This patch obsoletes any previous ones. This is an upstream candidate, so I'm looking for feedback so we can push this and start using it.

This version fixes a few bugs found by jboggs. It also includes some logging facilities that need to be fleshed out more.

This patch is ready for pushing upstream.

The previous patch was missing this file. Resending.

This patch is incomplete, but early feedback would be welcome. Rich.

Previously posted: https://www.redhat.com/archives/libguestfs/2018-November/msg00000.html https://www.redhat.com/archives/libguestfs/2018-November/msg00001.html This completes the split and rewrite of the virt-v2v manual to make it much simpler to understand and digest. Rich.

...39; is not a directory (type='dir'). See virt-v2v(1) section \"OUTPUT TO LIBVIRT\"") output_pool; + error (f_"-o libvirt: output pool ‘%s’ is not a directory (type='dir'). See virt-v2v(1) section \"OUTPUT TO LIBVIRT\"") output_pool; let target_path = match xpath_string "/pool/target/path/text()" with | None -> - error (f_"-o libvirt: output pool '%s' does not have /pool/target/path element. See virt-v2v(1) section \"OUTPUT TO LIBVIRT\"") output_pool + error (f_"-o li...