[Bug 1874647] Re: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures
** Changed in: ubuntu-z-systems Status: Fix Committed => 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/1874647 Title: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874647] Re: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures
This bug was fixed in the package libvirt - 6.0.0-0ubuntu8.4 --- libvirt (6.0.0-0ubuntu8.4) focal; urgency=medium * avoid stale libvirt capability cache (LP: #1874647) - when host cpu changes (e.g. nested with different configuration) - when s390x protvirt or AMD SEV changes - d/p/ubuntu/lp-1874647-* -- Christian Ehrhardt Mon, 31 Aug 2020 08:41:25 +0200 ** Changed in: libvirt (Ubuntu Focal) Status: Fix Committed => 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/1874647 Title: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1874647] Re: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures
On Wed, Sep 23, 2020 at 4:05 AM Chris Halse Rogers <1874...@bugs.launchpad.net> wrote: > > This looks like it should be ready for release into focal-updates, but > it's unclear to me whether anyone has tested the packages currently in > focal-proposed? Hi Chris, I did test the x86 part of it. AFAIK the s390x part was only tested on the PPA, but I'm unsure if we can expect them to be tested twice without actively pinging/polling for it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874647 Title: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874647] Re: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures
This looks like it should be ready for release into focal-updates, but it's unclear to me whether anyone has tested the packages currently in focal-proposed? I see that some PPA packages have been tested and confirmed to work, but for SRUs we generally require that the actual packages that will end up in -updates (ie: the packages in -proposed) be tested. This is to avoid human error where the packages in a PPA are not exactly the same code as that in -proposed, and also to avoid the rare cases where some quirk of the build environment causes PPA builds to build correctly but the archive packages to fail. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874647 Title: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874647] Re: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures
All tests should be resolved by now reaching their former result state -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874647 Title: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874647] Re: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures
It seems vorlon already retried two of the three cases. One recovered, one did not. Still an indication that it is at least flaky ... :-/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874647 Title: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874647] Re: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures
@Boris - while not strictly required if you have the test system still around testing also the version in -proposed as well would be awesome. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874647 Title: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874647] Re: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures
The three test issues on armhf all seemed to be from the test environment, but not the involved components. For now I just restarted them as-is ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874647 Title: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874647] Re: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures
Thank you Brian, IBM just did the s390x specific eval on the equivalent build from the PPA - no need to redo all of this. I was running a regression test and the tests I was doing before in comment #17 again. They behaved the same as with my PPA tests which is (combined with the IBM tests on protvirt) enough confirmation on this. Setting verified tags on this, yet we need to still sort out the off autopkgtest issues that we hit... ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874647 Title: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874647] Re: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures
** Changed in: ubuntu-z-systems Status: In Progress => 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/1874647 Title: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874647] Re: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures
Hello bugproxy, or anyone else affected, Accepted libvirt into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libvirt/6.0.0-0ubuntu8.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libvirt (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874647 Title: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874647] Re: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures
FYI - Re-uploaded since the first shot (while testing fine) had formally an incorrect format for referencing a Launchpad bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874647 Title: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874647] Re: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures
** Changed in: ubuntu-z-systems Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874647 Title: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874647] Re: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures
MP is also reviewed, this is uploaded for an SRU. Once the SRU Team got to it it would be great to have IBM testing -proposed for this case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874647 Title: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874647] Re: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures
** Changed in: ubuntu-z-systems Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874647 Title: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874647] Re: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures
Test the test to be helpful: Run guest a defined model like: 23 24 SandyBridge-IBRS 25 Intel 26 In the guest check the cache file update time: $ sudo ls -laF /var/cache/libvirt/qemu/capabilities/ -rw--- 1 root root 75171 Sep 2 08:58 926803a9278e445ec919c2b6cbd8c1c449c75b26dcb1686b774314180376c725.xml -rw--- 1 root root 85376 Sep 2 08:58 f11008721aacc79c97e592178e61264d75be551864cd79cc41fe820e31262f27.xml $ virsh domcapabilities > dpre $ virsh capabilities > cpre $ head -n5 /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 42 model name : Intel Xeon E312xx (Sandy Bridge, IBRS update) Then shutdown and change that to IvyBridge-IBRS (similar but not the same) When again started it should refresh the cache, as the CPU changed. But without the fix it hasn't. While cpuinfo changed, the cache and results didn't. $ head -n5 /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 58 model name : Intel Xeon E3-12xx v2 (Ivy Bridge, IBRS) $ virsh domcapabilities > dpost $ virsh capabilities > cpost $ md5sum cp* dp* f0df917463798992d5842297fa039f86 cpost 4f214575cab864502576a0da1bceb031 cpre 94d6fe53ee5f9f6270e001788a225328 dpost 94d6fe53ee5f9f6270e001788a225328 dpre With the fix: -rw--- 1 root root 75171 Sep 2 09:04 926803a9278e445ec919c2b6cbd8c1c449c75b26dcb1686b774314180376c725.xml -rw--- 1 root root 85376 Sep 2 09:04 f11008721aacc79c97e592178e61264d75be551864cd79cc41fe820e31262f27.xml And after reboot into the other type we see the host section updated. $ md5sum cp* dp* 4f214575cab864502576a0da1bceb031 cpost f0df917463798992d5842297fa039f86 cpre 94d6fe53ee5f9f6270e001788a225328 dpost 94d6fe53ee5f9f6270e001788a225328 dpre -rw--- 1 root root 75171 Sep 2 09:04 926803a9278e445ec919c2b6cbd8c1c449c75b26dcb1686b774314180376c725.xml -rw--- 1 root root 85376 Sep 2 09:04 f11008721aacc79c97e592178e61264d75be551864cd79cc41fe820e31262f27.xml $ diff -Naur cpre cpost --- cpre2020-09-02 09:04:41.058583142 + +++ cpost 2020-09-02 09:05:50.65200 + @@ -4,10 +4,11 @@ 058268cb-6229-46c7-84f8-5cd8edac4c5d x86_64 - IvyBridge-IBRS + SandyBridge-IBRS Intel + There are more complex feature checks that might go deeper e.g. when actually starting a guest and deriving host-model. But this should be ok as a test of the area I hope. P.S. I've yet to see the "Outdated capabilities for '%s': host CPU changed" message in a debug log, maybe the tests needs to be further adapted for the specific case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874647 Title: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874647] Re: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures
** Changed in: libvirt (Ubuntu Groovy) Assignee: Christian Ehrhardt (paelzer) => (unassigned) ** Changed in: libvirt (Ubuntu Focal) Assignee: (unassigned) => Christian Ehrhardt (paelzer) ** Changed in: libvirt (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874647 Title: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874647] Re: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures
** Description changed: + [Impact] + + * capability caching by libvirt is required for efficiency, but +often stumbles over changes it misses to pick up and refresh + + * This backports several fixes to catch more of such situations +and refresh the caches in those cases +- AMD SEV changed +- s390x protvirt changed +- CPU changed + + * Backporting these changes + + [Test Case] + + * For AMS SEV and s390x protvirt you'd need the respective HW and +environments. Maybe IBM can test the latter then. +- For nested we can test it thou + 1. create a guest with host-model type + 2. install libvirt in the guest + 3. run "virsh capabilities" and save it to a file + 4. shut down guest + 5. edit the guest and take away some cpu features + 6. start guest again and run "virsh capabilities" again +It will still report these features as present (wrong) + +With the fix at #6 it will realize the CPU has changed and refresh the +capabilities cache. + + [Regression Potential] + + * This increases the amount of capability refreshes, the regression that +comes to mind is that if this contains false-positives it might trigger +too often and therefore slow down operations on systems where this +happens. +Functionally that would be no breakage, even not caching at all works +fine, but a performance issue. The added tests seem fine thou as a cpu +attribute has to change which isn't a high frequency event. + + [Other Info] + + * n/a + + --- + Stale libvirt cache leads to VM startup failures - - Contact Information = Viktor Mihajlovski - + + Contact Information = Viktor Mihajlovski + ---Additional Hardware Info--- - Z15 with IBM Secute Execution + Z15 with IBM Secute Execution - ---uname output--- Linux linux02 5.4.0-21-generic #25-Ubuntu SMP Sat Mar 28 13:10:00 UTC 2020 s390x s390x s390x GNU/Linux - - Machine Type = 8562 (IBM Z15) - + + Machine Type = 8562 (IBM Z15) + ---Debugger--- A debugger is not configured - + ---Steps to Reproduce--- 1. Install Ubuntu 20.04 in the LPAR 2. Modify the host kernel command line in /etc/zipl.conf to include prot_virt=1, run zipl and reboot. 3. Define at least one KVM guest with host CPU model and start and stop it 4. Define a secure KVM guest using the host CPU model and start and stop it. 5. Change back the host kernel command line, re-run zipl, reboot. 6. Try to start the first KVM guest, which fails with a message like: - error: internal error: qemu unexpectedly closed the monitor: 2020-04-23T13:55:30.889152Z qemu-system-s390x: Some features requested in the CPU model are not available in the configuration: unpack + error: internal error: qemu unexpectedly closed the monitor: 2020-04-23T13:55:30.889152Z qemu-system-s390x: Some features requested in the CPU model are not available in the configuration: unpack The reason for that is that libvirt caches the domaincapabilities reported during the first boot and doesn't update them after the reboot in step 5 even though changing the prot_virt= in the command line changes the CPU features as reported by domcapabilities. So even though the guest may not require the unpack feature, libvirt constructs a CPU model which can't be satisfied on this configuration. The issue also occurs the other way around, going from prot_virt=0 to prot_virt=1, in which case the guest will fail to boot as it requires the unpack feature. Manually removing the content of /var/cache/libvirt/qemu/capabilities/ will force libvirt to refresh it's capabilities cache and temporarily resolve the situation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874647 Title: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874647] Re: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures
This bug was fixed in the package libvirt - 6.6.0-1ubuntu2
---
libvirt (6.6.0-1ubuntu2) groovy; urgency=medium
* d/p/u/lp-1892826-Revert-m4-virt-xdr-rewrite-XDR-check.patch: avoid clashes
between libtripc and glibc that break libvirt-lxc (LP: #1892826)
* d/p/ubuntu-aa/lp-1892736-apparmor-allow-libvirtd-to-call-virtiofsd.patch:
allow libvirt to control virtiofsd (LP: #1892736)
libvirt (6.6.0-1ubuntu1) groovy; urgency=medium
* Merge with Debian 6.6.0-1 from experimental
Among many other new features and fixes this includes fixes for:
(LP: #1874647) - Stale libvirt cache leads to VM startup failures
(LP: #1869796) - bad ordering and dependent restarts of services/sockets
Remaining changes:
- d/p/ubuntu-aa/lp-1847361-load-versioned-module.patch: allow loading
versioned modules after qemu package upgrades (LP 1847361)
- libvirt-uri.sh: Automatically switch default libvirt URI for users
via user profile (xen URI on dom0, qemu:///system otherwise)
- 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 README.Debian with Ubuntu changes
- d/p/ubuntu/ubuntu_machine_type.patch: accept ubuntu types as pci440fx
- fix autopkgtests
+ d/t/control, d/t/smoke-qemu-session: fixup smoke-qemu-session by making
vmlinuz available and accessible (Debian bug 848314)
+ d/t/control: fix smoke-qemu-session by ensuring the service will run
installing libvirt-daemon-system
+ d/t/smoke-lxc: fix smoke-lxc by ignoring potential issues on destroy as
long as the following undefine succeeds
+ d/t/smoke-lxc: use systemd instead of sysV to restart the service
- dnsmasq related enhancements
+ run dnsmasq as libvirt-dnsmasq (LP: 1743718)
+ d/libvirt-daemon-system.postinst: add libvirt-dnsmasq user and group
+ d/libvirt-daemon-system.postrm: remove libvirt-dnsmasq user and group
on purge
+ d/p/ubuntu/dnsmasq-as-priv-user: write dnsmasq config with user
libvirt-dnsmasq and adapt the self tests to expect that config
+ d/libvirt-daemon-system.postinst: fix old libvirt-dnsmasq users group
+ Add dnsmasq configuration to work with system wide dnsmasq-base
- debian/rules: disable the netcf backend. (LP: 1764314)
- debian/patches/ubuntu/ovmf_paths.patch: adjust paths to secboot.fd UEFI
Secure Boot enabled variants of the OVMF firmware and variable store for
the paths where we ship these files in Ubuntu.
- d/p/ubuntu/set-default-machine-to-ubuntu.patch: to select default
machine type correctly with newer qemu/libvirt
- d/control: add libzfslinux-dev to build-deps
- d/control: drop libvirt-lxc, vbox and xen drivers to suggest
- d/p/ubuntu/lp-1861125-ubuntu-models: recognize Ubuntu models for
(LP 1861125) fixups
- Apparmor Delta that is Ubuntu specific or yet to be upstreamed
split into logical pieces. File names in debian/patches/ubuntu-aa/:
+ 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
+ 0020-virt-aa-helper-ubuntu-storage-paths.patch:
apparmor, virt-aa-helper: Allow various storage pools and image
locations
+ 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
[Bug 1874647] Re: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures
** Changed in: ubuntu-z-systems Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874647 Title: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874647] Re: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures
** Changed in: libvirt (Ubuntu Groovy) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874647 Title: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874647] Re: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures
See https://launchpad.net/ubuntu/+source/libvirt/6.6.0-1ubuntu1 And soon but not yet https://launchpad.net/ubuntu/+source/libvirt/6.6.0-1ubuntu2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874647 Title: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874647] Re: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures
Libvirt 6.6 contains the fix, but is stuck in groovy proposed for a while already. After a fix (that you also want for virtiofsd) and another issue around libtripc being resolved there will be a follow up upload that should resolve those two today and hopefully migrate to groovy-release soon after. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874647 Title: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874647] Re: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures
** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/libvirt/+git/libvirt/+merge/389531 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874647 Title: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874647] Re: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures
** Also affects: libvirt (Ubuntu Groovy) Importance: Medium Assignee: Christian Ehrhardt (paelzer) Status: Triaged ** Also affects: libvirt (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874647 Title: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874647] Re: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures
awesome, thanks Boris! I think I'm looking at making sure to catch these when merging libvirt for 20.10 and then we might take just the two commits for the initial bug into Focal. ** Tags added: libvirt-20.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874647 Title: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874647] Re: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures
** Changed in: ubuntu-z-systems Assignee: (unassigned) => Christian Ehrhardt (paelzer) ** Changed in: ubuntu-z-systems Status: Incomplete => Triaged ** Changed in: libvirt (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Christian Ehrhardt (paelzer) ** Changed in: ubuntu-z-systems Assignee: Christian Ehrhardt (paelzer) => Skipper Bug Screeners (skipper-screen-team) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874647 Title: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874647] Re: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures
Note: the referred path set didn't land yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874647 Title: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874647] Re: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures
(just for the records: "Bug 185971" in comment #7 is an IBM Bugzilla number, not a LP bug number, hence pointing with the automatic link generation to a wrong LP bug) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874647 Title: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874647] Re: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures
The case with the module parameter in SEV needs a fix similar to https://libvirt.org/git/?p=libvirt.git;a=commit;h=b183a75319b90d0af5512be513743e1eab950612 as it can be re-loaded at any time. Essentially the checks in virQEMUCapsLoadCache check qemu/kernel version and many other things. They also check microcode version ... I think the decision there can be two ways, either "on any reboot we need to refresh caps" which makes the code small but probably also wastes quite some refreshes that were not needed. Or it could along all the versions that it checks also keep a full string of /proc/cmdline and compare it. If changed it needs to be refreshed. I agree to Frank that this should be reported upstream. No matter if you or I write a fix, it needs to go upstream then - so a bug tracker there can't hurt. OTOH you can as well start right away with a RFC patch there if you have something prepared already - there is no "strict need" for an upstream bug, only if you hope someone there will fix it for you. Since workarounds are available the prio is medium IMHO, eager to see what upstream thinks. P.S. Even if you have no patch, it would be great if you (as the affected) would kick off the discussion upstream. Please provide a link here to the mailing list entry. ** Package changed: linux (Ubuntu) => libvirt (Ubuntu) ** Changed in: libvirt (Ubuntu) Status: New => Triaged ** Changed in: libvirt (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874647 Title: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874647] Re: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures
Was this problem already reported upstream and a fix made available? Btw. the latest (and wit that GA) kernel of 20.04 is: 5.4.0-26 ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Importance: Undecided => Medium ** Changed in: ubuntu-z-systems Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874647 Title: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
