Hi guys, I've noticed the following regression on qemu.git HEAD: VMCreateError: VM creation command failed: "/root/autotest/client/tests/kvm/qemu -name 'vm1' -monitor unix:'/tmp/monitor-humanmonitor1-20110119-083240-ocD9',server,nowait -serial unix:'/tmp/serial-20110119-083240-ocD9',server,nowait -drive file='/tmp/kvm_autotest_root/images/f14-64.qcow2',index=0,if=virtio,cache=none,boot=on device virtio-net-pci,netdev=idyBlEoF,mac='9a:52:ec:f7:49:f4' -netdev user,id=idyBlEoF,hostfwd=tcp::5000-:22,hostfwd=tcp::5001-:12323 -m 512 -smp 2 -drive file='/tmp/kvm_autotest_root/isos/linux/Fedora-14-x86_64-DVD.iso',media=cdrom,index=2 -drive file='/tmp/kvm_autotest_root/images/f14-64/ks.iso',media=cdrom,index=1 -kernel '/tmp/kvm_autotest_root/images/f14-64/vmlinuz' -initrd '/tmp/kvm_autotest_root/images/f14-64/initrd.img' -vnc :1 -boot d --append 'ks=cdrom nicdelay=60 console=ttyS0,115200 console=tty0'" (status: 1, output: 'Two devices with same boot index 0\n') I took the liberty of splitting up the qemu-kvm command line into blocks so I could verify the problem. So, after looking at the command line components, it is evident that kvm autotest constructed a valid, correct command line and somehow during the processing of the command line qemu-kvm thinks 2 devices have the same boot index, when in reality they don't. Please let's look into this. I am available for any further clarifications. Cheers! Lucas -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
