Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ubuntu: Don't use LTS Hardware Enablement Stack #529

Closed
legal90 opened this issue Feb 1, 2016 · 6 comments
Closed

Ubuntu: Don't use LTS Hardware Enablement Stack #529

legal90 opened this issue Feb 1, 2016 · 6 comments
Assignees
Labels
Type: Enhancement Adds new functionality.

Comments

@legal90
Copy link
Contributor

legal90 commented Feb 1, 2016

Was originally reported by @byronclark here: Parallels/vagrant-parallels#247

The current Parallels Ubuntu 14.04 boxes use the LTS Hardware Enablement Stack (https://wiki.ubuntu.com/Kernel/LTSEnablementStack).
Usually this wouldn't be a big issue, but there's a fairly nasty bug that affects NFS and the install(1) command: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1445664.
I'd love to see these boxes built without the LTS Hardware Enablement Stack as recommended by Ubuntu for cloud and virtual images.

To Bento maintainers: What do you think about it? Is it reasonable to disable "LTS Hardware Enablement Stack" in bento templates for Ubuntu?

@yzl
Copy link

yzl commented Feb 3, 2016

I am 👍 with not using the LTS Hardware Enablement Stack going forward.

@tas50
Copy link
Contributor

tas50 commented Feb 4, 2016

We should probably disable it since the AWS AMIs don't use it. You'd be testing on a significantly different host than what you'd be using in prod if you were on AWS.

@cheeseplus
Copy link
Contributor

I'm down with the change

@sethvargo
Copy link
Contributor

This seems reasonable to me

@cheeseplus
Copy link
Contributor

Seems we're now being bit by this with specifically VMware tools and it appears the only way to disable this is to start from an older image and upgrade. It's less than ideal but it may be the only solution.

@cheeseplus
Copy link
Contributor

It seems that the only way to get non-HWE kernels is to start with older releases and upgrade all the way through - this is pretty lame on Canonical's part but I think that is how we best address this unfortunately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Enhancement Adds new functionality.
Projects
None yet
Development

No branches or pull requests

6 participants