VMware {code} Community
starkman
Contributor
Contributor
Jump to solution

How to import an OVA?

I having trouble getting this to work.  I followed the steps

1)Validate OVF

2)Create Import Spec

3)ImportVapp

I get the lease *HttpNfcLease" back but from there it goes down hill.

The VM is never created on the host.  However the directory containing the VM is created on the host datastore with the correct name and all the files.  The lease is forever in the "initializing" state.  Please help.

--Ken

Tags (2)
0 Kudos
1 Solution

Accepted Solutions
matt222r
Contributor
Contributor
Jump to solution

This was happening to me too, and I stopped it by passing in valid, non-null arguments for "folder" and "host" when calling importVApp.

View solution in original post

0 Kudos
3 Replies
starkman
Contributor
Contributor
Jump to solution

As a little more information I looked at the logs from the host and compared them to importing the same test ova from vsphere..

Anyone Please?

From c# client log snip

Retrieved current VM state from foundry 5, 2

State Transition (VM_STATE_INITIALIZING -> VM_STATE_OFF)
ModeMgr::End: op = normal, current = normal, count = 1
Predicted VM overhead: 124555264 bytes
Initialized virtual machine.
Create DONE: /vmfs/volumes/4e9fef25-926aecf0-86bf-000c29471f77/KAS-AutoDeployVA/KAS-AutoDeployVA.vmx
Create worker thread completed succesfully
Unregister called on virtual machine
State Transition (VM_STATE_OFF -> VM_STATE_UNREGISTERING)
[2012-01-24 17:21:34.712 23540B90 verbose 'DatastoreBrowser'] 224-envmgr-datastorebrowser::Destroy
[2012-01-24 17:21:34.712 23540B90 verbose 'Vmsvc'] Released Vm Id: 224.
Close Handle called
Shutting down VMDB service...
Unregistering callback...
...done
[2012-01-24 17:21:34.712 FFDD2B90 verbose 'App'] Looking up object with name = "224" failed.
[2012-01-24 17:21:34.712 FFDD2B90 panic 'ThreadPool'] Worker: Unhandled exception:
0d15a528
[2012-01-24 17:21:34.712 FFDD2B90 error 'App']
Exception: Object not found: LookupObject: id = 224
Type: N7Vmacore17NotFoundExceptionE
Backtrace:
[00] rip 1305e8b3 
[01] rip 12ef0cae 
[02] rip 12e90682 
From VShpere Log snip

verbose  Retrieved current VM state from foundry 5, 2

info State Transition (VM_STATE_INITIALIZING -> VM_STATE_OFF)
verbose 'ha-host' opID=58F303D1-00000152] ModeMgr::End: op = normal, current = normal, count = 1
verbose  Predicted VM overhead: 124555264 bytes
info 'vm:/vmfs/volumes/4e9fef25-926aecf0-86bf-000c29471f77/No-NetworkFree-Dos/No-NetworkFree-Dos.vmx' opID=58F303D1-00000152] Initialized virtual machine.
verbose  Create DONE: /vmfs/volumes/4e9fef25-926aecf0-86bf-000c29471f77/No-NetworkFree-Dos/No-NetworkFree-Dos.vmx
info 'ha-eventmgr' opID=58F303D1-00000152] Event 75 : Created virtual machine  on localhost.prod.quest.corp in ha-datacenter
verbose  Create worker thread completed succesfully
info  State Transition (VM_STATE_OFF -> VM_STATE_IMPORTING)
verbose 'ha-host' opID=58F303D1-00000152] ModeMgr::Begin: op = normal, current = normal, count = 0
0 Kudos
matt222r
Contributor
Contributor
Jump to solution

This was happening to me too, and I stopped it by passing in valid, non-null arguments for "folder" and "host" when calling importVApp.

0 Kudos
starkman
Contributor
Contributor
Jump to solution

Thanks for your help...That is indeed the solution I came up with.. I opened a ticket with vmware and they came back and said it was a known issue but they did not reccommend using a valid Folder parameter though. They can simply "Fix" the issue just by changing thier documentation.

0 Kudos