From: Gleb Natapov <gleb@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: minyard@acm.org, "Marcel Apfelbaum" <marcel.a@redhat.com>,
seabios@seabios.org, qemu-devel@nongnu.org,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [SeaBIOS] [PATCH] don't expose pvpanic device in the UI
Date: Tue, 6 Aug 2013 15:17:37 +0300 [thread overview]
Message-ID: <20130806121737.GZ8218@redhat.com> (raw)
In-Reply-To: <20130806120552.GA14396@redhat.com>
On Tue, Aug 06, 2013 at 03:05:52PM +0300, Michael S. Tsirkin wrote:
> On Tue, Aug 06, 2013 at 03:00:06PM +0300, Gleb Natapov wrote:
> > On Tue, Aug 06, 2013 at 01:23:49PM +0200, Andreas Färber wrote:
> > > Am 06.08.2013 13:00, schrieb Gleb Natapov:
> > > > On Tue, Aug 06, 2013 at 12:35:10PM +0200, Andreas Färber wrote:
> > > >> I wonder if IPMI might be such an alternative in the future, in which
> > > >> case we should come up with some way to fully disable pvpanic device
> > > >> creation. CC'ing Corey.
> > > >>
> > > > IPMI was considered, to complicated for what was needed.
> > >
> > > Sorry? There's nothing wrong with going for pvpanic as a simple
> > > implementation.
> > >
> > Sure, why "sorry" then? :) PV has its benefits.
>
> PV always seems easier. It sometimes becomes a maintainance problem
> down the way though.
>
If it is modelled as proper device, why? What PV devices we have that are pain?
> > > There have been IPMI patchsets on qemu-devel though, and SUSE will be
> > > investigating adding some IPMI support too (not sure if identical to the
> > > scope of those patchsets), whether IPMI is complicated or not. It's a
> > > standard present on physical servers, facilitating unified management of
> > > virtual and physical servers, and there's OpenIPMI as implementation.
> > >
> > Of course, there is nothing wrong with implementing IPMI either. Many
> > problems that IPMI solves are much simpler to solve in virtualized
> > environment with management software and pvpanic closes one gap
> > between what IPMI provides and virtual machine management can do.
> >
> > > My point was, there may be alternative, non-PV implementations to suck
> > > such information out of a guest, IPMI being one example of a management
> > > interface that exists for physical servers. So it's not necessarily
> > > black-or-white, but choices similar to virtio vs. IDE vs. AHCI vs. SCSI.
> > >
> > pvpanic not meant to replace IPMI though.
>
> But will you want pvpanic if you have IPMI?
>
Why not? They report to different components.
--
Gleb.
next prev parent reply other threads:[~2013-08-06 12:17 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1375688843-19573-1-git-send-email-hutao@cn.fujitsu.com>
[not found] ` <20130805081055.GA356@redhat.com>
[not found] ` <20130805081617.GB2258@redhat.com>
[not found] ` <20130805091826.GA877@redhat.com>
[not found] ` <20130805092044.GH2258@redhat.com>
[not found] ` <20130805150333.GC877@redhat.com>
[not found] ` <20130805160421.GB15901@redhat.com>
2013-08-05 18:32 ` [Qemu-devel] [SeaBIOS] [PATCH] don't expose pvpanic device in the UI Michael S. Tsirkin
2013-08-06 7:34 ` Gleb Natapov
2013-08-06 8:03 ` Vadim Rozenfeld
2013-08-06 8:05 ` Gleb Natapov
2013-08-06 8:14 ` Vadim Rozenfeld
2013-08-06 8:38 ` Gleb Natapov
[not found] ` <51FF6A79.9060603@redhat.com>
[not found] ` <703333176.9515483.1375697447963.JavaMail.root@redhat.com>
[not found] ` <20130805151723.GF877@redhat.com>
[not found] ` <1970367422.9695773.1375718517492.JavaMail.root@redhat.com>
[not found] ` <20130805161833.GA4244@redhat.com>
[not found] ` <51FFD6CE.5090302@redhat.com>
[not found] ` <20130805182628.GC4244@redhat.com>
[not found] ` <20130806072152.GK10891@redhat.com>
2013-08-06 8:33 ` Michael S. Tsirkin
2013-08-06 8:36 ` Gleb Natapov
2013-08-06 8:45 ` Andreas Färber
2013-08-06 9:15 ` Michael S. Tsirkin
2013-08-06 9:20 ` Gleb Natapov
2013-08-06 10:04 ` Michael S. Tsirkin
2013-08-06 17:53 ` Andreas Färber
2013-08-06 9:56 ` Markus Armbruster
2013-08-06 10:11 ` Michael S. Tsirkin
2013-08-06 9:21 ` Michael S. Tsirkin
2013-08-06 9:32 ` Gleb Natapov
2013-08-06 10:19 ` Michael S. Tsirkin
2013-08-06 10:44 ` Gleb Natapov
2013-08-06 11:03 ` Andreas Färber
2013-08-06 11:16 ` Gleb Natapov
2013-08-06 11:48 ` Markus Armbruster
2013-08-06 12:03 ` Gleb Natapov
2013-08-06 12:09 ` Michael S. Tsirkin
2013-08-06 12:45 ` Andreas Färber
2013-08-07 8:17 ` Stefan Hajnoczi
2013-08-06 11:54 ` Gerd Hoffmann
2013-08-06 12:08 ` Gleb Natapov
2013-08-06 10:35 ` Andreas Färber
2013-08-06 11:00 ` Gleb Natapov
2013-08-06 11:23 ` Andreas Färber
2013-08-06 12:00 ` Gleb Natapov
2013-08-06 12:02 ` Gerd Hoffmann
2013-08-06 12:05 ` Michael S. Tsirkin
2013-08-06 12:17 ` Gleb Natapov [this message]
2013-08-06 17:22 ` Andreas Färber
2013-08-06 12:08 ` Michael S. Tsirkin
2013-08-06 12:19 ` Gleb Natapov
2013-08-06 9:26 ` Hu Tao
2013-08-06 9:29 ` Gleb Natapov
2013-08-06 10:13 ` Michael S. Tsirkin
2013-08-06 10:14 ` Gleb Natapov
2013-08-06 10:23 ` Michael S. Tsirkin
2013-08-06 10:28 ` Gleb Natapov
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=20130806121737.GZ8218@redhat.com \
--to=gleb@redhat.com \
--cc=afaerber@suse.de \
--cc=kraxel@redhat.com \
--cc=marcel.a@redhat.com \
--cc=minyard@acm.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.