[Bug 1759509] Re: [19.10][qemu] virsh dompmwakeup fails to wake VM from dompmsuspend state (kvm)

2019-06-12 Thread Frank Heimes
** 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/1759509

Title:
  [19.10][qemu] virsh dompmwakeup fails to wake VM from dompmsuspend
  state (kvm)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1759509/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1759509] Re: [19.10][qemu] virsh dompmwakeup fails to wake VM from dompmsuspend state (kvm)

2019-06-12 Thread Launchpad Bug Tracker
This bug was fixed in the package libvirt - 5.4.0-0ubuntu1

---
libvirt (5.4.0-0ubuntu1) eoan; urgency=medium

  * Merged with Debian git 5.3.0-1~1.gbp7b1637 and upstreams 5.4 release
Among many other new features and fixes this includes fixes for:
LP: #1759509 - virsh dompmwakeup fails to wake VM from dompmsuspend state
Remaining changes:
- Disable libssh2 support (universe dependency)
- Disable firewalld support (universe dependency)
- Set qemu-group to kvm (for compat with older ubuntu)
- Additional apport package-hook
- Autostart default bridged network (As upstream does, but not Debian).
  In addition to just enabling it our solution provides:
  + do not autostart if subnet is already taken (e.g. in guests).
  + iterate some alternative subnets before giving up
- d/p/ubuntu/Allow-libvirt-group-to-access-the-socket.patch: This is
  the group based access to libvirt functions as it was used in Ubuntu
  for quite long.
  + d/p/ubuntu/daemon-augeas-fix-expected.patch fix some related tests
due to the group access change.
  + d/libvirt-daemon-system.postinst: add users in sudo to the libvirt
group.
- ubuntu/parallel-shutdown.patch: set parallel shutdown by default.
- Update Vcs-Git and Vcs-Browser fields to point to launchpad
- Xen related
  - d/p/ubuntu/ubuntu-libxl-qemu-path.patch: this change was split. The
section that adapts the path of the emulator to the Debian/Ubuntu
packaging is kept.
  - d/p/ubuntu/ubuntu-libxl-Fix-up-VRAM-to-minimum-requirements.patch: auto
set VRAM to minimum requirements
  - d/p/ubuntu/xen-default-uri.patch: set default URI on xen hosts
  - Add libxl log directory
  - libvirt-uri.sh: Automatically switch default libvirt URI for users on
Xen dom0 via user profile (was missing on changelogs before)
- d/p/ubuntu/apibuild-skip-libvirt-common.h: drop libvirt-common.h from
  included_files to avoid build failures due to duplicate definitions.
- Update README.Debian with Ubuntu changes
- Enable some additional features on ppc64el and s390x (for arch parity)
  + systemtap, zfs, numa and numad on s390x.
  + systemtap on ppc64el.
- d/t/control, d/t/smoke-qemu-session: fixup smoke-qemu-session by making
  vmlinuz available and accessible (Debian bug 848314)
- d/t/control, d/t/smoke-lxc: fix up lxc smoke test isolation
- d/p/ubuntu/ubuntu_machine_type.patch: accept ubuntu types as pci440fx
- Further upstreamed apparmor Delta, especially any new one
  Our former delta is split into logical pieces and is either Ubuntu only
  or is part of a continuous upstreaming effort.
  Listing related remaining changes in debian/patches/ubuntu-aa/:
  + 0001-apparmor-Allow-pygrub-to-run-on-Debian-Ubuntu.patch: apparmor:
Allow pygrub to run on Debian/Ubuntu
  + 0003-apparmor-libvirt-qemu-Allow-read-access-to-overcommi.patch:
apparmor, libvirt-qemu: Allow read access to overcommit_memory
  + 0007-apparmor-libvirt-qemu-Allow-owner-read-access-to-PRO.patch:
apparmor, libvirt-qemu: Allow owner read access to @{PROC}/*/auxv
  + 0017-apparmor-virt-aa-helper-Allow-access-to-tmp-director.patch:
apparmor, virt-aa-helper: Allow access to tmp directories
  + ubuntu-aa/0020-virt-aa-helper-ubuntu-storage-paths.patch:
apparmor, virt-aa-helper: Allow various storage pools and image
locations
  + 0021-apparmor-virt-aa-helper-Add-openvswitch-support.patch:
apparmor, virt-aa-helper: Add openvswitch support
  + 0029-appmor-libvirt-qemu-Add-9p-support.patch: appmor,
libvirt-qemu: Add 9p support
  + 0030-virt-aa-helper-Complete-9p-support.patch: virt-aa-helper:
add l to 9p file options.
  + 0031-virt-aa-helper-Ask-for-no-deny-rule-for-readonly-dis.patch:
virt-aa-helper: Ask for no deny rule for readonly disk (renamed and
reworded, was virt-aa-helper-no-explicity-deny-for-basefiles.patch)
  + 0032-apparmor-libvirt-qemu-Allow-reading-charm-specific-c.patch:
apparmor, libvirt-qemu: Allow reading charm-specific ceph config
  + 0033-UBUNTU-only-apparmor-for-kvm.powerpc-LP-1680384.patch: allow
commands executed by ubuntu only kvm wrapper on ppc64el
(LP 1686621 LP 1680384 LP 1784023)
  + 0034-apparmor-virt-aa-helper-access-for-snapped-nova.patch:
apparmor, virt-aa-helper: access for snapped nova
  + d/p/ubuntu-aa/0050-local-include-for-libvirt-qemu.patch,
d/libvirt-daemon-system.postinst: provide a local apparmor include
for abstraction/libvirt-qemu (LP: 1786019)
  + d/p/ubuntu-aa/lp-1815910-allow-vhost-net.patch: avoid apparmor issues
with vhost-net/vhost-vsock/vhost-scsi hotplug (LP: 1815910)
- d/rules: enable build time self tests on all architectures
- dnsmasq related enhancements
  + run dnsmasq as 

[Bug 1759509] Re: [19.10][qemu] virsh dompmwakeup fails to wake VM from dompmsuspend state (kvm)

2019-06-07 Thread Christian Ehrhardt 
** Changed in: libvirt (Ubuntu)
   Status: Confirmed => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759509

Title:
  [19.10][qemu] virsh dompmwakeup fails to wake VM from dompmsuspend
  state (kvm)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1759509/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1759509] Re: [19.10][qemu] virsh dompmwakeup fails to wake VM from dompmsuspend state (kvm)

2019-05-13 Thread Andrew Cloke
Status update: qemu patches now released. Libvirt patches are targeted
for release in 19.10.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759509

Title:
  [19.10][qemu] virsh dompmwakeup fails to wake VM from dompmsuspend
  state (kvm)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1759509/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1759509] Re: [19.10][qemu] virsh dompmwakeup fails to wake VM from dompmsuspend state (kvm)

2019-05-06 Thread Manoj Iyer
** Summary changed:

- [18.10][qemu] virsh dompmwakeup fails to wake VM from dompmsuspend state (kvm)
+ [19.10][qemu] virsh dompmwakeup fails to wake VM from dompmsuspend state (kvm)

** Changed in: libvirt (Ubuntu)
Milestone: None => ubuntu-19.10

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759509

Title:
  [19.10][qemu] virsh dompmwakeup fails to wake VM from dompmsuspend
  state (kvm)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1759509/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs