search

ppggff / vagrant-qemu

Use Vagrant to manage machines using QEMU. Test with Apple Silicon / M1 and CentOS aarch64 image
MIT License
408 stars 32 forks source link

socket path change due to qemu limitation : Path must be less than 10… #3

Closed efortin closed 2 years ago

efortin commented 2 years ago

Hi, i've fix a socket path issue ( due to qemu >104 chars limitation on socket) https://unix.stackexchange.com/questions/367008/why-is-socket-path-length-limited-to-a-hundred-chars

I've moved socket to /.vagrant.d/tmp.

Please, let me know if you have a dedicated process for PR

ppggff commented 2 years ago

Thanks a lot, how about use env[:tmp_path] instead of the fixed path? I think is OK to pass a tmp_path when initialising a new Driver obj: @driver = Driver.new(@machine.id, @machine.data_dir).

ppggff commented 2 years ago

Or add a env parameter to the Driver's start/initialize function?

ppggff commented 2 years ago

Fix in v0.1.7