On Thu, 2020-03-05 at 09:57 +, Daniel P. Berrangé wrote:
> On Thu, Mar 05, 2020 at 10:06:53AM +0100, Andrea Bolognani wrote:
> > On Fri, 2020-02-28 at 16:56 +0100, Michal Privoznik wrote:
> > > +++ b/src/qemu/qemu_shim.c
> > > @@ -150,6 +150,7 @@ int main(int argc, char **argv)
> > >
On Thu, Mar 05, 2020 at 10:06:53AM +0100, Andrea Bolognani wrote:
> On Fri, 2020-02-28 at 16:56 +0100, Michal Privoznik wrote:
> > I've found that if my virtlogd is socket activated but the daemon
> > doesn't run yet, then the virt-qemu-run is killed right after it
> > tries to start the domain.
On Fri, 2020-02-28 at 16:56 +0100, Michal Privoznik wrote:
> I've found that if my virtlogd is socket activated but the daemon
> doesn't run yet, then the virt-qemu-run is killed right after it
> tries to start the domain. The problem is that because the default
> setting is to use virtlogd, the
I've found that if my virtlogd is socket activated but the daemon
doesn't run yet, then the virt-qemu-run is killed right after it
tries to start the domain. The problem is that because the default
setting is to use virtlogd, the domain create code tries to
connect to virtlogd socket, which in
