Hello all, On 2013/05/09, at 7:54, Juergen Schoenwaelder <[email protected]> wrote:
> I do not think the MIB module makes any assumptions that make it > specific to type 1 or type 2 hypervisors and reading the wiki page, it > seems the boundary between the two types is somewhat fuzzy anyway. I also don't think we need to distinguish type 1 and 2 in the draft. Both types can cover the information items defined in our MIB draft. This discussion reminds me of one another topic, a container, such as LXC. It is a kind of virtualization system well deployed recently, but we don't consider the type deeply at this moment in the draft. In my opinion, I want to put the third type of virtualization monitor system aside, since it has a slightly different properties compared to the type 1 and 2 monitors. --- Keiichi SHIMA (島 慶一) WIDE project <[email protected]> Research Laboratory, IIJ Innovation Institute, Inc <[email protected]> On 2013/05/09, at 7:54, Juergen Schoenwaelder <[email protected]> wrote: > Thanks. > > I do not think the MIB module makes any assumptions that make it > specific to type 1 or type 2 hypervisors and reading the wiki page, it > seems the boundary between the two types is somewhat fuzzy anyway. > > One of the goals is to allow implementation based on libvirt and I > leave it as an exercise to the readers to classify the virtualization > systems supported by libvirt as type 1 or type 2. ;-) > > http://libvirt.org/ > > /js > > On Wed, May 08, 2013 at 11:36:37AM -0400, Black, David wrote: >> A type 1 hypervisor is effectively an Operating System - it runs directly on >> the hardware. >> A type 2 hypervisor is effectively an application - it runs on an OS that >> runs on hardware. >> >> More explanation and diagrams here: https://en.wikipedia.org/wiki/Hypervisor >> >> Thanks, >> --David >> >>> -----Original Message----- >>> From: [email protected] [mailto:[email protected]] On Behalf Of >>> Juergen Schoenwaelder >>> Sent: Wednesday, May 08, 2013 3:42 AM >>> To: Tina TSOU >>> Cc: [email protected] >>> Subject: Re: [OPSAWG] FW: vm mib notifications >>> >>> On Tue, May 07, 2013 at 08:31:20PM +0000, Tina TSOU wrote: >>> >>>> Based on the feedback I got from some readers, I think we need to >>>> clarify whether this draft supports only type 1 hypervisor (directly >>>> on bear metal) or if it does type 2 hypervisor (indirectly) as well, >>>> and if the draft was written with both types of hypervisors. >>> >>> Tina, >>> >>> can you please clarify what you mean by type 1 hypervisor (directly on >>> bear metal) or if it does type 2 hypervisor (indirectly)? >>> >>> /js >>> >>> -- >>> Juergen Schoenwaelder Jacobs University Bremen gGmbH >>> Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany >>> Fax: +49 421 200 3103 <http://www.jacobs-university.de/> >>> _______________________________________________ >>> OPSAWG mailing list >>> [email protected] >>> https://www.ietf.org/mailman/listinfo/opsawg >> > > -- > Juergen Schoenwaelder Jacobs University Bremen gGmbH > Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany > Fax: +49 421 200 3103 <http://www.jacobs-university.de/> > _______________________________________________ > OPSAWG mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/opsawg _______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
