Yes, training implementations and courses can teach whatever they want, agreed.
I just wanted to note that, AFAIK, LPI objectives and exams cover only open source, with a preference for Upstream built-in and not conflicting (e.g., kernel.org). So in the case of 'guest' (e.g., 102.6), that would mean what is in kernel.org or compatible by default, let alone nothing that would be incompatible (technical or licensing). The only things I've seen, and someone can correct me if I'm wrong, that are an issue are 'host' modules, not 'guess,' and GPLv2 incompatible VirtualBox Extensions for 'guests.' - bjs P.S. Maybe the objective should be named "Linux kernel 'guest' support software (GPLv2 compatible)'? On Mon, Dec 31, 2018, 06:41 Fabian Thorns <[email protected] wrote: > Hi Segrio, Hi Bryan, > > when Linux runs as a guest operating system in a VM, it can interact with > the hypervisor in multiple ways. This could be pure paravirtualization (as > in Xen), paravirtualized drivers (as in VirtIO, VirtualBox guest > extensions, VMware tools, open-vm-tools, ...), networking protocols (as in > CIFS to mount a host share) or tools that adjust images (cloud-init, which, > again can be integrated with the 'cloud' in numerous ways). Likewise, when > Linux acts as a hypervisor, it must provide the respective counterparts and > access specific system resources, such as the kvm devices (which, e.g., can > block VirtualBox when a KVM instance is already running) or a cloud-init > disk. The term "extension" is intended to cover all of these interfaces > without being too specific whether it is a kernel module, a device, an API, > ... . As Bryan pointed out, this is not about knowing the details of a > specific implementation, it is about knowing that they exist and knowing > how to deal with this kind of extensions, for example, when migrating a VM > from one hypervisor to another. > > I wouldn't worry too much about licensing here. The objective is weight 1, > so it is about the general concepts, not about a specific hypervisor / > cloud implementation. In a training scenario it might be worth to show the > benefits of leveraging guest extensions, demonstrating how device names > change when starting the same VM image in a different hypervisor, and maybe > investigating the situation in an IaaS instance in your favorite cloud. > > If you have an idea for a better wording, we can put add it as a change > consideration for the next update. > > Wishing you all great new year's eve parties, > > Fabian > > On Mon, Dec 31, 2018 at 2:13 AM Sergio Belkin <[email protected]> wrote: > >> Hi folks >> >> I've read and re-read the new objectives and some kind of wording it's >> confusing for me. For example, what does mean: >> "Understand Linux extensions which integrate Linux with a virtualization >> product." (102.6 >> https://www.lpi.org/our-certifications/exam-101-objectives) >> >> I guess that is talking about kvm and its integration with qemu, is that >> right? >> >> Also it could be interesting be aware of conflicts between kvm and >> virtualbox. >> >> Please tell me if I understood well the objective. >> >> Thanks in advance. >> >> -- >> -- >> Sergio Belkin >> LPIC-2 Certified - http://www.lpi.org >> _______________________________________________ >> lpi-examdev mailing list >> [email protected] >> http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev > > > > -- > Fabian Thorns <[email protected]> GPG: F1426B12 > Director of Certification Development, Linux Professional Institute > _______________________________________________ > lpi-examdev mailing list > [email protected] > http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
_______________________________________________ lpi-examdev mailing list [email protected] http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
