This is a really old post but I also had the same question, I found in the README a very subtle hint on how to pass Custom Arguments directly to qemu for cases where the exposed options in the Vagrantfile don't map to what you need.
https://github.com/vagrant-libvirt/vagrant-libvirt#custom-command-line-arguments On Friday, February 23, 2018 at 6:05:26 AM UTC-6, gloo wrote: > > Hey guys I'm quite new to Vagrant and trying to find a solution to use EFI > bootloader for a qemu vm in Vagrant. > It seems to be possible to add the readonly part of EFI with > > > *config.vm.provider :libvirt do |libvirt|* > * libvirt.loader = '/usr/share/OVMF/OVMF_CODE.fd' * > > but how can I pass the writeable pflash OVMF_VARS.fd via Vagrant? > The libvirt storage options don't seem to allow pflash files as drive > > In qemu (packer) I use the following 2 lines to pass both files: > > [ "-drive", > "file=OVMF_CODE.fd,if=pflash,format=raw,unit=0,readonly=on" ], > [ "-drive", "file=OVMF_VARS.fd,if=pflash,format=raw,unit=1" ], > > Any help would be appreciated. > > Gloo > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/1155ed3f-6274-4280-9942-dc0ed55514f2%40googlegroups.com.
