From: Anthony Liguori <anthony@codemonkey.ws>
To: minyard@acm.org
Cc: qemu-devel <qemu-devel@nongnu.org>,
Corey Minyard <tcminyard@gmail.com>,
kvm@vger.kernel.org, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] Adding an IPMI BMC device to KVM
Date: Mon, 07 May 2012 18:17:40 -0500 [thread overview]
Message-ID: <4FA85814.3080906@codemonkey.ws> (raw)
In-Reply-To: <4FA80F71.30209@acm.org>
On 05/07/2012 01:07 PM, Corey Minyard wrote:
> I think we are getting a little out of hand here, and we are mixing up concepts :).
>
> There are lots of things IPMI *can* do (including serial access, VGA snooping,
> LAN access, etc.) but I don't see any value it that. The main thing here is to
> emulate the interface to the guest. OOB management is really more appropriately
> handled with libvirt. How the BMC integrates into the hardware varies a *lot*
> between systems, but it's really kind of irrelevant. (Well, almost irrelevant,
> BMCs can provide a direct I2C messaging capability, and that may matter.)
>
> A guest can have one (or more) of a number of interfaces (that are all fairly
> bad, unfortunately). The standard ones are called "KCS", "BT" and "SMIC" and
> they generally are directly on the ISA bus, but are in memory on non-x86 boxes
> (and on some x86 boxes) and sometimes on the PCI bus. Some systems also have
> interfaces over I2C, but that hasn't really caught on. Others have interfaces
> over serial ports, and that unfortunately has caught on in the ATCA world. And
> there are at least 3 different basic types of serial port interfaces with
> sub-variants :(. I'm not sure what the USB rndis device is, but I'll look at it.
> But there is no IPMI over USB.
USB rndis == USB network adapater. It's just seen by the machine as IPMI over LAN.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2012-05-07 23:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4FA429BA.3040006@acm.org>
2012-05-06 13:11 ` [Qemu-devel] Adding an IPMI BMC device to KVM Avi Kivity
2012-05-06 14:35 ` Anthony Liguori
2012-05-06 14:39 ` Avi Kivity
2012-05-07 14:30 ` Anthony Liguori
2012-05-07 14:44 ` Avi Kivity
2012-05-07 14:55 ` Anthony Liguori
2012-05-07 15:11 ` Avi Kivity
2012-05-07 15:21 ` Anthony Liguori
2012-05-07 18:07 ` Corey Minyard
2012-05-07 19:45 ` Dave Allan
2012-05-07 20:47 ` Corey Minyard
2012-05-07 23:17 ` Anthony Liguori [this message]
2012-05-18 13:08 ` Stefan Hajnoczi
2012-05-18 14:57 ` Corey Minyard
2012-05-18 15:01 ` 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=4FA85814.3080906@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=minyard@acm.org \
--cc=qemu-devel@nongnu.org \
--cc=tcminyard@gmail.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;
as well as URLs for NNTP newsgroup(s).