Displaying 3 results from an estimated 3 matches for "guests_dir".
Did you mean:
guestfsdir
2015 Jul 27
4
[PATCH] v2v: add --in-place mode
...t in this case
+# it's especially bad because we don't want to start creating guests
+# or storage pools in the system namespace.
+if [ "$(id -u)" -eq 0 ]; then
+ echo "$0: test skipped because you're running tests as root. Don't do that!"
+ exit 77
+fi
+
+guests_dir="$(cd $(dirname $0)/../tests/guests && pwd)"
+libvirt_uri="test://$guests_dir/guests.xml"
+
+f="$guests_dir/windows.img"
+if ! test -f $f || ! test -s $f; then
+ echo "$0: test skipped because phony Windows image was not created"
+ exit 77
+fi
+...
2015 Jul 28
0
Re: [PATCH] v2v: add --in-place mode
...ly bad because we don't want to start creating guests
> +# or storage pools in the system namespace.
> +if [ "$(id -u)" -eq 0 ]; then
> + echo "$0: test skipped because you're running tests as root. Don't do that!"
> + exit 77
> +fi
> +
> +guests_dir="$(cd $(dirname $0)/../tests/guests && pwd)"
> +libvirt_uri="test://$guests_dir/guests.xml"
> +
> +f="$guests_dir/windows.img"
> +if ! test -f $f || ! test -s $f; then
> + echo "$0: test skipped because phony Windows image was not created...
2015 Aug 11
41
[PATCH v2 00/17] v2v: add --in-place mode
This series is a second attempt to add a mode of virt-v2v operation
where it leaves the config and disk image conversion, rollback on
errors, registering with the destination hypervisor, etc. to a
third-party toolset, and performs only tuning of the guest OS to run in
the KVM-based hypervisor.
The first 14 patches are just refactoring and rearrangement of the code,
factoring the implementation