Re: Improved How-to

#53207

gordonf
Member

I managed to migrate a ZS 1.0 Beta 16 profile to the ZS 3.0.0 OVA template, not lose any configuration from the profile, and have the updated VMware Tools (9.2.3) running.

Here’s a proper how-to:

1) Download the OVA (single file OVF) template from the first post.

2) If you run VMware Tools on your existing ZS VM router, disable launching it and restart ZS. For instance, on the 1.0 b16 example, browse to Setup, Startup / Cron, pick Post-Boot, and delete or comment-out lines like:

/DB/vmware-tools/startup/run.sh
or
/Database/vmware-tools/startup/run.sh

3) Make a backup of your profile(s) (Setup, Profiles). If you’re backing up logs too, note your profile’s size and remember that the template creates a volume that only has 2 GB free disk space.

4) Deploy the OVA template to your VMware installation. OVA templates are supposed to be supported by ESXi 5 or later, and VMware Workstation 8 or later.

5) Modify the deployed VM as needed, by adding network adapters (E1000 only; no vmxnet support here), RAM, disk, etc. Turn off “connected” on the NICs until you get a chance to change IPv4 addresses on them.

6) Power up the new ZS VM you just deployed. Change the NIC IPv4 settings to match your old ZS VM’s settings from the ZS console.

7) Turn off “connected” on the old ZS VM NICs and turn on “connected” on the new ZS VM NICs. This will cut you off from your old ZS. Browse to the new ZS admin interface.

8) Log on, browse to Setup, Profiles, and restore your backed-up profile. Activate it, and restart ZS. When it comes back, it should work as your old ZS VM did but VMware Tools will not yet be running. Test your new router to make sure everything’s working; especially make sure the NIC names and IPv4 assignments are correct.

9) Now we activate VMware Tools. Browse to Setup, Startup / Cron, then select Post Boot and add this line:

/DB/vmware-tools/startup/run.sh

Change the status from Disabled to Enabled. Because the Tools folders reside in /DB instead of /Database, this will work for any profile.

10) Finally, Restart ZS once more. Once it restarts, it should work as your previous ZS worked plus have a running VMware Tools. You can test “Shut Down Guest,” “Restart Guest,” and see its IPv4 addresses in the VM’s properties.

That’s it.

If you need to free up disk space and your previous profile had a copy of VMware Tools in it, open its console, bring up a shell, and browse your /Database directory. You can delete old copies of vmware-tools, rootfs, and vmware-tools-distrib from there if they exist.

WARNING: The run.sh script re-links two root-level directories: /usr and /sbin, which seems to break switching and deactivating profiles. It might also negatively impact downloaded modules. To safely manipulate profiles, and possibly modules, disable the Startup / Cron post-boot command that launches VMware Tools and restart ZS beforehand. Once you’re done, re-enable the command and restart.