-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
WIP: Adding Ubuntu 16.04 #545
Conversation
"<enter><wait><f6><esc><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs>", | ||
"<bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs>", | ||
"<bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs>", | ||
"<bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs><bs>", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Man, that's a lot of BS....heyyyoooo!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, still broken in 16.04 facepalm
VMware: image building works with latest packer release, however the imported box fails to start tested with today's daily server build (x64).
|
Is this a bug with 16.04 or something we need to work around? |
Good question. Initial setup configures the interfaces as It's clearly not working at this stage. I've also tried several kernel combos of "biosdevname" and "net.ifnames" boot arg options but without success. The only working hack for me is to run I'm not sure what causes the issue. Ubuntu, VMware Tools, packer/vagrant… I've no idea at this stage. |
by the way, exactly same with Ubuntu 15.10 on VMware Fusion 8.1 and Packer 0.10.0 |
Hrm, I'll try to confirm but I don't recall seeing the same thing - it sounds like it could still be related to https://gist.github.com/brbsix/b70413dec907906ef659 but in my testing that problem seemed to disappear. |
In my case the scheme is consistent ( Source of slot number "33" probably: https://github.com/mitchellh/packer/blob/master/builder/vmware/iso/step_create_vmx.go#L181 |
related: hashicorp/vagrant#4590 |
Overwriting the "build-time" pci slot for the ethernet interface to '32' with: diff --git i/ubuntu-16.04-amd64.json w/ubuntu-16.04-amd64.json
index 3251c0b..90f157c 100644
--- i/ubuntu-16.04-amd64.json
+++ w/ubuntu-16.04-amd64.json
@@ -108,7 +108,8 @@
"vmx_data": {
"cpuid.coresPerSocket": "1",
+ "ethernet0.pciSlotNumber": "32",
"memsize": "384",
"numvcpus": "1"
} allowed me to build, import and run the 16.04 image with test-kitchen and working default networking. vagrant@default-ubuntu-1604:~$ udevadm info -e |grep ens
P: /devices/pci0000:00/0000:00:11.0/0000:02:00.0/net/ens32
E: DEVPATH=/devices/pci0000:00/0000:00:11.0/0000:02:00.0/net/ens32
E: ID_NET_NAME_SLOT=ens32
E: INTERFACE=ens32
E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/ens32 15.10 and beyond with its new systemd infrastructure introduce a hell of new aspects to ubuntu-based systems. While this solution depends on a consistent VMWare behaviour, it doesn't require a modification to the distro or Vagrant. It would be awesome if other VMWare users (Fusion, Workstation and different versions) can verify this. I'm also pretty sure this will fix the 15.10 issue. |
If this build-time solution is not sufficient or breaks compatibility, we'll need at least some |
Any progress on this? |
@repeatedly are you asking about 16.04 boxes or fixing 15.10 vmware driver issues? |
@cheeseplus Ubuntu 16.04 boxes. |
@repeatedly 16.04 is not out yet ;) Official release date is April 21 fwiw |
@cheeseplus Ahhh, Thx. |
16.04 has been released right now |
Yep! Let's give the bento team a day or two to validate things. 🤘 |
One note - using config very similar to what's in this PR, when I try starting the VM with Vagrant/VirtualBox, I get the following error with 16.04:
(Similar to the problem mentioned with 15.10 earlier in this thread). |
@geerlingguy That is probably related to hashicorp/vagrant@0505771 |
@rickard-von-essen - partly; see geerlingguy/packer-boxes#1 (comment) for the two parts that fail when using private networking. There's an open PR to fix the interface naming support. |
This PR and the following patch works for me.
|
@geerlingguy that eth#-schema is outdated, see my comments above and 284f214 |
@rmoriz - ah, so adding For the second (ifdown bailing out), that commit (hashicorp/vagrant@0505771) fixes the problem, but it's not available in a Vagrant release yet (when, oh when, will 1.8.2 come out with that fix and a bajillion others I'm waiting on??). |
@geerlingguy never had that ifdown thing and I guess nobody except you is having this problem in this PR comments… |
Amazing :) When will this appear here? https://atlas.hashicorp.com/bento |
The pipeline is building/publishing now and ubuntu-1604 is near the end - we've got 35 builds left out of 64. That said the 16.04 builds all seem have driver or shared folder issues as well as potential vagrant issues. |
@geerlingguy I applied the patch from hashicorp/vagrant@0505771 to my local vagrant installation and it seems to work with the bento boxes I'm in the process of releasing now. |
@cheeseplus - Here's to a 1.8.2 Vagrant release someday :) |
Chef 12.7.2
|
@Vrtak-CZ wrong place, unrelated issue, no comments, bad style :( |
Adding Ubuntu Xenial (16.04) builds using daily images until released. Verified these build at least.