Check http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/block-device-mapping-concepts.html especially the diagram under "Example Block Device Mapping" it explains the difference in naming.
On 31 October 2016 at 15:24, Tom Wu <[email protected]> wrote: > Thanks for helping! >> > > The problem has been resolved, after removing virtual_name > <https://www.packer.io/docs/builders/amazon-ebs.html#virtual_name> , I am > able to see xvdl 202:176 0 100G 0 disk > > lsblk > NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT > xvda 202:0 0 10G 0 disk > ├─xvda1 202:1 0 1M 0 part > └─xvda2 202:2 0 10G 0 part / > xvdf 202:80 0 6G 0 disk > └─xvdf1 202:81 0 6G 0 part /home > xvdg 202:96 0 6G 0 disk > └─xvdg1 202:97 0 6G 0 part /var > xvdh 202:112 0 1G 0 disk > └─xvdh1 202:113 0 1023M 0 part /var/log > xvdi 202:128 0 1G 0 disk > └─xvdi1 202:129 0 1023M 0 part /var/log/audit > xvdj 202:144 0 1G 0 disk > └─xvdj1 202:145 0 1023M 0 part /var/tmp > xvdl 202:176 0 100G 0 disk > > > Here is current config looks like > > "ami_block_device_mappings": [ > { > "device_name": "/dev/xvdl", > "volume_size": 100, > "volume_type": "gp2", > "delete_on_termination": true > } > ], > "launch_block_device_mappings": [ > { > "device_name": "/dev/xvdl", > "volume_size": 100, > "volume_type": "gp2", > "delete_on_termination": true > } > ], > > According to AWS doc, > > *VirtualName* (request), *virtualName* (response) > > The virtual device name (ephemeralN). Instance store volumes are numbered > starting from 0. An instance type with 2 available instance store volumes > can specify mappings for ephemeral0 and ephemeral1.The number of > available instance store volumes depends on the instance type. After you > connect to the instance, you must mount the volume. > > Constraints: For M3 instances, you must specify instance store volumes in > the block device mapping for the instance. When you launch an M3 instance, > we ignore any instance store volumes specified in the block device mapping > for the AMI. > > Type: String > > Required: No > > However it would be nice for someone to help me understand why it behaves > this way. > > -- > 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 [email protected]. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/packer-tool/3577a6fd-dbc6-4732-8451-d3f25425a004%40googlegroups.com > <https://groups.google.com/d/msgid/packer-tool/3577a6fd-dbc6-4732-8451-d3f25425a004%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/CALz9Rt_3%3DR4-BkP5q3%2BE%2BLSNvxgxjoW7Xbh3i15w%2BAQkXk614w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
