Re: [ovirt-users] gluster VM disk permissions
On Fri, May 20, 2016 at 02:53:02PM -0700, Bill James wrote:
maybe the other doc is old but it says:
"And a feature I intentionally removed in RHEL 7 was importing KVM → KVM"
which is what I am doing. raw disk KVM to ovirt.
Yes I can copy the disk image over the top of a ovirt disk image,
but the import script seemed cleaner.
Does virt-v2v try to convert the KVM image to KVM image or does it
just import it?
Virt-v2v will now refuse to do this at all (except if you "trick" it
as I did in my blog posting), but if we allowed it then it would make
all kinds of modifications inside the guest which you don't need and
have at least the potential to break things.
The import-to-ovirt.pl script is/was intended as a simple import
script which you should use instead in the case where guests already
run on KVM and therefore don't need driver etc conversion/
installation.
As Nir said in the other reply, oVirt 4.0 has native import
functionality and the import script is not needed at all for KVM ->
oVirt imports.
Virt-v2v should only be used for foreign hypervisor imports, such as
VMware, Xen or Hyper-V to oVirt.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual machines. Supports shell scripting,
bindings from many languages. http://libguestfs.org