vmware-iso builder, "keep_input_artifact": true, "No supported hardware versions"

62 views
Skip to first unread message

b...@tanners.org

unread,
Dec 13, 2017, 5:44:52 PM12/13/17
to Packer
Not sure if this is a packer issue, Virtualbox issue, or a VMware issue. Starting here with packer.

Creating images with packer 1.1.3 and have "keep_input_artifact": true.

I assumed the output-virtualbox-iso/*.ovf files would be something I could import into VMware 6.5 but trying to import the .ovf file vSphere throws an error:

        No supported hardware version among [virtualbox-2.2]; supported: [vmx-04,...,vmx-13]

Looking inside the .ovf

        <vssd:VirtualSystemType>virtualbox-2.2</vssd:VirtualSystemType>

Lots of stuff on Google about how to work around it. I'm looking for a fix.

Is the problem in packer?

My gut tells me the problem is in Virtualbox.

Any feedback would be appreciated.

Thanks.

Rickard von Essen

unread,
Dec 14, 2017, 12:32:36 AM12/14/17
to packe...@googlegroups.com
Packer doesn't manage the content of the ovf. 

--
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/bc617dd4-1789-4d87-9445-7e7158961e12%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Bob Tanner

unread,
Dec 14, 2017, 12:34:23 AM12/14/17
to packe...@googlegroups.com
Thanks for the quick response.

I’ll go talk with the Virtualbox people.

Alvaro Miranda Aguilera

unread,
Dec 14, 2017, 4:52:17 AM12/14/17
to packe...@googlegroups.com
hello

lets say you want to build with Virtualbox and then import on vmware, first question is, does this will be production at some point?


will vmware (since its a paid product) will support this?

if you really want to build in virtualbox and use in vmware, couple of options.

A. export an OVA from virtualbox, and conver to OVF with OVFTOOL (vmware tool)
B. copy the disk into a new disk vmdk, create a VM using that disk.

However, once packer build finish the build, from there is not a packer bug if you want to do cross hypervisor stuff

Thanks
Alvaro.

--
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/bc617dd4-1789-4d87-9445-7e7158961e12%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Alvaro

b...@tanners.org

unread,
Dec 14, 2017, 3:17:23 PM12/14/17
to Packer
7 year old bug tracked over at Virtualbox: https://www.virtualbox.org/ticket/7982

Some work arounds, a script, and changing export to 0.9, but honestly I think Virtualbox should apply the fix I suggest at the end of the post.
Reply all
Reply to author
Forward
0 new messages