[0.2.0.dev] Using chef-solo provisioner on a box without 9p support causes kernel panic on the guest

[tatsuya6502]

• Vagrant 1.5.2
• vagrant-kvm 0.2.0.dev with PR 9p: use md5 of guest path as mount_tag #219

Using chef-solo provisioner on a CentOS 6.5 box without 9p support causes the VM to get kernel panic.

How to reproduce:

Install vagrant-kvm 0.2.0.dev with PR #219. Then run the following commands.

mkdir centos65-chef
cd centos65-chef
wget https://gist.githubusercontent.com/tatsuya6502/10709935/raw/9a3650976f9f0f07a8b30c3262a3d141de1168d6/Vagrantfile
mkdir cookbooks
cd cookbooks
git clone [email protected]:opscode-cookbooks/yum.git
cd ..
vagrant up

[tatsuya6502]

I created and uploaded a "9p ready" CentOS 6.5 box. (you will find it on the List of Boxes Wiki page.) That box just works fine with chef-solo provisioner and the 9p synced folders.

[miurahr]

Oh, excellent! 👍

[miurahr]

We need to check guest's capability.
Also to provide configuration option for users.

[miurahr]

In my short research, I cannot detect guest's capability by checking guest kernel configuration.
Only the way I can do is that p9 capability claim when guest is either debian, gentoo, fedora or arch. (white list) It is impossible to black list for capability.

Does it acceptable?

The direction of white listing p9 cap make RHEL/CentOS not to support p9 even when guest image is modified to support p9.

[miurahr]

I've made question on hashicorp/vagrant#3829

[miurahr]

Answer is

• You can configure provider-specific overrides directly in your box via a Vagrantfile, just like you would in a normal Vagrantfile. Vagrant will merge this.

so we can update document for box creator to advice to add kvm specific configuration in Vagrantfile in box file.