[Bug 1896937] Re: Error with seclabel "apparmor" since upgrading from 18.04 to 20.04

2020-09-25 Thread Christian Ehrhardt
** Changed in: libvirt (Ubuntu) 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/1896937 Title: Error with seclabel "apparmor" since upgrading from 18.04 to 20.04 To

[Bug 1894879] Re: frequent crashes when using do-resolve()

2020-09-25 Thread Christian Ehrhardt
Hi David, your comment seems out of context here. If there is an issue I'd recommend filing a new bug for netplan and discussing things there, but if all you need is "Is it possible to run with the old net manager and focal" then look at [1]. [1]:

[Bug 1896740] Re: BIND crashes with failed assertion INSIST(dns_name_issubdomain(>name, >domain))

2020-09-25 Thread Christian Ehrhardt
** Tags added: server-next -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896740 Title: BIND crashes with failed assertion INSIST(dns_name_issubdomain(>name, >domain)) To manage notifications

[Bug 1890435] Re: gcc-10 breaks on armhf (flaky): internal compiler error: Segmentation fault

2020-09-25 Thread Christian Ehrhardt
I tried to isolate what was running concurrently and found 7 gcc calls. I have set them up to run concurrently in endless loops each. That way they reached a lot of iterations without triggering the issue :-/ I don't know how to continue :-/ But I can share a login to this system and show how to

[Bug 1849644] Re: QEMU VNC websocket proxy requires non-standard 'binary' subprotocol

2020-09-25 Thread Christian Ehrhardt
SRU Template for qemu added and MP linked to fix this in Ubuntu 20.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849644 Title: QEMU VNC websocket proxy requires non-standard 'binary'

[Bug 1887490] Re: Add/Backport EPYC-v3 and EPYC-Rome CPU model

2020-09-25 Thread Christian Ehrhardt
** Description changed: + ## Qemu SRU ## + + [Impact] + + * CPU definitions are added to qemu as these CPUs are known. +And due to that over time are missing in former releases. + + * To really benefit from the new features of these chips +they have to be known, therefore new type

[Bug 1896751] Re: Guest hang on reboot after migration from bionic to focal

2020-09-25 Thread Christian Ehrhardt
SRU Template for qemu added and MP linked to fix this in Ubuntu 20.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896751 Title: Guest hang on reboot after migration from bionic to focal To

[Bug 1887490] Re: Add/Backport EPYC-v3 and EPYC-Rome CPU model

2020-09-25 Thread Christian Ehrhardt
SRU Template for qemu added and MP linked to fix this in Ubuntu 20.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887490 Title: Add/Backport EPYC-v3 and EPYC-Rome CPU model To manage

[Bug 1849644] Re: QEMU VNC websocket proxy requires non-standard 'binary' subprotocol

2020-09-24 Thread Christian Ehrhardt
** Description changed: - When running a machine using "-vnc" and the "websocket" option QEMU - seems to require the subprotocol called 'binary'. This subprotocol does - not exist in the WebSocket specification. In fact it has never existed - in the spec, in one of the very early drafts of

[Bug 1887490] Re: Add/Backport EPYC-v3 and EPYC-Rome CPU model

2020-09-24 Thread Christian Ehrhardt
** Changed in: qemu (Ubuntu Focal) 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/1887490 Title: Add/Backport EPYC-v3 and EPYC-Rome CPU model To manage

[Bug 1896751] Re: Guest hang on reboot after migration from bionic to focal

2020-09-24 Thread Christian Ehrhardt
** Changed in: qemu (Ubuntu Focal) 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/1896751 Title: Guest hang on reboot after migration from bionic to focal To

[Bug 1896937] Re: Error with seclabel "apparmor" since upgrading from 18.04 to 20.04

2020-09-24 Thread Christian Ehrhardt
Hi, Please check with aa-status if libvirtd itself is being in enforced mode. If it isn't it can't provide apparmor seslabel handling to guests. Should be something like (reduced the length a bit) $ sudo aa-status | grep -e mode -e libvirt 257 profiles are in enforce mode. libvirtd

[Bug 1896751] Re: Guest hang on reboot after migration from bionic to focal

2020-09-24 Thread Christian Ehrhardt
** Description changed: - When migrating a guest from a bionic host to a focal host, the guest may - hang during reboot. This is due to an upstream optimization that skips - ROM reset on incoming migrations. + [Impact] + + * Upstream skipped rom resets which turned out to affect the +

[Bug 1896751] Re: Guest hang on reboot after migration from bionic to focal

2020-09-24 Thread Christian Ehrhardt
Without the fix: 1. spawn guest on bionic $ uvt-kvm create --password ubuntu testguest arch=amd64 release=bionic label=daily 2. migrate it over to a focal system $ virsh migrate --live testguest qemu+ssh://10.102.141.223/system 3. check on focal if the guest arrived e.g. log in $ virsh console

