public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Andrey Korolyov <andrey@xdel.ru>, kvm@vger.kernel.org
Subject: Re: QEMU P2P migration speed
Date: Fri, 07 Feb 2014 20:10:12 +0400	[thread overview]
Message-ID: <52F50564.20806@msgid.tls.msk.ru> (raw)
In-Reply-To: <52F4FC93.2040704@redhat.com>

07.02.2014 19:32, Paolo Bonzini wrote:
> Il 07/02/2014 14:07, Andrey Korolyov ha scritto:
>> Ok, I will do, but looks like libvirt version(1.0.2) in not relevant -
>> it meets criteria set by debian packagers
> 
> Then Debian's qemu packaging it's wrong, QEMU 1.6 or newer should conflict
> with libvirt <1.2.0.

I've no idea when qemu breaks libvirt.  I found out - just by a chance -
that qemu 1.3+ breaks libvirt <1.0, and I stated this in the deps.
But the thing that 1.6 requires libvirt 1.2 is news for me.

I'll add this requiriment to the debian package.

At any rate, there's no libvirt 1.0 in debian.  Current stable has 0.9,
and current testing has 1.2.1, and this version is also available in
backports for stable.  1.2 was the first version past 0.9 which were
backproted to stable.  There's no other versions of libvirt in debian.

So whomever installed that mess did that on their own, it is definitely
not supported on debian ;)

Thanks,

/mjt

>> and again, 'broken state' is
>> not relevant to the libvirt state history, it more likely to be qemu/kvm
>> problem.
> 
> It is relevant, qemu introduced a new migration status before "active" 
> ("setup") and libvirt doesn't recognize it.  That's why you need at
> least 1.2.0.
> 
> Paolo
> 


  reply	other threads:[~2014-02-07 16:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-04 17:06 QEMU P2P migration speed Andrey Korolyov
2014-02-05  7:27 ` Paolo Bonzini
2014-02-05 10:46   ` Andrey Korolyov
2014-02-05 15:15     ` Paolo Bonzini
2014-02-06 13:40       ` Andrey Korolyov
2014-02-07  8:14         ` Paolo Bonzini
2014-02-07 13:07           ` Andrey Korolyov
2014-02-07 15:26             ` Paolo Bonzini
2014-02-07 15:32             ` Paolo Bonzini
2014-02-07 16:10               ` Michael Tokarev [this message]
2014-02-08 11:33               ` Andrey Korolyov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52F50564.20806@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=andrey@xdel.ru \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox