packer-plugin-vagrant has been updated with breaking changes

[dafyddj]

Hi,

packer-plugin-vagrant has recently been updated to v1.1.0 and the structure of the files included in the Vagrant box has changed. See hashicorp/packer-plugin-vagrant#48

If I'm not mistaken, this causes the check on this line to fail:

vagrant-qemu/lib/vagrant-qemu/action/import.rb

Line 22 in 4d85f60

if !image_path || !image_path.file?

This is using vagrant-qemu version v0.3.5

[ppggff]

Thanks, do you have a example box for test?

[dafyddj]

You can try this one

[ppggff]

To support the new version of libvirt box, I need to find a workable libvirt machine for test.
(See how libvirt convert multiple disk config to qemu command)
It'll take a while.

There is temporary workaround for single disk box: use the image file directly.

Install box and find image path:

# install box as "test_new_box"
vagrant box add --name test_new_box ./alpine318-packer_plugin_v1.1.0.box

# find the image file, the default location for "test_new_box":
~/.vagrant.d/boxes/test_new_box/0/libvirt/box_0.img

Set image_path config in Vagrantfile.

qe.image_path = "/Users/xxx/.vagrant.d/boxes/test_new_box/0/libvirt/box_0.img"

[dafyddj]

Thanks for the update

[Xantios]

running into this same issue, currently hardcoding paths in my Vagrantfile.
is there any plans on fixing this so i don't need a workaround ?

[unixerius]

Instead of hardcoding the path, I decided to symlink "box_0.img" to "box.img" which is equally nasty. Both solutions break on the next update of the box image.

For me, the issues occured with generic/alma9 and generic/fedora39.

[unixerius]

I've made a pull request to at least get this plugin working again with boxes that have one single drive image.

[ppggff]

Please try the new v0.3.6

[unixerius]

I can confirm that your version 0.3.6 seems to be working for me.

Please feel free to close this issue.