Hi Seth, for Vivid you can use the trusty package, anyway, I added a fake changelog entry and uploaded on the same ppa.
>Trusty sounds difficult. There are multiple supported kernels for 14.04 LTS; >3.13 kernel in 14.04.1 >3.16 kernel from 14.04.2 (linux-generic-lts-utopic) >3.19 kernel from 14.04.3 (linux-generic-lts-vivid) >4.2 kernel (linux-generic-lts-wily). >All of these are currently supported; when 16.04 LTS is released, I think >then only the original 3.13 kernel and the (probably) 4.4 kernel from >16.04 LTS will be supported. > >I think VB hasn't worked for anyone on the HWE kernels; will this update >mean VB will only work on the newest HWE kernels and break for users >still on the original 3.13 kernels? well I think we have no issues there :) precise is different from trusty :D 4.3 is fine, the problem is virtualbox 4.1.x (because the feature has been backported only to 4.2.x+ releases) precise came with a kernel without that feature, and people who used an HWE kernel found their virtualbox broken (with the affected cpu models). So, in precise (not trusty that is completely fine), they have a broken virtualbox, and they will continue having a broken one. Not a regression (they can use a newer virtualbox from one of my ppas if they want, but I think the sum of people that runs precise and run virtualbox, and use an hwe kernel (>=3.18 or so, when the feature has been added) and have a specific cpu model (only two models are affected), is somewhat low. anyway, this is a *regression* in the kernel, this update won't make it any worse :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1517161 Title: virtualbox SRU for CVE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1517161/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
