Using Packer, and these scripts, I've generated a Windows 7 base box for use with VMware Workstation, so that, after installing the VMware Workstation plugin, I can use Vagrant to bring up a Windows 7 VM. Pretty straightforward when I do this on my machine, where Packer generated this base box.
But! When I take this base box and use vagrant up on a different machine, with different hardware (but still with Vagrant, VMware, and the plugin installed), Windows wants to load drivers for a different CPU, (because the host has a different CPU) and then of course, reboot.
Is there a way to prevent or ameliorate this? Is this the expected behavior, or am I doing something wrong, or missing something with how Packer, Vagrant, or VMware works?
Using Packer, and these scripts, I've generated a Windows 7 base box for use with VMware Workstation, so that, after installing the VMware Workstation plugin, I can use Vagrant to bring up a Windows 7 VM. Pretty straightforward when I do this on my machine, where Packer generated this base box.
But! When I take this base box and use
vagrant upon a different machine, with different hardware (but still with Vagrant, VMware, and the plugin installed), Windows wants to load drivers for a different CPU, (because the host has a different CPU) and then of course, reboot.Is there a way to prevent or ameliorate this? Is this the expected behavior, or am I doing something wrong, or missing something with how Packer, Vagrant, or VMware works?