Bug#930100: after upgrade to buster, qemu cannot read default spice certs

2019-06-18 Thread Sam Hartman
control: tags -1 patch here you go. Rebuilt packages and tested on one of our vm servers. From 76321001651a1c9a3425b38f231373bb6b31b922 Mon Sep 17 00:00:00 2001 From: Sam Hartman Date: Tue, 18 Jun 2019 09:02:09 -0400 Subject: [PATCH] Include /etc/pki/qemu in apparmor We already permit

Bug#930100: after upgrade to buster, qemu cannot read default spice certs

2019-06-18 Thread Guido Günther
Hi, On Thu, Jun 06, 2019 at 05:31:51PM -0400, Sam Hartman wrote: > package: libvirt-daemon-system > severity: important > version: 5.0.0-3 > > Upgrading stretch to buster. > After the upgrade, libvirt could not read /etc/pki/qemu/server-cert.pem > and server-key.pem. > > This is because of the

Bug#930100: after upgrade to buster, qemu cannot read default spice certs

2019-06-06 Thread Sam Hartman
package: libvirt-daemon-system severity: important version: 5.0.0-3 Upgrading stretch to buster. After the upgrade, libvirt could not read /etc/pki/qemu/server-cert.pem and server-key.pem. This is because of the apparmor profile. I think that's the default place where you're supposed to put