On Fri, 2007-08-31 at 22:13 +0200, [EMAIL PROTECTED] wrote: > Hi Anthony, > > I think passing only the directory name is better because it can be like a > "black box" : the user don't have to know how it is inside. And it is much > more simple to use "qemu my_pc" than "qemu -c my_pc/config".
You're overriding what "qemu my_pc" means. "qemu my_pc" create a QEMU vm with 128m of memory and -hda my_pc with the default network card. "qemu -c my_pc/config" only has one meaning: read command line arguments from "my_pc/config". Your suggested syntax may be simpler for your particular use-case, but it makes QEMU much more difficult to understand for every other user. Regards, Anthony Liguori > Regards, > Laurent > > ------------------------------------------------------ > Pour : Jorge Lucángeli Obes <[EMAIL PROTECTED]> > cc : [EMAIL PROTECTED], qemu-devel@nongnu.org > ccc : > Objet : Re: [kvm-devel] [PATCH][RFC] Allowing QEMU to directly > execute a directory (and storing command line options in it) > Anthony Liguori <[EMAIL PROTECTED]> > Envoyé par : [EMAIL PROTECTED] > 31/08/2007 13:54 EST > <font size=-1></font> > > > > > > > > > > > > > > > > > > > > It makes little sense to pass a directory when you can pass a config > file and assume that the directory the config file is in is the CWD. > > For instance, if vm.cfg contained just the command line arguments, you > could have: > > MyImage/vm.cfg: -hda disk0.qcow -m 512 > MyImage/disk0.qcow: <disk image> > > And then do: > > qemu -c MyImage/vm.cfg > > > > > >
