Comments

126 Comments
karma

x86_64

x86_64, i5-7200U w/embedded GPU, HW model HP 850 G4, KDE, VPN IPsec, VirtualBox 6.0.4.

As far as I understand and can evaluate also rbhz 1701096 added to 5.0.9-301 works well. With 5.0.8 and 5.0.9-300, VirtualBox kernel modules did not load unless I disabled SecureBoot; with 5.0.9-301 the modules load with SecureBoot enabled again. Maybe #1701096 should be added to the list of solved bugs?

x86_64, i5-7200U w/embedded GPU, HW model HP 850 G4, KDE, VPN IPsec, VirtualBox 6.0.4.

karma

x86_64, i5-7200U w/embedded GPU, HW model HP 850 G4, KDE, VPN IPsec.

x86_64

x86_64

VM guest on VirtualBox 6.0.4 host, x86_64, i5-7200U w/embedded GPU, HW model HP 850 G4, KDE

x86_64, i5-7200U w/embedded GPU, HW model HP 850 G4, KDE, VPN IPsec, VirtualBox 6.0.4.

VM guest, x86_64, i5-7200U w/embedded GPU, HW model HP 850 G4, KDE, VPN IPsec, VirtualBox 6.0.4.

BZ#1689750 VBoxService stops with error VERR_VERSION_MISMATCH if VirtualBox server is version 6.0.4

x86_64, i5-7200U w/embedded GPU, HW model HP 850 G4, KDE, VPN IPsec. Note: VirtualBox-5.2.24-1.fc29.x86_64 does not work with any 5.0 kernel, because its out-of-the-tree kernel modules fail to compile. As far as I understand this issue is not in scope of Fedora kernel bug fixing..

x86_64, i5-7200U, KDE, IPsec VPN, VBox 5.2.24.

x86_64, i5-7200U w/embedded GPU, PC model HP850G4, multiple VM's in Virtualbox 5.2.24, IPsec VPN, KDE.

x86_64, i5-7200U w/embedded GPU, PC model HP850G4, multiple VM's in Virtualbox 5.2.24, IPsec VPN, KDE.

x86_64, i5-7200U w/embedded GPU, PC model HP850G4, Virtualbox, IPsec VPN, KDE.

x86_64, CPU i5-7200U w/embedded GPU, model HP850G4, KDE5, VirtualBox, VPN IPsec/OpenVPN

x86_64, CPU i5-7200U w/embedded GPU, model HP850G4, KDE5, VirtualBox, VPN IPsec/OpenVPN

x86_64, CPU i5-7200U w/embedded GPU, model HP850G4, KDE5, VirtualBox, VPN IPsec/OpenVPN

x86_64, i5-7200U, laptop model HP850G4, IPsec VPN, OpenVPN, KDE, VBox