Joanna - the new Proxmox host - is up and running, and all but two VMs have been migrated, and demonstrated to work properly. I've created a new PFsense VM on joanna, and configured and tested it. This will operate in place of the one still running on Jerome - the old VM host based on VirtualBox. The "old" PFsense VM will not be preseved. A new one will be created once jerome has been setup to run Proxmox.
The other VM still running on Jerome is my SO's desktop VM (running - shudder - MS Windows). The one dificulty I expect may happen when migrating is the whole "you've replaced too much hardware" alarm going off and having to re-register MS Windows 10. On the plus side, it's retail Win 10 Pro. As such, my understanding is that you can re-home the license, unlike OEM versions. The possible downside is Win10 is approaching EOL (October of next year) and MS would really rather you use Win11 because telemetry. We'll see. I'm confident in my process for migrating VMs from VirtualBox to Proxmox. I'm less confident in Microsoft.
Floyd - the old storage host - is still plugging along. All shares have been moved off the storage on jerome, and all clients are re-pointed to floyd. That's good.
I'm planning to migrate routing from the PFsense VM on jerome to the one on joanna today, and shutting down the one on jerome. This coming Saturday, I'm planning to migrate the last VM - the Win10 one - off jerome, and lights-out the box for the last time as an Ubuntu-based VM host running VirtualBox. Then, hopefully, I can take my time getting jerome stood up as a properly-configured Proxmox host.
No comments:
Post a Comment