[Bug 1849644] Re: QEMU VNC websocket proxy requires non-standard 'binary' subprotocol

2020-09-24 Thread Christian Ehrhardt
I can confirm the test steps mentioned above. In an unchanged scenario a formerly failing-to-connect case got working when replacing the qemu (on Focal) in use with a patched one. Adding an SRU Template for Focal to the bug description ... -- You received this bug notification because you are a

[Bug 1894804] Re: Second DEVICE_DELETED event missing during virtio-blk disk device detach

2020-09-24 Thread Christian Ehrhardt
As outlined before the time from device_del to the DEVICE_DELETED is indeed "a bit longer" in Focal (from ~0.1s to ~6s), but other than that I couldn't find anything else yet. We were wondering due to [1] in a related bug if it might be dependent to (over)load. I was consuming Disk and CPU in a

[Bug 1890435] Re: gcc-10 breaks on armhf (flaky): internal compiler error: Segmentation fault

2020-09-24 Thread Christian Ehrhardt
Interim Summary: - hits armhf compiles of various large source projects, chances are it it completely random and just hits those more likely by compiling more - build system auto-retries the compiles and they work on retry eventually reported as "The bug is not reproducible, so it is likely

[Bug 1890435] Re: gcc-10 breaks on armhf (flaky): internal compiler error: Segmentation fault

2020-09-24 Thread Christian Ehrhardt
Not sure if it is entirely random, it hit the second time on /<>/linux-user/syscall.c:12479:1: internal compiler error: Segmentation fault in like 2/8 hits I've had so far. Given how much code it builds that is unlikely to be an accident. -- You received this bug notification because you are

[Bug 1890435] Re: gcc-10 breaks on armhf (flaky): internal compiler error: Segmentation fault

2020-09-24 Thread Christian Ehrhardt
Three reruns later I got cc -iquote /root/qemu-5.0/b/qemu/accel/tcg -iquote accel/tcg -iquote /root/qemu-5.0/tcg/arm -isystem /root/qemu-5.0/linux-headers -isystem /root/qemu-5.0/b/qemu/linux-headers -iquote . -iquote /root/qemu-5.0 -iquote /root/qemu-5.0/accel/tcg -iquote

[Bug 1849644] Re: QEMU VNC websocket proxy requires non-standard 'binary' subprotocol

2020-09-24 Thread Christian Ehrhardt
Repro steps: $ sudo apt install qemu-system-x86 novnc /usr/share/novnc python3 -m http.server Connect browser to http://:8000/vnc.html Click "Settings" Open "advanced" Open "websocket" Set port 5700 Clear path Click "Connect" And it works ... Turns out my former check on the

[Bug 1849644] Re: QEMU VNC websocket proxy requires non-standard 'binary' subprotocol

2020-09-24 Thread Christian Ehrhardt
This is in v5.0.0 so fixed in Groovy. The related noVNC change is in upstream version >=v1.0.0 which correlates with Ubuntu >=20.04, threfore fixing this in Focals Qemu seems good. ** Also affects: qemu (Ubuntu) Importance: Undecided Status: New ** Also affects: qemu (Ubuntu Focal)

[Bug 1896751] Re: Guest hang on reboot after migration from bionic to focal

2020-09-24 Thread Christian Ehrhardt
This is in v5.0.0 so fixed in Groovy. But the offending patch is in Focal so there we need a fix. @Markus - is there anything needed to reproduce (particular guest config) other than migrating from B->F and then rebooting? ** Also affects: qemu (Ubuntu Focal) Importance: Undecided

[Bug 1887490] Re: Add/Backport EPYC-v3 and EPYC-Rome CPU model

2020-09-24 Thread Christian Ehrhardt
Thanks for the extra reports - I'll take a look at these qemu cases and in that time you can try getting the libvirt Rome change upstream. Once everything is in place we can SRU libvirt sort of together on this. -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1890435] Re: gcc-10 breaks on armhf (flaky): internal compiler error: Segmentation fault

2020-09-24 Thread Christian Ehrhardt
Ok, apport through the stack of LXD is ... not working. I have used a more mundane core pattern and a C test program to ensure I will get crash dumps. $ cat /proc/sys/kernel/core_pattern /var/crash/core.%e.%p.%h.%t $ gcc test.c ; ./a.out ; ll /var/crash/ Segmentation fault (core dumped) total 3

[Bug 1890435] Re: gcc-10 breaks on armhf (flaky): internal compiler error: Segmentation fault

