Hi Avi, On Sun, 2011-11-06 at 12:23 +0200, Avi Kivity wrote: > > If this is a serious attempt in making QEMU command line suck less on > > Linux, I think it makes sense to do this properly instead of adding a > > niche script to the kernel tree that's simply going to bit rot over > > time. > > You misunderstand. This is an attempt to address the requirements of a > niche population, kernel developers and testers, not to improve the qemu > command line. For the majority of qemu installations, this script is > useless. Right. On Sun, 2011-11-06 at 12:23 +0200, Avi Kivity wrote: > In most installations, qemu is driven by other programs, so any changes > to the command line would be invisible, except insofar as they break things. > > For the occasional direct user of qemu, something like 'qemu-kvm -m 1G > /images/blah.img' is enough to boot an image. This script doesn't help > in any way. > > This script is for kernel developers who don't want to bother with > setting up a disk image (which, btw, many are still required to do - I'm > guessing most kernel developers who use qemu are cross-arch). It has > limited scope and works mostly by hiding qemu features. As such it > doesn't belong in qemu. I'm certainly not against merging the script if people are actually using it and it solves their problem. I personally find the whole exercise pointless because it's not attempting to solve any of the fundamental issues QEMU command line interface has nor does it try to make Linux on Linux virtualization simpler and more integrated. People seem to think the KVM tool is only about solving a specific problem to kernel developers. That's certainly never been my goal as I do lots of userspace programming as well. The end game for me is to replace QEMU/VirtualBox for Linux on Linux virtualization for my day to day purposes. Pekka -- 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
