qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Noel Burton-Krahn <noel@pistoncloud.com>
To: Corey Minyard <minyard@acm.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Add an IPMI device to qemu
Date: Fri, 24 Apr 2015 14:57:51 -0700	[thread overview]
Message-ID: <CAH6UTCGhqOtFi6T9JuDnfbEx_Rf=n17g3yYuyafO_1r4JSDi_A@mail.gmail.com> (raw)
In-Reply-To: <55396736.2090500@acm.org>

[-- Attachment #1: Type: text/plain, Size: 2002 bytes --]

Thanks, Corey.

How does the lan_config_program in lan.conf work?  I couldn't find an
example in the OpenIPMI-2.0.21 tarball.  Our central controller expects
each node's ipmi module to dhcp for an address.  I'm trying to decide if I
need to run dhcpc on the interface that ipmi_sim runs on.  Can I just bind
ipmi_sim to an interface and let it dhcp for its address?  If not, how does
it work with lan_config_program?


FYI, In our setup, we have two networks for ipmi and data.  One control
node is connected to both networks and provides dhcp

controller       node1      node2 ...
IPMI  eth0 ----- ipmi0 ---- ipmi0
DATA  eth1 ----- eth0 ----- eth0

I'm using veth pairs with one end in a bridge for the ipmi interfaces and
tap devices for qemu simulating the nodes.

--
Noel




On Thu, Apr 23, 2015 at 2:42 PM, Corey Minyard <minyard@acm.org> wrote:

> 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
>

[-- Attachment #2: Type: text/html, Size: 2959 bytes --]

  reply	other threads:[~2015-04-24 21:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-22 21:30 [Qemu-devel] Add an IPMI device to qemu Noel Burton-Krahn
2015-04-22 22:46 ` Corey Minyard
2015-04-22 23:26   ` Noel Burton-Krahn
2015-04-23  0:25     ` Noel Burton-Krahn
2015-04-23 21:42       ` Corey Minyard
2015-04-24 21:57         ` Noel Burton-Krahn [this message]
2015-04-25  0:28           ` Corey Minyard

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='CAH6UTCGhqOtFi6T9JuDnfbEx_Rf=n17g3yYuyafO_1r4JSDi_A@mail.gmail.com' \
    --to=noel@pistoncloud.com \
    --cc=minyard@acm.org \
    --cc=qemu-devel@nongnu.org \
    /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;
as well as URLs for NNTP newsgroup(s).