2020-09-23 Thread Christian Ehrhardt
Finally: cc -iquote /root/qemu-5.0/b/user-static/linux-user -iquote linux-user -iquote /root/qemu-5.0/tcg/arm -isystem /root/qemu-5.0/linux-headers -isystem /root/qemu-5.0/b/user-static/linux-headers -iquote . -iquote /root/qemu-5.0 -iquote /root/qemu-5.0/accel/tcg -iquote

[Bug 1890435] Re: gcc-10 breaks on armhf (flaky): internal compiler error: Segmentation fault

2020-09-23 Thread Christian Ehrhardt
I got the crash in the repro env. dmesg holds no OOM which is good - also no other dmesg/journal entry that would be related. It might be depending on concurrent execution as this was the primary change to last time. And not having set up apport/whoopsie to catch the crash :-/ I've installed

Re: [Bug 1874647] Re: [Ubuntu 20.04] Stale libvirt cache leads to VM startup failures

2020-09-23 Thread Christian Ehrhardt
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.

[Bug 1815632] Re: seeds update: remove from supported

2020-09-23 Thread Christian Ehrhardt
FYI server-ship isn't used anymore to build an ISO or anything like it (only server-ship-live is). We recently migrated everything off server-ship as it will likely go away in the future. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1887490] Re: Add/Backport EPYC-v3 and EPYC-Rome CPU model

2020-09-23 Thread Christian Ehrhardt
@Markus - did the patch 5d6059f8ec cpu_map: Distinguish Cascadelake-Server from Skylake-Server really work for you without the changes to support stepping applies? Or does your own build have much more applied to make it work? -- You received this bug notification because you are a member of

[Bug 1887490] Re: Add/Backport EPYC-v3 and EPYC-Rome CPU model

2020-09-23 Thread Christian Ehrhardt
I agree Markus. Not only does the Focal qemu miss the related changes, I also dived deeper through the "what exactly happened" to be sure. The added patches I picked make it more obvious (test breaks) that we would need cpu model "stepping" ranges to work. This would add the need for much more

[Bug 1887490] Re: Add/Backport EPYC-v3 and EPYC-Rome CPU model

2020-09-23 Thread Christian Ehrhardt
Hmm, I spoke too soon ... :-/ Some of the self tests failed due to the changes - I'll fix them up and ping again once the builds complete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887490 Title:

[Bug 1890435] Re: gcc-10 breaks on armhf (flaky): internal compiler error: Segmentation fault

2020-09-23 Thread Christian Ehrhardt
I reduced the CPU/Mem of my canonistack system that I try to recreate on (to be more similar). Also I now do run with DEB_BUILD_OPTIONS=parallel=4 as the real build. /me hopes this might help to finally trigger it in a debuggable environment. P.S: I'm now at 4/4 retries that failed for the real

[Bug 1887490] Re: Add/Backport EPYC-v3 and EPYC-Rome CPU model

