From mboxrd@z Thu Jan  1 00:00:00 1970
From: Juan Quintela <quintela@redhat.com>
Subject: KVM call minutes for 2014-02-18
Date: Tue, 18 Feb 2014 16:05:13 +0100
Message-ID: <87eh30cvh2.fsf@elfo.mitica>
Reply-To: quintela@redhat.com
Mime-Version: 1.0
Content-Type: text/plain
To: KVM devel mailing list <kvm@vger.kernel.org>,
	qemu-devel qemu-devel <qemu-devel@nongnu.org>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:13746 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1756120AbaBRPFS (ORCPT <rfc822;kvm@vger.kernel.org>);
	Tue, 18 Feb 2014 10:05:18 -0500
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>



2014-02-18
----------

* [Qemu-devel] [PATCH V17 00/11] Add support for binding guest numa
  nodes
  Any news about this? (Vinod)

* Should we change anything to get more people to sign for the call?
  There hasn't been a call in quite a long time.  Ideas? (me)

* x2apic?

-  Pending patch for cpu feature flag.
-  Should this be the default.
-  It is not for 32bits, but should it be for 64bit?
-  libvirt always use x2apic, unconditionally?
-  What happens if one side of migration uses -m <cpu_something and the
   other -m cpu_something+x2apic
-  disabling if for all old machine types
-  Use the same that hyperv flags?


* release
- No Anthony
- People happy (on happy enough) with current schedule

* Maintenance?
- How is being handling patches for the stable release?
  CC: stable@  for stable maintance.
- add documentation about what/how to send patches for stable release
- Regressions deserve a backport almost always?
- There is no stable tree public where we see what patches are being integrated?
- How can we make more people additoally to Michael to work with stable branches
- Should we change anynthing?