![]() | Software: Computing Template‑class | |||||||||
|
I think it is somewhat unfair and misleading to have Citrix XenClient and Citrix XenServer listed, but not Xen. These are not all exactly the same thing, and in particular, Xen per se is essentially independent of Citrix now. The list as it stands, I feel, gives too much credit to Citrix and not enough to the people who work on Xen. At the same time, I recognize that it's undesirable to have clutter and redundancy in these lists. Thoughts? ProfStevie ( talk) 22:04, 24 April 2013 (UTC)
I don't really think PearPC should qualify as “virtualization”, because it's an emulator. I suppose the lines are blurring with regard to this, but I view “runs an architecture on another architecture” as definitively emulation, rather than virtualization. I'm one of the principle developers, so I don't feel comfortable just bulldozing my opinion on the matter into the template. But I have never though of PearPC as a virtualizer… -- Puellanivis ( talk) 23:12, 27 July 2016 (UTC)
CoreOS is the name of a company, and its main product (which I assume is meant to be referenced here) is Container Linux. But Container Linux is just a bare Linux, engineered from scratch for containerization. I think we should replace "CoreOS" by "rkt", witch is an alternative to Docker, meant to be based on Container Linux. -- Galeop ( talk) 12:38, 14 September 2017 (UTC)
Should bhyve be moved under Independent, as it supports many different types of guests?
-- KJ4IPS ( talk) 17:19, 28 December 2017 (UTC)
Hey, everyone. 😊 I'm having a little bit of trouble understanding the subgroups of the "OS-level virtualization". Right now, they are "OS implementation", "Containers", "Kernel features" and "Orchestration". "OS implementation" is the most troublesome. Its name implies it is something that OS implements, in which case it begs the question: "What's the difference between 'OS implmentation' and 'Kernel features'?" Flowing dreams ( talk) 07:07, 17 August 2019 (UTC)
![]() | Software: Computing Template‑class | |||||||||
|
I think it is somewhat unfair and misleading to have Citrix XenClient and Citrix XenServer listed, but not Xen. These are not all exactly the same thing, and in particular, Xen per se is essentially independent of Citrix now. The list as it stands, I feel, gives too much credit to Citrix and not enough to the people who work on Xen. At the same time, I recognize that it's undesirable to have clutter and redundancy in these lists. Thoughts? ProfStevie ( talk) 22:04, 24 April 2013 (UTC)
I don't really think PearPC should qualify as “virtualization”, because it's an emulator. I suppose the lines are blurring with regard to this, but I view “runs an architecture on another architecture” as definitively emulation, rather than virtualization. I'm one of the principle developers, so I don't feel comfortable just bulldozing my opinion on the matter into the template. But I have never though of PearPC as a virtualizer… -- Puellanivis ( talk) 23:12, 27 July 2016 (UTC)
CoreOS is the name of a company, and its main product (which I assume is meant to be referenced here) is Container Linux. But Container Linux is just a bare Linux, engineered from scratch for containerization. I think we should replace "CoreOS" by "rkt", witch is an alternative to Docker, meant to be based on Container Linux. -- Galeop ( talk) 12:38, 14 September 2017 (UTC)
Should bhyve be moved under Independent, as it supports many different types of guests?
-- KJ4IPS ( talk) 17:19, 28 December 2017 (UTC)
Hey, everyone. 😊 I'm having a little bit of trouble understanding the subgroups of the "OS-level virtualization". Right now, they are "OS implementation", "Containers", "Kernel features" and "Orchestration". "OS implementation" is the most troublesome. Its name implies it is something that OS implements, in which case it begs the question: "What's the difference between 'OS implmentation' and 'Kernel features'?" Flowing dreams ( talk) 07:07, 17 August 2019 (UTC)