On 08/01/2018 06:47 AM, Peter Krempa wrote:
> On Wed, Aug 01, 2018 at 12:40:14 +0200, Michal Privoznik wrote:
>> On 07/31/2018 07:19 PM, Ján Tomko wrote:
>>> And I'm still unsure about leaving in
>>> commit 55ce65646348884656fd7bf3f109ebf8f7603494
>>> qemu: Use the correct vm def on cold
On Wed, Aug 01, 2018 at 01:10:08PM +0100, Daniel P. Berrangé wrote:
> On Wed, Aug 01, 2018 at 01:41:48PM +0200, Bjoern Walk wrote:
> > Daniel P. Berrangé [2018-08-01, 11:51AM +0100]:
> > > On Tue, Jul 31, 2018 at 03:54:43PM +0200, Bjoern Walk wrote:
> > > > Bjoern Walk [2018-07-31, 03:16PM
On Wed, Aug 01, 2018 at 01:41:48PM +0200, Bjoern Walk wrote:
> Daniel P. Berrangé [2018-08-01, 11:51AM +0100]:
> > On Tue, Jul 31, 2018 at 03:54:43PM +0200, Bjoern Walk wrote:
> > > Bjoern Walk [2018-07-31, 03:16PM +0200]:
> > > > I have not yet had the time to figure out what goes wrong, any
Daniel P. Berrangé [2018-08-01, 11:51AM +0100]:
> On Tue, Jul 31, 2018 at 03:54:43PM +0200, Bjoern Walk wrote:
> > Bjoern Walk [2018-07-31, 03:16PM +0200]:
> > > I have not yet had the time to figure out what goes wrong, any ideas are
> > > welcome.
> >
> > Ah, classic. The mocked
On 07/31/2018 07:19 PM, Ján Tomko wrote:
> And I'm still unsure about leaving in
> commit 55ce65646348884656fd7bf3f109ebf8f7603494
> qemu: Use the correct vm def on cold attach
> https://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=55ce6564634
> Which means attach-device --live --config will
On 08/02/2018 03:57 AM, Peter Krempa wrote:
> On Wed, Aug 01, 2018 at 17:44:56 -0400, John Ferlan wrote:
>> On 08/01/2018 04:44 PM, Laine Stump wrote:
>
> [...]
>
>>> At any rate, there is no perfect solution in sight for the current
>>> release, so the question is whether the new (bad)
On Wed, Aug 01, 2018 at 17:44:56 -0400, John Ferlan wrote:
> On 08/01/2018 04:44 PM, Laine Stump wrote:
[...]
> > At any rate, there is no perfect solution in sight for the current
> > release, so the question is whether the new (bad) behavior is better or
> > worse than the old (also bad)
On 08/01/2018 04:44 PM, Laine Stump wrote:
> (Let's see now which people were the ones who believe it's a huge
> insult to Cc them in list replies, and which are the ones who appreciate
> the Cc and use it as a flag to raise the visibility of the message in
> their mail client . ?.
(Let's see now which people were the ones who believe it's a huge
insult to Cc them in list replies, and which are the ones who appreciate
the Cc and use it as a flag to raise the visibility of the message in
their mail client . ?. Ah, I give up, just leaving in the Cc's
and let the
On 08/01/2018 12:47 PM, Peter Krempa wrote:
> On Wed, Aug 01, 2018 at 12:40:14 +0200, Michal Privoznik wrote:
>> On 07/31/2018 07:19 PM, Ján Tomko wrote:
>>> And I'm still unsure about leaving in
>>> commit 55ce65646348884656fd7bf3f109ebf8f7603494
>>> qemu: Use the correct vm def on cold attach
On Tue, Jul 31, 2018 at 03:54:43PM +0200, Bjoern Walk wrote:
> Bjoern Walk [2018-07-31, 03:16PM +0200]:
> > I have not yet had the time to figure out what goes wrong, any ideas are
> > welcome.
>
> Ah, classic. The mocked virRandomBytes function is not endian-agnostic,
> generating a different
On Wed, Aug 01, 2018 at 12:40:14 +0200, Michal Privoznik wrote:
> On 07/31/2018 07:19 PM, Ján Tomko wrote:
> > And I'm still unsure about leaving in
> > commit 55ce65646348884656fd7bf3f109ebf8f7603494
> > qemu: Use the correct vm def on cold attach
> >
On Tue, Jul 31, 2018 at 19:19:33 +0200, Ján Tomko wrote:
> On Tue, Jul 31, 2018 at 12:19:28PM +0800, Daniel Veillard wrote:
> > It is out, tagged in git and with signed tarball and rpms at the
> > usual place:
> >
> > ftp://libvirt.org/libvirt/
> >
> > in my limited testing it works but we
On Tue, Jul 31, 2018 at 12:19:28PM +0800, Daniel Veillard wrote:
It is out, tagged in git and with signed tarball and rpms at the
usual place:
ftp://libvirt.org/libvirt/
in my limited testing it works but we have that pending issue
raised by Andrea. worse case someone reverse the patches
Michal Privoznik [2018-07-31, 04:10PM +0200]:
> On 07/31/2018 03:54 PM, Bjoern Walk wrote:
> > Bjoern Walk [2018-07-31, 03:16PM +0200]:
> >> I have not yet had the time to figure out what goes wrong, any ideas are
> >> welcome.
> >
> > Ah, classic. The mocked virRandomBytes function is not
On 07/31/2018 03:54 PM, Bjoern Walk wrote:
> Bjoern Walk [2018-07-31, 03:16PM +0200]:
>> I have not yet had the time to figure out what goes wrong, any ideas are
>> welcome.
>
> Ah, classic. The mocked virRandomBytes function is not endian-agnostic,
> generating a different interface name as
Bjoern Walk [2018-07-31, 03:16PM +0200]:
> I have not yet had the time to figure out what goes wrong, any ideas are
> welcome.
Ah, classic. The mocked virRandomBytes function is not endian-agnostic,
generating a different interface name as expected by the test.
Bjoern
--
IBM Systems
Linux on
Bjoern Walk [2018-07-31, 02:21PM +0200]:
> Daniel Veillard [2018-07-31, 12:19PM +0800]:
> >It is out, tagged in git and with signed tarball and rpms at the
> > usual place:
> >
> >ftp://libvirt.org/libvirt/
> >
> > in my limited testing it works but we have that pending issue
> >
Daniel Veillard [2018-07-31, 12:19PM +0800]:
>It is out, tagged in git and with signed tarball and rpms at the
> usual place:
>
>ftp://libvirt.org/libvirt/
>
> in my limited testing it works but we have that pending issue
> raised by Andrea. worse case someone reverse the patches and
>
19 matches
Mail list logo
