[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug 1707297] Re: qemu became more picky parsing -m option
From: |
Thomas Huth |
Subject: |
[Bug 1707297] Re: qemu became more picky parsing -m option |
Date: |
Sat, 26 Sep 2020 17:04:44 -0000 |
Looks like nobody cared to implement this within 3 years ... and IMHO
it's maybe even better to not overload the CLI syntax too much ... so
I'm closing this ticket now.
** Changed in: qemu
Status: New => Won't Fix
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1707297
Title:
qemu became more picky parsing -m option
Status in QEMU:
Won't Fix
Bug description:
With qemu-kvm-2.9.0-3.fc26.x86_64 I am no longer to specify the memory
size using something like "-m 1.00000GiB" but with qemu-
kvm-2.7.1-7.fc25.x86_64 I could without any problem. I now get an
error message like:
qemu-system-x86_64: -m 1.00000GiB: Parameter 'size' expects a non-negative
number below 2^64
Optional suffix k, M, G, T, P or E means kilo-, mega-, giga-, tera-, peta-
and exabytes, respectively.
Is this expected or a regression?
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1707297/+subscriptions
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Bug 1707297] Re: qemu became more picky parsing -m option,
Thomas Huth <=