From: Corey Minyard <minyard@acm.org>
To: "Longever, Joseph" <Joseph.Longever@emc.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] QEMU IPMI support
Date: Sat, 04 Apr 2015 21:02:06 -0500 [thread overview]
Message-ID: <5520979E.2080208@acm.org> (raw)
In-Reply-To: <9C46C997A77C834C81ACBF2B3F67C31705657237D7@MX43A.corp.emc.com>
Ok, done. It's at https://github.com/cminyard/qemu on github. There
are two branches at the moment, stable-2.2-ipmi is based on the 2.2
release and will not rebase. master-ipmi-rebase will rebase on master
as it moves.
I haven't done extensive testing yet, and it has a few experimental
things, like an SMBus IPMI interface and an I2C mux device. I need to
split all that out at some point. I also need to rework the ACPI
handling to use the new code to build the ACPI tables.
Copying qemu-devel so that group knows.
Thanks,
-corey
On 04/03/2015 01:17 PM, Longever, Joseph wrote:
> Hi Corey,
>
> Yes please, setting up a git repo on git hub with IPMI support would be a tremendous help.
>
> Thank you,
> Joel
>
> -----Original Message-----
> From: Corey Minyard [mailto:tcminyard@gmail.com] On Behalf Of Corey Minyard
> Sent: Friday, April 03, 2015 2:16 PM
> To: Longever, Joseph
> Subject: Re: QEMU IPMI support
>
> On 04/01/2015 07:23 AM, Longever, Joseph wrote:
>> Hi Corey,
>>
>>
>>
>> I noticed a lot of work you had done to add IPMI/BMC emulation to QEMU
>> ... great work!
>>
>> http://sourceforge.net/p/openipmi/mailman/openipmi-developer/thread/13
>> 69865296-19584-1-git-send-email-minyard%40acm.org/#msg30911152
>>
>>
>>
>>
>> I was wondering if they were going to push those features into an
>> official QEMU release? To avoid porting the above patches over (not
>> sure which commit it's based on, 1.5.0?), would you have the patch
>> set to support the latest stable QEMU version? I would like to use
>> OpenIPMI's lanserv to spawn a QEMU KVM with IPMI char device enabled,
>> however I think I need your patches to enable the device in QEMU.
>>
>>
>>
>> Any suggestions or help is very much appreciated.
>>
>>
>>
>> Thanks,
>>
>> Joel
>>
>>
>>
> I'm not sure when I can get this pushed in. It's really more up to the qemu maintainers, and they are pretty busy with bigger stuff. Unless Redhat wants changes, which is how the qemu-char changes I needed for IPMI support got into the release.
>
> I can set up a git repository on github. Would that help?
>
> -corey
next parent reply other threads:[~2015-04-05 2:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9C46C997A77C834C81ACBF2B3F67C31705657234BF@MX43A.corp.emc.com>
[not found] ` <551ED8C5.7020003@acm.org>
[not found] ` <9C46C997A77C834C81ACBF2B3F67C31705657237D7@MX43A.corp.emc.com>
2015-04-05 2:02 ` Corey Minyard [this message]
2015-04-07 12:24 ` [Qemu-devel] QEMU IPMI support Longever, Joseph
2015-04-07 12:43 ` Corey Minyard
2015-04-07 12:51 ` Longever, Joseph
2015-04-07 15:05 ` Longever, Joseph
2015-04-07 12:31 ` Corey Minyard
[not found] <CAGm6yaQdByfFu=8qv4+tt01jE=uDupFzDcXUBghFA0YJaRn1cQ@mail.gmail.com>
[not found] ` <20131105135305.GA3696@redhat.com>
2013-11-05 16:43 ` [Qemu-devel] Qemu " Bret Ketchum
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=5520979E.2080208@acm.org \
--to=minyard@acm.org \
--cc=Joseph.Longever@emc.com \
--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).