Hi,
it looks to me that the reason for 'IDE Controller' missing may be actually in the box.ovf file, ~/.vagrant.d/boxes/centos-VAGRANTSLASH-7/1610.01/virtualbox/box.ovf. Comparing the box.ovf file from puppetlabs/centos-7.2-64-puppet to centos/7 I see many namespaces are missing in the Envelope of the latter.
So I took the box.ovf from 1.0.1 puppetlabs/centos-7.2-64-puppet copied it over centos/7, and modified it (attached) to match the 1610.01 centos/7 one. This consisted of replacing the vmdk name and uuids (diff vs. the original puppetlabs ovf attached), and 'IDE Controller' is again available. I'm on Ubuntu 14.04: $ vagrant --version Vagrant 1.9.0 $ vboxmanage --version 5.1.10r112026
All this may be still due to a mystery about 'IDE Controller' that we don't understand, and I may just be lucky, but it is worth trying on more platforms.
Another hint that something may be wrong with centos/7 box.ovf is the fact that the boot order reported by the original centos/7 box, and the Vagrantfile after the "workaround" of replacing 'IDE Controller' -> 'IDE' does not correspond to the boot order in box.ovf:
vboxmanage showvminfo --machinereadable <uuid> | grep 'boot.=' boot1="floppy" boot2="dvd" boot3="disk" boot4="none"
Moreover, the xml file is supposed to be human-readable, the box.ovf from centos/7 is not - please fix this when generating the new xml file.
Marcin
On Sat, Dec 3, 2016 at 9:34 PM, Laurențiu Păncescu lpancescu@gmail.com wrote:
Hi,
I can't give it a try right now, but I would expect to see an error: I've already had to update my starter kit at the beginning of November, to address the name of the IDE controller having changed. [1] The proper solution would be to get the name of the IDE controller by parsing the output of "VBoxManage showvminfo", instead of hard-coding it.
I've never looked at the reasons for the name change - is "IDE controller" what you get when using Packer, instead of just "IDE"?
Best regards, Laurențiu
[1] https://github.com/lpancescu/cloud-instance-starter-kit/commit/ eb259d0574d80e0c18aadfaad320b77a3d89b052
On Sat, Dec 3, 2016 at 8:11 PM, Marcin Dulak marcin.dulak@gmail.com wrote:
Hi,
does anyone get the above error for the attached Vagrantfile, with: OS X 10.11.6 Vagrant 1.9.0 VirtualBox 5.1.10 r112026 (Qt5.6.2)
Reported here: https://github.com/marcindulak/vagrant-mariadb-galera- tutorial-centos7/pull/1
$ BOX='puppetlabs/centos-7.2-64-puppet' VERSION='1.0.1' vagrant up # works $ BOX='centos/7' VERSION='1610.01' vagrant up # fails $ BOX='centos/7' VERSION='1505.01' vagrant up # fails
["storageattach", :id, "--storagectl", "IDE Controller", "--port", 0, "--device", 1, "--type", "hdd", "--medium", "sdb.vdi"]
The following error was experienced: #<Vagrant::Errors::VBoxManageError: There was an error while executing `VBoxManage`, a CLI used by Vagrantfor controlling VirtualBox. The command and stderr is shown below.
Command: ["storageattach", "51e7f61f-2d6f-43dc-916b-1d8dad0ea505", "--storagectl", "IDE Controller", "--port", "0", "--device", "1", "--type", "hdd", "--medium", "sdb.vdi"]
Stderr: VBoxManage: error: Could not find a controller named 'IDE Controller'>
Please fix this customization and try again.
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel