[
https://issues.apache.org/jira/browse/JCLOUDS-889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14506642#comment-14506642
]
Alex Heneveld commented on JCLOUDS-889:
---------------------------------------
This looks like a bug in `EC2HardwareBuilder`. It sets the default required
virtualization type for instance types to be "windows or PV". However the
current generation types no longer all support PV; HVM is preferred. Because
virt type is wrong on several new instance types, jclouds finds a PV image
which is not compatible. If virt type were set correctly to HVM it looks like
that would fix it, jclouds would look for HVM images which are compatible.
For details of virt support see:
http://aws.amazon.com/amazon-linux-ami/instance-type-matrix/
and
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/virtualization_types.html
> listImages don't consider `hvm` vs `paravirtual`
> ------------------------------------------------
>
> Key: JCLOUDS-889
> URL: https://issues.apache.org/jira/browse/JCLOUDS-889
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-compute
> Affects Versions: 1.9.0
> Reporter: Andrea Turli
>
> the node creation fails if one only specifies `osFamily` and `minRam=8G`
> (which triggers the creation of a large instance type) as `hvm` is an
> implicit requirement not satisfied by the templateBuilder
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
