On Fri, May 17, 2019 at 09:56:56 +0200, Thomas Stein wrote:
> On 2019-05-17 09:36, Peter Krempa wrote:
> > On Thu, May 16, 2019 at 17:20:05 +0200, Thomas Stein wrote:
> > > Hello all.
> >
> > Hi,
> >
> >
> > > My currently used versions: libvirt-5.2.0 and qemu-4.0.0.
> >
> > I don't think this
On 2019-05-17 09:36, Peter Krempa wrote:
On Thu, May 16, 2019 at 17:20:05 +0200, Thomas Stein wrote:
Hello all.
Hi,
My currently used versions: libvirt-5.2.0 and qemu-4.0.0.
I don't think this is a regression, but it will not hurt to ask. Is
this
a new problem which was not observed
On Thu, May 16, 2019 at 17:20:05 +0200, Thomas Stein wrote:
> Hello all.
Hi,
> My currently used versions: libvirt-5.2.0 and qemu-4.0.0.
I don't think this is a regression, but it will not hurt to ask. Is this
a new problem which was not observed before? (I'm asking because I was
messing with
On 5/16/19 10:20 AM, Thomas Stein wrote:
> Hello all.
>
> My currently used versions: libvirt-5.2.0 and qemu-4.0.0.
>
> Here is my problem. I'm struggeling since a few weeks with a strange
> behaviour by either qemu or libvirt. After a reboot of
> the hardware node the $domain.xml contains
Hello all.
My currently used versions: libvirt-5.2.0 and qemu-4.0.0.
Here is my problem. I'm struggeling since a few weeks with a strange
behaviour by either qemu or libvirt. After a reboot of
the hardware node the $domain.xml contains suddenly a backingStore
setting which was not there
