At any one time, I've got a dozen or so virtual machines that I might want to boot a subset of. Monday and Tuesday I might need one bunch, but Wednesday through Friday another. VMware Fusion's default lease time is a day, which means frequently those early-week machines are assigned IPs that the later-in-the-week machines were previously using. Flip-flop batches and they collide.
Well, you can change the default and maximum lease times that Fusion gives out to guests by using the `vmnet-cfgcli` command. It's pretty easy, and you do it on a per-vmnet basis. To query the current values, for example on the NAT vmnet8 device, goes like this:
Well, you can change the default and maximum lease times that Fusion gives out to guests by using the `vmnet-cfgcli` command. It's pretty easy, and you do it on a per-vmnet basis. To query the current values, for example on the NAT vmnet8 device, goes like this:
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cfgcli getdhcpparam vmnet8 defleasetime
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cfgcli getdhcpparam vmnet8 maxleasetime
And you set the values, again with an example on the NAT network, like this:
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cfgcli setdhcpparam vmnet8 defleasetime <seconds>
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cfgcli setdhcpparam vmnet8 maxleasetime <seconds>
Restart VMware Fusion and you're all set. Machines requesting a new lease will now receive one with the updated settings. By the way, a week is 604800 seconds.
No comments:
Post a Comment