[BUILDER][VMWARE-ISO] Virtual hardware version stuck to 11

376 views
Skip to first unread message

Jean-François FILIPPI

unread,
Nov 10, 2016, 4:04:45 AM11/10/16
to Packer
Hi,

I'm currently using Packer 0.10.2 (on Windows 7 x64).

Running a vmware-iso builder (on a VMware Workstation 10) with those parameters :

    {
     
"boot_command": [
       
"<esc><wait>",
       
"auto url=http://some-ip/preseed.cfg <wait>",
       
"<enter><wait>"
     
],
     
"iso_checksum": "{{user `iso_checksum`}}",
     
"iso_checksum_type": "{{user `iso_checksum_type`}}",
     
"iso_url": "{{user `iso_url`}}",
     
"ssh_password": "{{user `ssh_password`}}",
     
"ssh_username": "root",
     
"ssh_port": "{{user `ssh_port`}}",
     
"ssh_wait_timeout": "10000s",
     
"type": "vmware-iso",
     
"disk_size": "{{user `disk_size`}}",
     
"disk_type_id": 0,
     
"vmx_data": {
       
"cpuid.coresPerSocket": "1",
       
"memsize": "{{user `memory`}}",
       
"numvcpus": "{{user `core`}}"
     
},
     
"guest_os_type": "debian7-64",
     
"output_directory": "{{user `path`}}",
     
"vmdk_name": "{{user `vm_name`}}",
     
"vm_name": "{{user `vm_name`}}",
     
"shutdown_command": "shutdown -P now",
     
"version": "9"
   
}

and with some provisioning outputs a working virtual machine. Except when I'm exporting it to an OVF, then importing to another computer, the virtualhw.version is set to 11 even though I specified as 9 in the building phase, which should be the default value according to the documentation.
 
Before using packer all my manually-built virtual machines were rightly exported with a virtualhw.version of 9. Is this a (known) bug ? Did I mistakenly configured my builder ?

Thanks a lot

Jeff.

Rickard von Essen

unread,
Nov 10, 2016, 9:34:28 AM11/10/16
to packe...@googlegroups.com

virtualhw.version is a VMware specific thing, I doubt that OVF (which is a standard) supports it. The simplest way to check this is probably unpacking the ovf and check if the metadata contains this. If not I guess when VMware imports the ovf it defaults to version 11.


--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/66796bb8-07e5-4c4c-8ba6-12c830c1cc32%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jean-François FILIPPI

unread,
Nov 17, 2016, 3:23:24 AM11/17/16
to packe...@googlegroups.com
Using
"vmx_data": {
  "virtualHW.version": "10"
}

solved my issue. Exporting the OVF sets correctly a virtualhw.version = 10 which is compatible with my workstation out of the box.

Thanks for your help Rickard.

Jeff.

You received this message because you are subscribed to a topic in the Google Groups "Packer" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/packer-tool/KOqqRETpps4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to packer-tool+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/CALz9Rt86xmzRwFZ9rTq%2Bty9h25Zxj-wZRkOtd%2BpCCYjHBDcF5Q%40mail.gmail.com.
Reply all
Reply to author
Forward
0 new messages