On Thu, Jun 16, 2016 at 2:21 PM, Cam Mac <iuco...@gmail.com> 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: > > http://lists.ovirt.org/pipermail/users/2016-June/040298.html
You wrote: > I can access via http a list of VMs at the following URL: > https://nssesxi-mgmt/folder?dcPath=North%2520Sutton%2520Street&dsName=nssesxi%252dc2%252dr10%252dlun2 > Below is the URI to the vm itself (once shutdown, it gets the name 'vm2_1'): > https://nssesxi-mgmt/folder/wvm2_1?dcPath=North%2520Sutton%2520Street&dsName=nssesxi%252dc1%252dr10%252dlun2 Smells like vmware bug, double-escaping %20 to %2520. Did you check with vmware support? I would eliminate the spaces in the data center name to avoid such issues. Nir > > Kind regards, > > Cam > > On Wed, Jun 15, 2016 at 8:23 PM, Nir Soffer <nsof...@redhat.com> wrote: >> >> On Wed, Jun 15, 2016 at 8:41 PM, Cam Mac <iuco...@gmail.com> 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 getting rid of VMware. Using OVF files looks like a >> > lot >> > more manual work as compared to the GUI or virt-v2v, with their nice >> > conversion features. >> > >> > Any suggestions? >> >> I think the best way is use our import external vm feature. >> >> Can you point us to the mail about this? >> >> Nir > > _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users