This bug was fixed in the package linux - 4.15.0-42.45
---
linux (4.15.0-42.45) bionic; urgency=medium
* linux: 4.15.0-42.45 -proposed tracker (LP: #1803592)
* [FEAT] Guest-dedicated Crypto Adapters (LP: #1787405)
- KVM: s390: reset crypto attributes for all vcpus
- KVM:
This bug was fixed in the package linux - 4.15.0-42.45
---
linux (4.15.0-42.45) bionic; urgency=medium
* linux: 4.15.0-42.45 -proposed tracker (LP: #1803592)
* [FEAT] Guest-dedicated Crypto Adapters (LP: #1787405)
- KVM: s390: reset crypto attributes for all vcpus
- KVM:
I've verified [Test Case] using 4.15.0-42.45-generic.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1784501
Title:
libvirtd is unable to configure bridge
Bionic SRU: https://lists.ubuntu.com/archives/kernel-
team/2018-October/096335.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1784501
Title:
libvirtd is unable to configure bridge
** Description changed:
+ [Impact]
+
libvirtd cannot properly configure the default bridge device when
installed inside of unprivileged LXD containers. 'systemctl status
libvirtd' shows the following error:
- error : virNetDevBridgeSet:140 : Unable to set bridge virbr0
+ error :
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Tyler Hicks (tyhicks)
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
My 2nd theory was correct. ;-) Sorry for polluting this bug report with
my thinking-out-loud.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1784501
Title:
libvirtd is unable to
@mpontillo would you mind testing with the libvirt that's in the release
pocket of Bionic?
https://launchpad.net/ubuntu/+source/libvirt/4.0.0-1ubuntu8
That would help tell us if libvirt has had an SRU that changed this
behavior in the short time that Bionic has been released.
--
You received
To be fair, it's also possible that I did something like the following
in my previous test container and forgot about it. ;-)
cat << EOF > maas.xml
maas
EOF
virsh net-define maas.xml
rm maas.xml
virsh net-start maas
virsh net-autostart maas
--
You received this bug notification
Nothing has changed regarding privileged vs. unprivileged settings.
I just set this up again with a privileged container, and I believe the
cause of the regression to actually be in libvirt. I think it must have
silently ignored the bridge configuration error before and marked the
network active
@mpontillo Bionic has always suffered from this bug. The patch set has
only been backport to Cosmic and the fixes have not yet been backported
to Bionic.
Have you, by chance, recently reconfigured your container to be an
unprivileged container when it was previously a privileged container? (I
Were you maybe using a privileged container before? Those aren't
affected by the /sys ownership issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1784501
Title:
libvirtd is unable
This seems to be a regression on bionic; I have been using libvirtd
inside a container for several weeks; today when I tore down and rebuilt
the container I hit this bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug was fixed in the package linux - 4.17.0-7.8
---
linux (4.17.0-7.8) cosmic; urgency=medium
* linux: 4.17.0-7.8 -proposed tracker (LP: #1785242)
* Cosmic update to 4.17.12 stable release (LP: #1785211)
- spi: spi-s3c64xx: Fix system resume support
- Input:
Adding a task for bionic as we'll want this fix to be available for our 18.04
users.
No need to backport it to anything older than that though.
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1784501
Title:
libvirtd is unable to configure bridge devices
Patches submitted for inclusion in Ubuntu Cosmic:
https://lists.ubuntu.com/archives/kernel-team/2018-July/094426.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1784501
Title:
19 matches
Mail list logo
