qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	Corey Minyard <tcminyard@gmail.com>,
	minyard@acm.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Adding an IPMI BMC device to KVM
Date: Sun, 06 May 2012 09:35:10 -0500	[thread overview]
Message-ID: <4FA68C1E.3070503@codemonkey.ws> (raw)
In-Reply-To: <4FA6788A.8080500@redhat.com>

On 05/06/2012 08:11 AM, Avi Kivity wrote:
> (copied qemu-devel)
>
> On 05/04/2012 10:10 PM, Corey Minyard wrote:
>>
>> Either way, is this interesting for including into KVM?
>
> Not kvm, but certainly it would make a good addition to qemu, which kvm
> then uses.
>
>> Does anyone have any
>> opinions on the possible ways to implement this?
>
> My preference would be the second alternative.  The issue you raise is a
> good one.  There are two ways we can approach it:
>
> - have the management system intercept IPMI requests, start up a qemu
> instance (if it's down), and let it handle the event.
> - change the whole system to keep a running qemu even when the guest is
> down.  This is a much larger change; it involves reducing the memory
> footprint to almost nothing when the guest is down (deallocating memory
> and threads) so it doesn't impact guest density, but it allows for other
> minor features such as wake-on-LAN and RTC alarm wakeups.

libvirt is essentially the BMC for a virtual guest.  I would suggest looking at 
implementing an IPMI interface to libvirt and exposing it to the guest through a 
USB RNDIS device.

Regards,

Anthony Liguori

>

  reply	other threads:[~2012-05-06 14:35 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 [this message]
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
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=4FA68C1E.3070503@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).