Here is what worked for us: 1. Download the VMware workstation image from http://downloads.osv.io.s3.amazonaws.com/cloudius/osv/osv-v0.24.vmw.zip. 2. Import/deploy it into VMware workstation. 3. Delete harddrive from imported image. 4. Add your *.vmdk drive. 5. Export as ova. 6. Deploy VMware esxi.
Also I realized that *.ova files are in tar archive format so one can easily extract content and compare ovf files inside: tar tvf osv-v0.24.esx.ova -rw-r--r-- 0 someone 64 4387 Nov 3 2015 osv-esx.ovf -rw-r--r-- 0 someone 64 127 Nov 3 2015 osv-esx.mf -rw-r--r-- 0 someone 64 23292416 Nov 3 2015 osv-esx-disk1.vmdk I did a comparison between the content of this ova tar and one generated using the process above and here are the differences: 1. The osv-v0.24.esx.ova was generated using ovftool 3.0.1 where mine was generated using ovftool 3.5.0. 2. The name of the disk in is <rasd:ElementName>disk1</rasd:ElementName> where in mine it is <rasd:ElementName>disk0</rasd:ElementName>. 2,3c2,3 < <!--Generated by VMware ovftool 3.5.0 (build-1274719), UTC time: 2017-02-09T22:56:21.33943Z--> < <Envelope vmw:buildId="build-1274719" xmlns="http://schemas.dmtf.org/ovf/envelope/1"; xmlns:cim="http://schemas.dmtf.org/wbem/wscim/1/common"; xmlns:ovf="http://schemas.dmtf.org/ovf/envelope/1"; xmlns:rasd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSettingData"; xmlns:vmw="http://www.vmware.com/schema/ovf"; xmlns:vssd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_VirtualSystemSettingData"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> --- > <!--Generated by VMware ovftool 3.0.1 (build-801290), UTC time: > 2015-11-03T08:27:31.355373Z--> > <Envelope vmw:buildId="build-801290" > xmlns="http://schemas.dmtf.org/ovf/envelope/1"; > xmlns:cim="http://schemas.dmtf.org/wbem/wscim/1/common"; > xmlns:ovf="http://schemas.dmtf.org/ovf/envelope/1"; > xmlns:rasd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSettingData"; > xmlns:vmw="http://www.vmware.com/schema/ovf"; > xmlns:vssd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_VirtualSystemSettingData"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> 5c5 < <File ovf:href="elasticsearch-2.4.4-with-httpserver-disk1.vmdk" ovf:id="file1" ovf:size="65233408"/> --- > <File ovf:href="osv-esx-disk1.vmdk" ovf:id="file1" ovf:size="23292416"/> 9c9 < <Disk ovf:capacity="256" ovf:capacityAllocationUnits="byte * 2^20" ovf:diskId="vmdisk1" ovf:fileRef="file1" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized"; ovf:populatedSize="77856768"/> --- > <Disk ovf:capacity="10" ovf:capacityAllocationUnits="byte * 2^30" > ovf:diskId="vmdisk1" ovf:fileRef="file1" > ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized"; > ovf:populatedSize="30539776"/> 57c57 < <rasd:ElementName>disk0</rasd:ElementName> --- > <rasd:ElementName>disk1</rasd:ElementName> 88c88 < </Envelope> \ No newline at end of file --- > </Envelope> \ No newline at end of file 3. The *.mf file in osv-v0.24.esx.ova did have sha1 entries from both vmf and vmdk file but not in mine: 1,2c1,2 < SHA1(elasticsearch-2.4.4-with-httpserver-disk1.vmdk)= 8cbaec3f3a3f1b960695763ae0d0b4a84a13ff23 < \ No newline at end of file --- > SHA1(osv-esx.ovf)= 4d74e73a7786fb750a49c0f04b1975f1bd338885 > SHA1(osv-esx-disk1.vmdk)= cb54feb460e09558800a0e5ae1a1763e85c584ee Regards, Waldek On Wednesday, January 25, 2017 at 7:34:18 PM UTC-5, Ben Wright wrote: > Hi Lyor > > Did you ever get this fixed? > > Best > > Ben > > On Thursday, March 26, 2015 at 7:20:48 AM UTC-7, Lyor Goldstein wrote: > > Hi, > > > > > > > > After not using for quite a while OVA images, I wanted to try again. I > > therefore got the latest code, and compiled everything as always: > > > > > > > > > > make clean > > > > make image=java-shell jdkbase=$JAVA_HOME > > > > scripts/gen-vmx.sh > > > > make osv.vmdk > > > > ovftool build/release.x64/osv.vmx build/release.x64/osv-esx.ova > > > > Opening VMX source: build/release.x64/osv.vmx > > > > Warning: > > > > - Unsupported device backing for device 'serial0'. > > > > Opening OVA target: build/release.x64/osv-esx.ova > > > > Writing OVA package: build/release.x64/osv-esx.ova > > > > Transfer Completed > > > > Completed successfully > > > > > > > > When I import the OVA into my ESX and power it on nothing happens – no > > exceptions, no messages – all blank. At least in the past I got some kind > > of stacktrace, etc…. I noticed that recently some changes were made to the > > vmxnet3.cc file, so maybe that’s the reason… > > > > > > > > Strangely enough, the Vmware Workstation works just fine with the > > same VMDK / VMX files – only when I try to package them into an OVA and > > import into an ESX does this blank occur. How can I proceed ? If you want, > > I can post the OVA/VMX/VMDK somewhere for you download and try to analyze > > what is going on… > > > > > > > > Thanks, > > > > Lyor -- You received this message because you are subscribed to the Google Groups "OSv Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
