Lucas Bajolet

Hi @hegyre, The Block Device Mapping being referenced here is likely referring to the [AWS docs on device mapping](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/block-device-mapping-concepts.html). From what I gather, `virtual_name` is only for instance-based (ephemeral) volumes,...

Hi @steffakasid, Thanks for reporting this, since this concerns the Amazon plugin, I'll transfer it over there. Unfortunately, I can't promise we'll fix this soon as we have other priorities...

Hi @glachac-safelishare, Good call, the issue was automatically closed when we merged the PR for the other builders, I agree though that it would be good for EBS to support...

Hi @eamonnlambda, Unfortunately there's no changes on the AWS API that allow us to add this attribute to the commons without changing how we publish the AMI, since the `ebs`...

And this right here is why we're cautious about bringing about those changes. Thanks @lorengordon for the heads-up, that would have never crossed my mind for sure.

Hi @djmetzle, This may be a good addition indeed! This wouldn't be too hard to implement as well, so I figure this would be well suited for a first contribution....

Hi @teddylear, This looks like a good improvement for the plugin indeed! I've looked into the problem, and I fear that it may not be too trivial to implement at...

Hi @anoopsaxena, From what I can see in the logs, this is mostly because of a permission issue that the build fails. If you are using `chroot`, this means that...

Hi @lindhe, Thanks for the bug report! While this `Unexpected EOF` which caused Packer to crash is coming from the SDK (likely even gob), the underlying problem is coming from...

I'll add my 2 cents here, why do we do this check exactly? Is there a valid use case to building an image on VSphere without a communicator at all,...