From mboxrd@z Thu Jan  1 00:00:00 1970
From: Chris Friesen <chris.friesen@genband.com>
Subject: problems starting kvm-qemu with 5+ virtual functions
Date: Wed, 11 Jul 2012 10:52:26 -0600
Message-ID: <4FFDAF4A.1050402@genband.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
To: kvm@vger.kernel.org
Return-path: <kvm-owner@vger.kernel.org>
Received: from exprod7og123.obsmtp.com ([64.18.2.24]:36043 "EHLO
	exprod7og123.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751593Ab2GKSzo (ORCPT <rfc822;kvm@vger.kernel.org>);
	Wed, 11 Jul 2012 14:55:44 -0400
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Hi,

We're running into a problem where we can't start up a single instance 
of kvm-qemu with 5 or more virtual functions (for the ethernet card) 
being passed to the guest.  It's an Intel I350 NIC if it matters.

I noticed a discussion in a thread titled "[RFC PATCH 0/2] Expose 
available KVM free memory slot count to help avoid aborts" that seemed 
to point to the hardcoded definition of KVM_MEMORY_SLOTS as being a 
possible problem, and proposed some patches to allow dynamic sizing of 
the number of memory slots.  It looks like that patch never went through 
to mainline though.

Is this likely the source of my problem?  Why didn't it ever get 
submitted to mainline.

What's the proper method of supporting 8 VFs per VM, with possibly 
several VMs?

Thanks,
Chris