Comment 6 for bug 1350224

Reviewed: https://review.openstack.org/128508
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=264425678fd4a37618c2bceae8e62f6bba778223
Submitter: Jenkins
Branch: master

commit 264425678fd4a37618c2bceae8e62f6bba778223
Author: Thang Pham <email address hidden>
Date: Tue Oct 14 23:24:54 2014 -0400

    VMware: Accept image and block device mappings

    The logic in spawn ignores the specified image if there
    are block device mappings in "nova boot". This is incorrect
    and is a bug in the VMware driver, since the block devices
    can be blank volumes. We should be able to accept an image
    and block device mappings in "nova boot".

    DocImpact: VMware supports nova boot with the --block-device
    option. End users can specify the block device's bus to be
    either lsiLogic, busLogic, ide, lsiLogicsas, or paraVirtual.
    For example, nova boot --flavor m1.tiny --block-device
    source=image,dest=volume,size=1,id=<image_id>,bus=lsiLogicsas,
    bootindex=0 test

    Change-Id: Ibf59906b95bda560d2427c88a78b65c098825959
    Closes-Bug: #1350224
    Closes-Bug: #1271966