Hi,
that is upstream commit [1].
I thank you for the report but this only makes a fatal error a nice-error-msg
error.
It will be nice to pick this up with the next release of qemu, but that will be
a no-op when we merge the new version for 18.04.
IMHO this is:
- bad user input leads to error (well that is normal right)
- not unbreaking a use case (one still gets an error, just a nicer one after
the fix)
Therefore I'd consider this not important enough for any backport, but instead
would track it as low prio task for the next release.
Please feel free to discuss if you disagree with that assessment.
[1]:
https://git.qemu.org/?p=qemu.git;a=commit;h=c0dd10991903c552811d8cbe9231055b1b3a7ebd
** Changed in: qemu (Ubuntu)
Status: New => Confirmed
** Changed in: qemu (Ubuntu)
Importance: Undecided => Low
** Summary changed:
- [Ubuntu17.10] qemu gets a trap when given a negative number to 'maxcpus'
argument
+ [Ubuntu18.04] qemu gets a trap when given a negative number to 'maxcpus'
argument
** Tags added: qemu-18.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1722495
Title:
[Ubuntu18.04] qemu gets a trap when given a negative number to
'maxcpus' argument
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1722495/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