2020-09-23 Thread Christian Ehrhardt
Thanks for the test of the new kernel Markus! I have respun the qemu build (the old one was outdated by a massive stable update - too bad this wasn't part of 4.2.1 already) with the patches we had before applied on top. Further I have reviewed the suggested libvirt changes and added a build

[Bug 1890435] Re: gcc-10 breaks on armhf (flaky): internal compiler error: Segmentation fault

2020-09-23 Thread Christian Ehrhardt
Bumping the prio since -as we were afraid of - this starts to become a service-problem (what if we can't rebuild anymore?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890435 Title: gcc-10 breaks

[Bug 1890435] Re: gcc-10 breaks on armhf (flaky): internal compiler error: Segmentation fault

2020-09-23 Thread Christian Ehrhardt
cc -iquote /<>/b/qemu/accel/tcg -iquote accel/tcg -iquote /<>/tcg/arm -isystem /<>/linux-headers -isystem /<>/b/qemu/linux-headers -iquote . -iquote /<> -iquote /<>/accel/tcg -iquote /<>/include -iquote /<>/disas/libvixl -I/usr/include/pixman-1 -pthread -I/usr/include/glib-2.0

[Bug 1847105] Re: very slow disk creation, snapshotting

2020-09-22 Thread Christian Ehrhardt
** Description changed: - This is a regression in eoan for me. I use virt-manager to create vms, - and I noticed that creating one now takes more than a minute. + [Impact] + + * The defaults of virt-manager for disk allocation always worked fine +when qcow2 had nothing but sparse support.

[Bug 1890435] Re: gcc-10 breaks on armhf (flaky): internal compiler error: Segmentation fault

2020-09-22 Thread Christian Ehrhardt
And again on the same :-/ cc -iquote /<>/b/qemu/linux-user/s390x -iquote linux-user/s390x -iquote /<>/tcg/arm -isystem /<>/linux-headers -isystem /<>/b/qemu/linux-headers -iquote . -iquote /<> -iquote /<>/accel/tcg -iquote /<>/include -iquote /<>/disas/libvixl -I/usr/include/pixman-1

[Bug 1890435] Re: gcc-10 breaks on armhf (flaky): internal compiler error: Segmentation fault

2020-09-22 Thread Christian Ehrhardt
Another breakage at https://launchpad.net/ubuntu/+source/qemu/1:5.0-5ubuntu9/+build/19958575 I had to retry it, we will see if it works on retry as before -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1895967] Re: Apparmor 3.0.0 does not load profiles in containers anymore

2020-09-22 Thread Christian Ehrhardt
That patch by Christian Bolz is already applied (which seems reasonable after that much time), but when merging 3.0 the old patch for bug 1824812 should have been dropped. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1895967] Re: Apparmor 3.0.0 does not load profiles in containers anymore

2020-09-22 Thread Christian Ehrhardt
Tested the change - works as expected, prepping an MP -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895967 Title: Apparmor 3.0.0 does not load profiles in containers anymore To manage

[Bug 1895967] Re: Apparmor 3.0.0 does not load profiles in containers anymore

2020-09-22 Thread Christian Ehrhardt
As refrence, it is a re-occurrence of https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1824812 , look who filed that bug :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895967 Title:

[Bug 1895967] Re: Apparmor 3.0.0 does not load profiles in containers anymore

2020-09-22 Thread Christian Ehrhardt
Isn't that "Not starting AppArmor in container" message just in: /lib/apparmor/apparmor.systemd -> /lib/apparmor/rc.apparmor.functions -> function is_container_with_internal_policy() That looks unchanged (except a comment) but it behaves differently: root@testguest-apparmor-good:~# .

[Bug 1895967] Re: Apparmor 3.0.0 does not load profiles in containers anymore

2020-09-22 Thread Christian Ehrhardt
https://gitlab.com/apparmor/apparmor/-/commit/61c27d8808f0589beb6a319cc04073e8bb32d860 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895967 Title: Apparmor 3.0.0 does not load profiles in

[Bug 1895967] Re: Apparmor 3.0.0 does not load profiles in containers anymore

2020-09-22 Thread Christian Ehrhardt
And we are back with Christian Bolz :-) commit 61c27d8808f0589beb6a319cc04073e8bb32d860 Author: Christian Boltz Date: Fri Jun 21 19:22:15 2019 +0200 Fix and simplify setting SFS_MOUNTPOINT The question is why isn't this in the apparmor 3.0 package in groovy- proposed ? -- You received

[Bug 1895967] Re: 3.0.0~beta1-0ubuntu1 in Groovy breaks Libvirt/Qemu/KVM

2020-09-22 Thread Christian Ehrhardt
Bad case: $ ./repro.sh bad + '[' bad == bad ']' + echo 'Bad case: Using apparmor from proposed' Bad case: Using apparmor from proposed + BADCASE=1 + lxc stop --force testguest-apparmor-bad + lxc delete --force testguest-apparmor-bad + lxc launch ubuntu-daily:groovy/amd64 testguest-apparmor-bad

[Bug 1895967] Re: 3.0.0~beta1-0ubuntu1 in Groovy breaks Libvirt/Qemu/KVM

2020-09-22 Thread Christian Ehrhardt
It seems it comes down to a change in /lib/apparmor/apparmor.systemd which now refuses to load profiles when running in a container. Example with 3.0: $ /lib/apparmor/apparmor.systemd reload Not starting AppArmor in container Example with 2.x /lib/apparmor/apparmor.systemd reload Restarting

[Bug 1895967] Re: 3.0.0~beta1-0ubuntu1 in Groovy breaks Libvirt/Qemu/KVM

2020-09-22 Thread Christian Ehrhardt
FYI - other testing might miss this as "starting a guest on groovy" works with the new versions, but it will be without apparmor. Migrating from focal or a pre-upgrade groovy shows the issues broken by apparmor not being enabled. ** Changed in: apparmor (Ubuntu) Status: Incomplete => New

[Bug 1895967] Re: 3.0.0~beta1-0ubuntu1 in Groovy breaks Libvirt/Qemu/KVM

2020-09-22 Thread Christian Ehrhardt
I have backed up this container and its snapshot for later and re-run the whole automation which got me that bad state. That allowed me to run my automation again without removing this container (in case we need it for debugging later). So I ran everything again to check if it would happen again

[Bug 1895967] Re: 3.0.0~beta1-0ubuntu1 in Groovy breaks Libvirt/Qemu/KVM

2020-09-22 Thread Christian Ehrhardt
Ok, I have definitely a snapshot left that has "conserved" the bad state. $ lxc stop testkvm-groovy-from $ lxc restore testkvm-groovy-from orig $ lxc start testkvm-groovy-from $ lxc exec testkvm-groovy-from # aa-status apparmor module is loaded. 15 profiles are loaded. 15 profiles are in enforce

