Hide Forgot
Description of problem: no prompting for required information when use virt-image --prompt to create guest from xml file Version-Release number of selected component (if applicable): python-virtinst-0.500.5-3.el6.noarch How reproducible: always Steps to Reproduce: 1.remove all guest,run command: # virt-image --prompt virt-image.xml there is no prompting for required. strangely, if a same name domain exist, [root@localhost tmp]# virsh list --all Id Name State ---------------------------------- 1 rhel6_x86_64_qcow2 running 2 test running 3 new running then run command: [root@localhost tmp]# virt-image --prompt virt-image.xml ERROR Guest name 'test' is already in use. What is the name of your virtual machine? new Creating guest new... Creating domain... the prompting will shown up. i check man help and --help of virt-image, all missing --prompt option detail,but --force exist. Actual results: Expected results: Additional info:
Rather than adding --prompting, we should just hide the option until there is something reasonable to prompt for.
Upstream now hides both --prompt and --force options, and doesn't have the weird prompting behavior you mention above. Truthfully the --prompt behavior is a pain to maintain so it will probably never be fully implemented for virt-image.
Fixed in python-virtinst-0.600.0-1.el6
verify with: python-virtinst-0.600.0-1.el6.noarch libvirt-0.9.4-0rc1.el6.x86_64 qemu-kvm-0.12.1.2-2.172.el6.x86_64 step: #virsh list --all Id Name State ---------------------------------- 7 demo running 20 test running #cat image.xml <image> <name>test</name> <domain> <boot type="hvm"> <guest> <arch>x86_64</arch> </guest> <os> ... #virt-image --prompt image.xml ERROR Guest name 'test' is already in use. no prompt shown up. verification passed.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: No description necessary
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2011-1643.html