Closed lonedevel closed 2 years ago
Hi @lonedevel ,
Sorry for a late reply. The disk is added twice because the VM is getting rebooted during the initial vagrant up
run (due to prl.update_guest_tools = true
) and you have a configuration which makes prl.customize
command to run on every boot:
prl.customize ["set", :id, "--device-add", "hdd", "--size", "128G"]
^ This is a default behavior. In your case you definitely need to run it only once, after the VM is created, so please add "post-import"
to that line :
prl.customize "post-import" ["set", :id, "--device-add", "hdd", "--size", "128G"]
See more details in docs: https://parallels.github.io/vagrant-parallels/docs/configuration.html
Thank you @legal90! Much appreciated!
I'm trying to create multi-node environment for distributed database testing. The database can run on multiple VMs and I'm trying to configure each with a separate separate disk and mount point for the database content.
In my Vagrantfile I'm only calling the provider.customize option once, yet I see 2 new SATA hdd definitions in each VM configuration that have the same size (128GB). I attached debug output log from the vagrant up command.
Here is the Vagrantfile:
Here is the VM Configuration.
Grepping the debug.log for the specific prlctl command yields:
debug.log