[Bug 1895967] Re: 3.0.0~beta1-0ubuntu1 in Groovy breaks Libvirt/Qemu/KVM

2020-09-22 Thread Christian Ehrhardt
Hi Christian Bolz o/ I'd have such rules but this isn't the problem here as that would matter only much later. I libvirtd itself isn't confined it refuses to go on confining the guests and that is here the problem. The current question really comes down to "how did I manage to have everything

[Bug 1895967] Re: 3.0.0~beta1-0ubuntu1 in Groovy breaks Libvirt/Qemu/KVM

2020-09-22 Thread Christian Ehrhardt
I knew from my former tests: 1. apparmor 3.0 = bad 2. downgrading to 2.13.3-7ubuntu6 and back up to 3.0 = good 3. aa-enforce + service restart = good I checked the logs on the affected systems how this got into the bad state: $ grep -E 'configure (lib)?(apparmor|libvirt)' /var/log/dpkg.log

[Bug 1895060] Re: [FFe] apparmor 3 upstream release

2020-09-22 Thread Christian Ehrhardt
Sorry, while being about evaluating the new apparmor this got posted to the wrong bug :-/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895060 Title: [FFe] apparmor 3 upstream release To manage

[Bug 1895060] Re: [FFe] apparmor 3 upstream release

2020-09-22 Thread Christian Ehrhardt
I knew from my former tests: 1. apparmor 3.0 = bad 2. downgrading to 2.13.3-7ubuntu6 and back up to 3.0 = good 3. aa-enforce + service restart = good I checked the logs on the affected systems how this got into the bad state: $ grep -E 'configure (lib)?(apparmor|libvirt)' /var/log/dpkg.log

[Bug 1894942] Re: [UBUNTU 20.04] Lost virtio host --> guest notifications cause devices to cease normal operation

2020-09-22 Thread Christian Ehrhardt
Checking SRU compatibility: #1 Source Focal: some (minor) backport noise Bionic: the same backport of Focal applies with offsets. Xenial: some more nois (tracepoint missing), but still ok Not as-is, but pretty close - should be ok #2 Builds I have started builds of those in

[Bug 1896575] Re: [UBUNTU 20.04] syslog daemon stop running unexpectedly

2020-09-22 Thread Christian Ehrhardt
This would usually be handled and written by rsyslog, what is this reporting: $ systemctl status syslog Also was /etc/rsyslog* modified in any way (please attach the config files) You showed this case with a tail -f, any chance that it rotated away and there are new entries in a new

[Bug 1893784] Re: [FFe]: apply some useful upstream changes

2020-09-22 Thread Christian Ehrhardt
I was cleaning MPs today, this seems to still waiting on FFe approval :-/ I'll ping a few people ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893784 Title: [FFe]: apply some useful upstream

[Bug 1847105] Re: very slow disk creation, snapshotting

2020-09-21 Thread Christian Ehrhardt
It works (as expected): before: 4 0 17337 263 20 0 163108 4240 - Sl ? 0:47 \_ /usr/bin/qemu-img create -f qcow2 -o preallocation=falloc,compat=1.1,lazy_refcounts /var/lib/libvirt/images/ubuntu20.04.qcow2 26214400K Now: 4 0 43901 263 20 0 163108

[Bug 1847105] Re: very slow disk creation, snapshotting

2020-09-21 Thread Christian Ehrhardt
Now that we got the change we sort of wanted from the beginning I have created a test build of virt-manager with the change applied. I need to debug if that now really enters the right code paths for non fallocate. -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1895967] Re: 3.0.0~beta1-0ubuntu1 in Groovy breaks Libvirt/Qemu/KVM

2020-09-21 Thread Christian Ehrhardt
Yeah and the comment above this function pointed the right way: Good case (libvirt is enforced): oot@testkvm-groovy-to:~# aa-status apparmor module is loaded. 31 profiles are loaded. 31 profiles are in enforce mode. /snap/snapd/9279/usr/lib/snapd/snap-confine

[Bug 1895967] Re: 3.0.0~beta1-0ubuntu1 in Groovy breaks Libvirt/Qemu/KVM

2020-09-21 Thread Christian Ehrhardt
This gets me back to a working system $ aa-enforce /etc/apparmor.d/usr.sbin.libvirtd $ systemctl restart libvirtd And this also explains why on the system where I re-installed libvirt things might have worked. The re-install runs dh_apparmor which has loaded and enforced it. -- You

[Bug 1895967] Re: 3.0.0~beta1-0ubuntu1 in Groovy breaks Libvirt/Qemu/KVM

2020-09-21 Thread Christian Ehrhardt
Sorry my system broke down in various way stalling debugging of this for a few days. Back on it ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895967 Title: 3.0.0~beta1-0ubuntu1 in Groovy

