[Bug 1722495] Re: [Ubuntu18.04] qemu gets a trap when given a negative number to 'maxcpus' argument

2018-02-12 Thread Manoj Iyer
** Changed in: ubuntu-power-systems
   Status: Confirmed => Fix Released

-- 
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

[Bug 1722495] Re: [Ubuntu18.04] qemu gets a trap when given a negative number to 'maxcpus' argument

2018-02-08 Thread Launchpad Bug Tracker
This bug was fixed in the package qemu - 1:2.11+dfsg-1ubuntu1

---
qemu (1:2.11+dfsg-1ubuntu1) bionic; urgency=medium

  * Merge with Debian testing, among other fixes this includes
- fix fatal error on negative maxcpus (LP: #1722495)
- fix segfault on dump-guest-memory on guests without memory (LP: #1723381)
- linux user threading issues (LP: #1350435)
- TOD-Clock Epoch Extension Support on s390x (LP: #1732691)
Remaining changes:
- qemu-kvm to systemd unit
  - d/qemu-kvm-init: script for QEMU KVM preparation modules, ksm,
hugepages and architecture specifics
  - d/qemu-kvm.service: systemd unit to call qemu-kvm-init
  - d/qemu-system-common.install: install systemd unit and helper script
  - d/qemu-system-common.maintscript: clean old sysv and upstart scripts
  - d/qemu-system-common.qemu-kvm.default: defaults for
/etc/default/qemu-kvm
  - d/rules: install /etc/default/qemu-kvm
- Enable nesting by default
  - set nested=1 module option on intel. (is default on amd)
  - re-load kvm_intel.ko if it was loaded without nested=1
  - d/p/ubuntu/expose-vmx_qemu64cpu.patch: expose nested kvm by default
in qemu64 cpu type.
  - d/p/ubuntu/enable-svm-by-default.patch: Enable nested svm by default
in qemu64 on amd
- libvirt/qemu user/group support
  - qemu-system-common.postinst: remove acl placed by udev, and add udevadm
trigger.
  - qemu-system-common.preinst: add kvm group if needed
- Distribution specific machine type
  - d/p/ubuntu/define-ubuntu-machine-types.patch: define distro machine
types to ease future live vm migration.
  - d/qemu-system-x86.NEWS Info on fixed machine type defintions
- improved dependencies
  - Make qemu-system-common depend on qemu-block-extra
  - Make qemu-utils depend on qemu-block-extra
  - let qemu-utils recommend sharutils
- s390x support
  - Create qemu-system-s390x package
  - Include s390-ccw.img firmware
  - Enable numa support for s390x
- ppc64[le] support
  - d/qemu-system-ppc.links provide usr/bin/qemu-system-ppc64le symlink
- arch aware kvm wrappers
  * Added Changes
- update VCS-git to match the bionic branch
- sdl2 is yet too unstable for the LTS Ubuntu release given the reports
  we still see upstream and in Debian - furthermore sdl2 isn't in main yet,
  so we revert related changes to stick with the proven for now:
  - 0fd25810 - do not build-depend on libx11-dev (libsdl2-dev already
   depends on it)
  - 9594f820 - switch from sdl1.2 to sdl2 (#870025)
- d/qemu-system-x86.README.Debian: document intention of nested being
  default is comfort, not full support
- update Ubuntu machine types for qemu 2.11
- qemu-guest-agent: freeze-hook fixes (LP: #1484990)
  - d/p/guest-agent-freeze-hook-skip-dpkg-artifacts.patch
  - d/qemu-guest-agent.install: provide /etc/qemu/fsfreeze-hook
  - d/qemu-guest-agent.dirs: provide /etc/qemu/fsfreeze-hook.d
- Create and install pxe netboot images for KVM s390x (LP: #1732094)
  - d/rules enable install s390x-netboot.img
  - debian/patches/ubuntu/partial-SLOF-for-s390x-netboot-compilation.patch
- d/control-in: enable RDMA support in qemu (LP: #1692476)
- on s390x provide facility bits 81 (ppa15) and 82 (bpb) (LP: #1743560)
  - d/p/ubuntu/linux-headers-update-to-4.15-rc1.patch
  - d/p/ubuntu/linux-headers-update-4.15-rc9.patch
  - d/p/ubuntu/lp1743560-s390x-kvm-Handle-bpb-feature.patch
  - d/p/ubuntu/lp1743560-s390x-kvm-provide-stfle.81.patch
- tolerate ipxe size change on migrations to >=18.04 (LP: #1713490)
  - d/p/ubuntu/pre-bionic-256k-ipxe-efi-roms.patch: old machine types
reference 256k path
  - d/control: depend on ipxe-qemu-256k-compat-efi-roms to be able to
handle incoming migrations from former releases.
- d/control-in: enable seccomp on s390x
  * Dropped changes (no more needed):
- Dropped VHOST_NET_ENABLED and KVM_HUGEPAGES from /etc/default/qemu-kvm
  The functionality is retained for upgraders, but is deprecated.
  Post 18.04 the implementation for these configurations will be removed.
  * Dropped changes (in Debian now):
- ppc64[le] support
  - Enable seccomp for ppc64el
  - bump libseccomp-dev dependency, 2.3 is the minimum for ppc64
- disable missing x32 architecture
- d/rules: or32 is now named or1k (since 4a09d0bb)
- d/qemu-system-common.docs: new paths since (ac06724a)
- d/qemu-system-common.install: qmp-commands.txt removed, but replaced
  by qapi-schema.json which is already packaged (since 4d8bb958)
- d/p/02_kfreebsd.patch: utimensat is no more optional upstream (Update
  to Debian patch to match qemu 2.10)
- d/qemu-system-common.docs: adapt new path of live-block-operations.rst
  since 8508eee7
- d/qemu-system-common.docs: adapt q35 

[Bug 1722495] Re: [Ubuntu18.04] qemu gets a trap when given a negative number to 'maxcpus' argument

2018-02-08 Thread ChristianEhrhardt
qemu 2.11 is in proposed

** Changed in: qemu (Ubuntu)
   Status: Confirmed => Fix Committed

-- 
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

[Bug 1722495] Re: [Ubuntu18.04] qemu gets a trap when given a negative number to 'maxcpus' argument

2017-12-18 Thread Andrew Cloke
** Changed in: ubuntu-power-systems
   Importance: Medium => Low

-- 
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

[Bug 1722495] Re: [Ubuntu18.04] qemu gets a trap when given a negative number to 'maxcpus' argument

2017-11-21 Thread bugproxy
** Tags removed: targetmilestone-inin1710
** Tags added: targetmilestone-inin1804

-- 
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

[Bug 1722495] Re: [Ubuntu18.04] qemu gets a trap when given a negative number to 'maxcpus' argument

2017-11-20 Thread ChristianEhrhardt
Grabbing the qemu task, but as I said in comment #1 - not urgent on next
merge.

** Changed in: qemu (Ubuntu)
 Assignee: David Britton (davidpbritton) => ChristianEhrhardt (paelzer)

-- 
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

[Bug 1722495] Re: [Ubuntu18.04] qemu gets a trap when given a negative number to 'maxcpus' argument

2017-11-20 Thread Manoj Iyer
** Changed in: qemu (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
David Britton (davidpbritton)

** Changed in: ubuntu-power-systems
 Assignee: Canonical Server Team (canonical-server) => David Britton 
(davidpbritton)

-- 
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

[Bug 1722495] Re: [Ubuntu18.04] qemu gets a trap when given a negative number to 'maxcpus' argument

2017-10-16 Thread Manoj Iyer
** Tags added: triage-g

-- 
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

[Bug 1722495] Re: [Ubuntu18.04] qemu gets a trap when given a negative number to 'maxcpus' argument

2017-10-11 Thread Frank Heimes
** Changed in: ubuntu-power-systems
   Status: New => Confirmed

-- 
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