Basically, I boot windows in safe mode and remove vmware tools. In this case I
was able to use old VM if there are issues with conversion. Of course you can
remove vmware tools before migration.
Linux VMs do not need the convertor. The procedure is much simpler:
1. Make sure you don't use
Hi Pavel,
Just to clarify: I've read on the virt-v2v page that you should remove the
VMware tools from the Windows VM before migration - for step 13 in your
list, does that apply only to non-windows VMs?
Cheers,
Cam
On Fri, Jun 17, 2016 at 10:54 AM, Cam Mac wrote:
> Hi
Hi Pavel,
I was testing an import of a Win 7 VM, though there are 2012 ones to import
as well. Thanks for all those steps, I'll try them out.
Cheers,
Cam
On Thu, Jun 16, 2016 at 7:31 PM, Pavel Gashev wrote:
> Cam,
>
>
>
> I did import vmware VMs, but it was not an easy
I wasn't either and was beating my head against the wall trying to get
it to work and finally found a post that mentioned it. In hindsight it
makes sense because the vdsm account is what it runs under but nowhere
in any document I've found from RH or oVirt on conversion does it
mention
Cam,
I did import vmware VMs, but it was not an easy procedure. Last time I did it,
there were the following issues:
* oVirt engine didn't support 32bit VMs. If you have a 32bit VM in vCenter, you
are not able to see the list VMs to import.
* There were issues if you have a cluster in vCenter.
On Thu, Jun 16, 2016 at 2:21 PM, Cam Mac wrote:
> Hi Nir,
>
> I have tried the import vm feature, but with no luck. Here is the original
> email I sent, which
> includes logs attached of the errors when using this tool:
>
>
Hi Shahar,
The details of my attempts, including the log, are at:
http://lists.ovirt.org/pipermail/users/2016-June/040298.html. The version
of VMware vCenter and vSphere is 6.0.
Please let me know if you need any further information.
Cheers,
Cam
On Thu, Jun 16, 2016 at 7:00 AM, Shahar Havivi
Hi Brett,
Thanks for the reply. Yes, I tried the GUI, and it failed (the original
email is at: http://lists.ovirt.org/pipermail/users/2016-June/040298.html,
which includes log files). I wasn't aware that virt-v2v doesn't like being
run as root, so I will try it as user vdsm. I will try your other
Hi Nir,
I have tried the import vm feature, but with no luck. Here is the original
email I sent, which
includes logs attached of the errors when using this tool:
http://lists.ovirt.org/pipermail/users/2016-June/040298.html
Kind regards,
Cam
On Wed, Jun 15, 2016 at 8:23 PM, Nir Soffer
On 15.06.16 22:23, Nir Soffer wrote:
> On Wed, Jun 15, 2016 at 8:41 PM, Cam Mac wrote:
> > Hi,
> >
> > I haven't had any luck using the oVirt GUI or virt-v2v (see earlier email),
> > and I need to find a way to migrate quite a few Windows hosts (Windows 7,
> > 2012, 2008, 2k3
On 06/15/2016 01:41 PM, Cam Mac wrote:
Hi,
I haven't had any luck using the oVirt GUI or virt-v2v (see earlier
email), and I need to find a way to migrate quite a few Windows hosts
(Windows 7, 2012, 2008, 2k3 etc) into my test oVirt cluster as a PoC
so I can make a compelling case for
On Wed, Jun 15, 2016 at 8:41 PM, Cam Mac wrote:
> Hi,
>
> I haven't had any luck using the oVirt GUI or virt-v2v (see earlier email),
> and I need to find a way to migrate quite a few Windows hosts (Windows 7,
> 2012, 2008, 2k3 etc) into my test oVirt cluster as a PoC so I can
12 matches
Mail list logo