libguestfs/virt-v2v-docs-master — English (United Kingdom) @ Fedora Weblate: This is only supported for:

Translation

Source change

English type: textblock

English (United Kingdom)

Needs editing

Skip

	English	English (United Kingdom)	Actions
	virt-v2v -i disk disk.img -o openstack -oo server-id=v2v-vm
	See L<virt-v2v-output-openstack(1)>.
	Convert disk image to disk image
	Given a disk image from another hypervisor that you want to convert to run on KVM, you have two options. The simplest way is to try:
	virt-v2v -i disk disk.img -o local -os /var/tmp
	where virt-v2v guesses everything about the input F<disk.img> and (in this case) writes the converted result to F</var/tmp>.
	A more complex method is to write some L<libvirt XML\|http://libvirt.org/formatdomain.html> describing the input guest (if you can get the source hypervisor to provide you with libvirt XML, then so much the better). You can then do:
	virt-v2v -i libvirtxml guest-domain.xml -o local -os /var/tmp
	Since F<guest-domain.xml> contains the path(s) to the guest disk image(s) you do not need to specify the name of the disk image on the command line.
	To convert a local disk image and immediately boot it in local qemu, do:
	virt-v2v -i disk disk.img -o qemu -os /var/tmp --qemu-boot
	B<--bandwidth> bps
	B<--bandwidth-file> filename	B<--add> file
	Some input methods are able to limit the network bandwidth they will use statically or dynamically. In the first variant this sets the bandwidth limit statically in bits per second. Formats like C<10M> may be used (meaning 10 megabits per second).
	In the second variant the bandwidth is limited dynamically from the content of the file (also in bits per second, in the same formats supported by the first variant). You may use both parameters together, meaning: first limit to a static rate, then you can create the file while virt-v2v is running to adjust the rate dynamically.
	This is only supported for:	Windows 8 is now supported.
	L<input from Xen\|virt-v2v-input-xen(1)>
	L<input from VMware VMX\|virt-v2v-input-vmware(1)/INPUT FROM VMWARE VMX> when using the SSH transport method
	L<input from VDDK\|virt-v2v-input-vmware(1)/INPUT FROM VDDK>
	I<-i libvirtxml> when using HTTP or HTTPS disks
	L<input from VMware vCenter server\|virt-v2v-input-vmware(1)/INPUT FROM VMWARE VCENTER SERVER>
	The options are silently ignored for other input methods.
	B<-b> ...
	B<--bridge> ...
	See I<--network> below.
	B<--colors>
	B<--colours>
	Use ANSI colour sequences to colourize messages. This is the default when the output is a tty. If the output of the program is redirected to a file, ANSI colour sequences are disabled unless you use this option.
	B<--compressed>
	Write a compressed output file. This is only allowed if the output format is qcow2 (see I<-of> below), and is equivalent to the I<-c> option of L<qemu-img(1)>.
	B<--debug-overlays>

Loading…

None

Source string changed

English 16 characters edited

3 years ago

Browse all string changes

Things to check

Mismatched colon

Source and translation do not both end with a colon

Reset

Mismatched full stop

Source and translation do not both end with a full stop

Reset

Glossary

English	English (United Kingdom)
No related strings found in the glossary.

String information

Source string description

type: textblock

Source string location

docs/virt-v2v.pod:175

String age

3 years ago

Last updated

11 months ago

Source string age

3 years ago

Translation file

po-docs/en_GB.po, string 771