[Bug 1894804] Re: Second DEVICE_DELETED event missing during virtio-blk disk device detach

2020-09-21 Thread Christian Ehrhardt
Hi, interesting bug report - thanks lee, Kashyap and Sean - as well as Danil for taking a look already. If this would always fail no unplugs would work ever which I knew can't be right as I test that. So we need to find what is different... @Openstack people - is that reliably triggering at

[Bug 1836701] Re: ubuntu18.04: ipmitool failed: Could not open device at /dev/ipmi0 : No such file or directory

2020-09-21 Thread Christian Ehrhardt
Mine: openat(AT_FDCWD, "/dev/ipmi0", O_RDWR) = 3 <0.52 Yours: openat(AT_FDCWD, "/dev/ipmi0", O_RDWR) = -1 EINVAL (Invalid argument) <0.53> So we are back at the kernel backend of this - on your particular hardware/firmware - not behaving correctly. This isn't one of the later ioctls,

[Bug 1818877] Re: uvtool doesn't specify a default video device

2020-09-21 Thread Christian Ehrhardt
This is in Focal, setting to Released ** Changed in: uvtool (Ubuntu) Status: In Progress => Fix Released ** Changed in: uvtool (Ubuntu) Assignee: Robie Basak (racb) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

Re: [Bug 1836701] Re: ubuntu18.04: ipmitool failed: Could not open device at /dev/ipmi0 : No such file or directory

2020-09-18 Thread Christian Ehrhardt
On Fri, Sep 18, 2020 at 2:15 PM Ventsislav Georgiev <1836...@bugs.launchpad.net> wrote: > > Yeah I did try that (saw it somewhere among the web) but it pretty much > gives nothing, because of the main error. > > root@x:~# strace -rT -ff -o ipmitool.strace ipmitool lan print > Could not open device

[Bug 1836701] Re: ubuntu18.04: ipmitool failed: Could not open device at /dev/ipmi0 : No such file or directory

2020-09-18 Thread Christian Ehrhardt
Hmm, so your system indeed has /dev/ipmi0 then (also you had that implicitly in comment #4 already) - thanks. But that means we are back at the beginning with the but triggering for you but being non reproducible in other places :-/ For the sake of generating more ideas what could happen in

[Bug 1887490] Re: Add/Backport EPYC-v3 and EPYC-Rome CPU model

2020-09-18 Thread Christian Ehrhardt
Correct Stefan, this is for Focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887490 Title: Add/Backport EPYC-v3 and EPYC-Rome CPU model To manage notifications about this bug go to:

[Bug 1836701] Re: ubuntu18.04: ipmitool failed: Could not open device at /dev/ipmi0 : No such file or directory

2020-09-18 Thread Christian Ehrhardt
** Attachment added: "strace good case" https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1836701/+attachment/5412154/+files/ipmitool.strace.183665 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1892245] Re: Extension breaks when accessing Overview or applications list (Focal)

2020-09-18 Thread Christian Ehrhardt
I can (as the other reporters) confirm that the version in focal- proposed works fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892245 Title: Extension breaks when accessing Overview or

[Bug 1892245] Re: Extension breaks when accessing Overview or applications list (Focal)

2020-09-18 Thread Christian Ehrhardt
Hi Fabio, I ran into the same issue today (bug 1896188 now marked a dup of this one) and I'm very happy to see your fix already in focal-proposed - thanks!. ** Bug watch added: Debian Bug tracker #968613 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968613 ** Also affects:

[Bug 1896188] Re: Activities Overview does not exit anymore getting the desktop stuck

2020-09-18 Thread Christian Ehrhardt
*** This bug is a duplicate of bug 1892245 *** https://bugs.launchpad.net/bugs/1892245 This might be an incompatibility of gnome-shell-extension-dash-to-panel version 31-1 with the recent update to gnome-shell:amd64 3.36.4-1ubuntu1~20.04. This bug seems to be about the same:

[Bug 1896188] Re: Activities Overview does not exit anymore getting the desktop stuck

2020-09-18 Thread Christian Ehrhardt
There were no extensions in: '/home/paelzer/.local/share/gnome-shell/extensions': No such file or directory I already disabled them via gnome-tweaks before, but doing so again the ways you asked me to do that. Getting back to the config showed a few of them enabled indeed, maybe that was

[Bug 1896188] Re: Activities Overview does not exit anymore getting the desktop stuck

2020-09-18 Thread Christian Ehrhardt
That was it, thanks Daniel! Now I need to restore as much of my config as possible without breaking it again ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896188 Title: Activities Overview

[Bug 1896188] ProcCpuinfoMinimal.txt

2020-09-18 Thread Christian Ehrhardt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1896188/+attachment/5412104/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1896188] Re: Show Application Overlay does not exit anymore getting the desktop stuck

