Vagrant on F23 issues

[jim-minter]

@chris-milsted

1. Appear to be hitting https://github.com/pradels/vagrant-libvirt/pull/423/files
2. On F23, vagrant-libvirt appears to barf on multiple interfaces with same IP within OSE3 guest when editing /etc/exports on host - workaround for now probably to set nfs_export to false in Vagrantfile on host (https://docs.vagrantup.com/v2/synced-folders/nfs.html)
3. Bonus - document use of echo 'pool-refresh default' | sudo virsh trick

[jim-minter]

@bkoz - would be useful to know the versions of vagrant & vagrant-libvirt you're using and where you got them from.

"It seems my vagrant issues on RHEL7 have to do with what IP address gets put into /etc/exports. On my RHEL7.2 laptop, I've seen 172.17.42.1, 10.1.0.1 and 192.168.121.246 (the actual IP of the VM) get put into the file.

When an 192.168.121.* IP is used, the nfs mount succeeds, otherwise it fails As a workaround, I've replaced /etc/exportfs with the following line and the mount succeeds consistently.

"/vagrant/ose" 192.168.121.0/24(rw,no_subtree_check,all_squash,anonuid=14045, anongid=14045,fsid=2127096955)

Also, occasionally, the nfs-server will not start after vagrant has written to /etc/exports. It seems like it somehow corrupts the file and confuses the nfs-server start up script."

This looks like case (2) from above as well

[jim-minter]

vagrant-libvirt/vagrant-libvirt#356 looks like it's in a similar ballpark as well

[jim-minter]

bkoz: using https://dl.bintray.com/mitchellh/vagrant/vagrant_1.7.4_x86_64.rpm
libvirt-1.2.17-13.el7_2.2.x86_64
vagrant-libvirt (0.0.32)

[jim-minter]

I've suggested vagrant-libvirt/vagrant-libvirt#571 upstream to help with this issue.