Am 28.07.19 um 11:29 schrieb Hans-Peter Jansen:
Am Samstag, 27. Juli 2019, 19:10:19 CEST schrieb Larry Finger:
On 7/27/19 9:57 AM, Michal Suchánek wrote:
On Sat, 27 Jul 2019 16:15:13 +0200
Michal Suchánek
wrote: On Sat, 27 Jul 2019 14:57:43 +0200
--snip--
At first glance, Stefan Seyfried's suggestion to merge the host and guest kmp packages into a single unit seems intriguing.
Well, from a power virtualbox user POV, this approach feels wrong. (Sorry, Stefan) After all, kernel modules always contain very delicate code.
Having both, the guest modules as well as the host modules installed everywhere, whether either host or guest functionality is requested, may open a couple of new issues. What happens, if, for some reason, a mix of these modules is loaded?
Nothing. Guest modules bind to pci devices only a vbox guest has and will just refuse to load or just do nothing. strolchi:~ # rpm -ql virtualbox-kmp-default /lib/modules/5.3.0-rc1-3.gc584343-default /lib/modules/5.3.0-rc1-3.gc584343-default/extra /lib/modules/5.3.0-rc1-3.gc584343-default/extra/vboxdrv.ko /lib/modules/5.3.0-rc1-3.gc584343-default/extra/vboxguest.ko /lib/modules/5.3.0-rc1-3.gc584343-default/extra/vboxnetadp.ko /lib/modules/5.3.0-rc1-3.gc584343-default/extra/vboxnetflt.ko /lib/modules/5.3.0-rc1-3.gc584343-default/extra/vboxpci.ko /lib/modules/5.3.0-rc1-3.gc584343-default/extra/vboxsf.ko /lib/modules/5.3.0-rc1-3.gc584343-default/extra/vboxvideo.ko strolchi:~ # modprobe vboxdrv strolchi:~ # modprobe vboxguest modprobe: ERROR: could not insert 'vboxguest': No such device strolchi:~ # modprobe vboxnetadp strolchi:~ # modprobe vboxnetflt strolchi:~ # modprobe vboxpci strolchi:~ # modprobe vboxsf modprobe: ERROR: could not insert 'vboxsf': No such device strolchi:~ # modprobe vboxvideo strolchi:~ # dmesg|tail -11 [88282.872682] vboxdrv: loading out-of-tree module taints kernel. [88282.873123] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel [88282.886689] vboxdrv: Found 4 processor cores [88282.906517] vboxdrv: TSC mode is Invariant, tentative frequency 2594091545 Hz [88282.906519] vboxdrv: Successfully loaded version 6.0.10_SUSE (interface 0x00290008) [88286.448086] vboxguest: PCI device not found, probably running on physical hardware. [88296.047653] VBoxNetAdp: Successfully started. [88306.518371] VBoxNetFlt: Successfully started. [88317.687230] VBoxPciLinuxInit [88317.687243] vboxpci: IOMMU not found (not registered) [88320.510137] vboxguest: PCI device not found, probably running on physical hardware.
Any chance, they interfere with each other? DoS.. Especially, the vboxfs module is one, that I don't want to see loaded on any host, that I depend on. To the contrary, I already thought of changes to make this module optional.
It will not load.
For the record, I usually add a zypper lock for the guest modules on vbox hosts.
Unnecessary, right now they conflict with vbox host modules anyway. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org