2020-09-18 Thread Christian Ehrhardt
Now the description is complete in regard to all things worth to try that came to my mind. Also the apport data as well as the video is attached. Setting back to new for re-review by the Desktop Team. P.S. is the overlay an application on it's own that I could try to kill from a console?

[Bug 1896188] monitors.xml.txt

2020-09-18 Thread Christian Ehrhardt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1896188/+attachment/5412107/+files/monitors.xml.txt ** Description changed: Hi, this must sound odd, but to me most Desktop bugs do :-/ The issue: - If I hit the meta key the usual "search

[Bug 1896188] Dependencies.txt

2020-09-18 Thread Christian Ehrhardt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1896188/+attachment/5412102/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1896188] GsettingsChanges.txt

2020-09-18 Thread Christian Ehrhardt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1896188/+attachment/5412103/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1896188] ShellJournal.txt

2020-09-18 Thread Christian Ehrhardt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1896188/+attachment/5412106/+files/ShellJournal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1896188] ProcEnviron.txt

2020-09-18 Thread Christian Ehrhardt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1896188/+attachment/5412105/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896188

[Bug 1896188] Re: Show Application Overlay does not exit anymore getting the desktop stuck

2020-09-18 Thread Christian Ehrhardt
The video shows: 00:09 - opening the "Show Applications" overlay works fine at first. 00:14 - searching an application in there works 00:16 - I open gedit and would expect to get back onto the desktop. But I can't it sticks within the overlay. I tried to hit the "Escape" key, clicking on

[Bug 1896188] Re: Show Application Overlay does not exit anymore getting the desktop stuck

2020-09-18 Thread Christian Ehrhardt
Hi Daniel, I'm on it ... :-) Video just completed - I already wrote that I'll attach one. And I separated the "potentially related, but other issues" into an extra section for exactly the reason of keeping this bug to one issue, but at the same time I want/need to provide all info that might be

[Bug 1896188] Re: GTK Overlays do not refresh/exit and get the desktop stuck

2020-09-18 Thread Christian Ehrhardt
** Description changed: Hi, this must sound odd, but to me most Desktop bugs do :-/ The issue: - If I hit the meta key the usual "search app" overlay appears. - I search for an application and start it - the overlay does NOT disappear anymore - the miniature images of the just

[Bug 1896188] Re: GTK Overlays do not refresh/exit and get the desktop stuck

2020-09-18 Thread Christian Ehrhardt
** Summary changed: - Overlays do not refresh anymore and get the desktop stuck + GTK Overlays do not refresh/exit and get the desktop stuck -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896188

[Bug 1896188] Re: Overlays do not refresh anymore and get the desktop stuck

2020-09-18 Thread Christian Ehrhardt
** Description changed: Hi, this must sound odd, but to me most Desktop bugs do :-/ The issue: - If I hit the meta key the usual "search app" overlay appears. - I search for an application and start it - the overlay does NOT disappear anymore - the miniature images of the just

[Bug 1896188] Re: Overlays do not refresh anymore and get the desktop stuck

2020-09-18 Thread Christian Ehrhardt
** Description changed: Hi, this must sound odd, but to me most Desktop bugs do :-/ The issue: - If I hit the meta key the usual "search app" overlay appears. - I search for an application and start it - the overlay does NOT disappear anymore - the miniature images of the just

[Bug 1896188] Re: Overlays do not refresh anymore and get the desktop stuck

2020-09-18 Thread Christian Ehrhardt
On backup I had: mv: cannot stat '.gnome2': No such file or directory mv: cannot stat '.gconfd': No such file or directory mv: cannot stat '.metacity': No such file or directory but worked for the rest Also disabled all extensions (didn't have any active, but can't hurt) Restarting into that now

[Bug 1896188] Re: Overlays do not refresh anymore and get the desktop stuck

2020-09-18 Thread Christian Ehrhardt
Trying hard reset of my config via: $ mkdir -p ~/.backup-gnome-config/ && for f in .gnome .gnome2 .gconf .gconfd .metacity .config/dconf; do mv $f ~/.backup-gnome-config/; done $ gnome-tweaks # then reset to defaults -- You received this bug notification because you are a member of Ubuntu

[Bug 1896188] Re: Overlays do not refresh anymore and get the desktop stuck

2020-09-18 Thread Christian Ehrhardt
** Description changed: Hi, this must sound odd, but to me most Desktop bugs do :-/ The issue: - If I hit the meta key the usual "search app" overlay appears. - I search for an application and start it - the overlay does NOT disappear anymore - the miniature images of the just

[Bug 1896188] Re: Overlays do not refresh anymore and get the desktop stuck

