Re: qemu option parsing error.

Dan Kenigsberg
2007-11-10T22:30:54Z

On Sat, Nov 10, 2007 at 01:22:06PM -0500, John Clemens wrote:
> It appears the qemu in KVM-51 has a weird glitch where it will ignore
> the '-m' memory parameter if it's the first parameter on the command
> line (the case 'QEMU_OPTION_m' stanza never gets called in
> qemu/hw/vl.c:main()). A quick look at the code doesn't reveal anything
> obvious to me as to why. Putting some other parameter first (like
> '-hda') works just fine. This doesn't happen with the current qemu
> cvs.
>
> i.e.:
>
> qemu-system-x86_64 -m 512 -hda test.img == 128MB ram in VM.
> qemu-system-x86_64 -hda test.img -m 512 == 512MB ram in VM.
>

I failed to reproduce this on my system (but I could not try if with the
exact same params). What's your host? What happens when you pass an
absurdly large memory size?

I get
$ ./qemu-system-x86_64 -m 4000 -hda /images/fc6.img
kvm_alloc_userspace_memory: Cannot allocate memoryCould not create KVM context

Dan.