From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:43184)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <tcminyard@gmail.com>) id 1YlOt8-0007Vn-G8
	for qemu-devel@nongnu.org; Thu, 23 Apr 2015 17:42:27 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <tcminyard@gmail.com>) id 1YlOt4-0004Rx-6g
	for qemu-devel@nongnu.org; Thu, 23 Apr 2015 17:42:26 -0400
Received: from mail-ie0-x22d.google.com ([2607:f8b0:4001:c03::22d]:36405)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <tcminyard@gmail.com>) id 1YlOt4-0004Rt-2B
	for qemu-devel@nongnu.org; Thu, 23 Apr 2015 17:42:22 -0400
Received: by iebrs15 with SMTP id rs15so71159964ieb.3
	for <qemu-devel@nongnu.org>; Thu, 23 Apr 2015 14:42:21 -0700 (PDT)
Sender: Corey Minyard <tcminyard@gmail.com>
Message-ID: <55396736.2090500@acm.org>
Date: Thu, 23 Apr 2015 16:42:14 -0500
From: Corey Minyard <minyard@acm.org>
MIME-Version: 1.0
References: <CAH6UTCEd3=owGb8-i9JZRa7ZVWHQaNAMCQ_OE3hf9SZuigxbKA@mail.gmail.com>	<553824D5.4050908@acm.org>	<CAH6UTCF2+-Vp=xr=9y8L0k39BAuMZi1wuU6znecMTiskNXSuTA@mail.gmail.com>
	<CAH6UTCFsNSQF96d0rzBdzujkFZUpJUmCjv1+WBA4RExpxeR2JA@mail.gmail.com>
In-Reply-To: <CAH6UTCFsNSQF96d0rzBdzujkFZUpJUmCjv1+WBA4RExpxeR2JA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] Add an IPMI device to qemu
Reply-To: minyard@acm.org
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Noel Burton-Krahn <noel@pistoncloud.com>
Cc: qemu-devel@nongnu.org

On 04/22/2015 07:25 PM, Noel Burton-Krahn wrote:
> OK, I've build qemu and openipmi.  I'm simulating a system where a
> central control node boots from USB, then uses IPMI to boot a cluster
> of slave nodes and provisions them by tftpboot.  If I understand
> correctly, I'll be running one ipmi_sim per slave node, and my control
> node will tell that to boot a qemu instance for each slave.  Sounds
> good so far?

Yes, that is correct.

>
> The sample lan.conf has two sections started by set_working_mc 0x20
> and set_working_mc 0x30.  Is that for configuring multiple ipmi
> simulators in a single config file?
>

That is just for testing, really.  IPMI supports configurations with
multiple management controllers, say if you put a management controller
in a power supply that just managed that device.

However, you should be able to manage multiple VMs from a single IPMI
simulator.  Create an MC for each VM and set it up, and send the chassis
management commands to the individual MC.  You can use the "-t" option
of ipmitool to set the particular MC you are addressing.

-corey

-corey