Comment 18 for bug 1708315

Ok, the fix works if I'm running kernel 4.4.

$ uname -a
Linux xenial 4.4.0-101-generic #124-Ubuntu SMP Fri Nov 10 18:29:59 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

I've installed virtualbox-guest-*-hwe packages version 5.0.40-dfsg-0ubuntu1.16.04.1~16.04.4 from xenial-proposed, along with HWE packages of xorg:

$ LC_ALL=C sudo apt-get install --no-install-recommends xserver-xorg-hwe-16.04 xserver-xorg-video-all-hwe-16.04 xserver-xorg-input-all-hwe-16.04 virtualbox-guest-dkms-hwe virtualbox-guest-utils-hwe virtualbox-guest-x11-hwe

All good, the installation went fine, and after the reboot the system works fine.

--------------------------------

I have a problem with kernel from linux-generic-hwe-16.04 though (version of linux-image-4.10.0-40-generic package is 4.10.0-40.44~16.04.1). That's why I had to use --no-install-recommends option - to avoid installing that kernel.

The VM just won't boot with it. It says "loading initial ramdisk", then VirtualBox just keeps eating 100% CPU on each core, and the boot doesn't continue.

This happens with both original xorg + virtualbox-guest-* packages and with HWE xorg + virtualbox-guest-*-hwe packages. So it's either a separate bug, or something with my VirtualBox, but it's not caused by the fix for this bug. Therefore this update is good to go.