2020-09-18 Thread Christian Ehrhardt
** Description changed: Hi, this must sound odd, but to me most Desktop bugs do :-/ The issue: - If I hit the meta key the usual "search app" overlay appears. - I search for an application and start it - the overlay does NOT disappear anymore - the miniature images of the just

[Bug 1896188] [NEW] Overlays do not refresh anymore and get the desktop stuck

2020-09-18 Thread Christian Ehrhardt
Public bug reported: Hi, this must sound odd, but to me most Desktop bugs do :-/ The issue: - If I hit the meta key the usual "search app" overlay appears. - I search for an application and start it - the overlay does NOT disappear anymore - the miniature images of the just started app seems

[Bug 1895967] Re: 3.0.0~beta1-0ubuntu1 in Groovy breaks Libvirt/Qemu/KVM

2020-09-17 Thread Christian Ehrhardt
Lookup fails: (gdb) fin Run till exit from #0 virSecurityDriverLookup (name=name@entry=0x0, virtDriver=virtDriver@entry=0x7fffd26ae1b2 "QEMU") at ../../../src/security/security_driver.c:50 virSecurityManagerNew (name=name@entry=0x0, virtDriver=virtDriver@entry=0x7fffd26ae1b2 "QEMU",

[Bug 1895967] Re: 3.0.0~beta1-0ubuntu1 in Groovy breaks Libvirt/Qemu/KVM

2020-09-17 Thread Christian Ehrhardt
This is the failing function 221 /* returns -1 on error or profile for libvirtd is unconfined, 0 if complain 222 * mode and 1 if enforcing. This is required because at present you cannot 223 * aa_change_profile() from a process that is unconfined. 224

[Bug 1895967] Re: 3.0.0~beta1-0ubuntu1 in Groovy breaks Libvirt/Qemu/KVM

2020-09-17 Thread Christian Ehrhardt
Need to check the init of the bunch in qemuSecurityInit and qemuSecurityNew. But that happens at daemon start and not later when probing caps. virQEMUDriverConfigLoadSecurityEntry load this from config and it includes apparmor in both: /etc/libvirt/qemu.conf:# security_driver = [

[Bug 1895967] Re: 3.0.0~beta1-0ubuntu1 in Groovy breaks Libvirt/Qemu/KVM

2020-09-17 Thread Christian Ehrhardt
for (i = 0; sec_managers[i]; i++) { ... VIR_DEBUG("Initialized caps for security driver \"%s\" with " Good: - apparmor - dac Bad: - none - dac In function virQEMUDriverCreateCapabilities. So it isn't probing apparmor because it isn't even in the list. That list is from

[Bug 1895967] Re: 3.0.0~beta1-0ubuntu1 in Groovy breaks Libvirt/Qemu/KVM

2020-09-17 Thread Christian Ehrhardt
Good: (gdb) p *((virSecurityStackDataPtr)(((virQEMUDriverPtr)conn->privateData )->securityManager->privateData))->itemsHead->securityManager $7 = {parent = {parent = {parent_instance = {g_type_instance = {g_class = 0x7f430805ddf0}, ref_count = 1, qdata = 0x0}}, lock = {lock = {__data = {__lock

[Bug 1895967] Re: 3.0.0~beta1-0ubuntu1 in Groovy breaks Libvirt/Qemu/KVM

2020-09-17 Thread Christian Ehrhardt
It seems once fixed the system is ok and I can't get into the bad state again :/ I tried on another bad system (withotu changing back to the former version) 1. A restart of the service 2. Trying to force capabilities reset (remove cache) + service restart None of these got it into the good case,

[Bug 1895967] [NEW] 3.0.0~beta1-0ubuntu1 in Groovy breaks Libvirt/Qemu/KVM

2020-09-17 Thread Christian Ehrhardt
Public bug reported: Hi, I stumbled over this due to automatic tests checking proposed. I found that Focal no more could migrate to Groovy with: $ virsh migrate --unsafe --live fguest qemu+ssh://10.162.30.163/system error: unsupported configuration: Security driver model 'apparmor' is not

[Bug 1894619] Re: [2.82 regression] router announcements have 'forever' lifetime by default

2020-09-17 Thread Christian Ehrhardt
The tests confirmed the issue that Iain reported and that the fix works. Also no other issues popped up in the NM test using it. autopkgtest [08:47:12]: summary wpa-dhclient PASS nm.pyPASS killswitches-no-urfkill PASS urfkill-integration PASS And

Re: [Bug 1895137] Re: [MIR] rpi-eeprom

2020-09-17 Thread Christian Ehrhardt
> > - Please consider updating to a newer version before you SRU things to > >=Focal > > Is it best at this point to fix the existing 7.8 upload, or reject that > and fix all this in a new 9.0 upload? Happy to do whichever is easier > from the MIR/security team's perspective. IMHO cancel what is

  1   2   3   4   5   6   7   8   9   10   >