Upgrade from 1.2.3 to 2.0 with VMware tools installed will panic
If you upgrade a VMware instance from 1.2.3 to 2.0 with the VMware tools installed, once booted into 2.0 (FreeBSD 8) the VM will attempt to load the old tools (From FreeBSD 7) and a panic will occur.
We may need something in the upgrade process to disable certain packages (or all packages?) until they can be upgraded.
Revert "Swoop through and stop any packages prior to upgrade. Ticket #1156"
This reverts commit cf42de70c84632bcee5d6d545b1242f14a73c618.
#4 Updated by Jon Gerdes about 8 years ago
This is still an issue:
Install new VM from 1.2.3-Release LiveCD
Install Open VM Tools
Use automatic updater to 2.0 RC1 - snapshot dated 28 Feb 2011
It's hard to see exactly where it panics but I definitely see "Configuring Firewall" and a line or two more before a great long stream of white text that looks like an unhappy system followed by a reboot.
#6 Updated by rancor rancor almost 8 years ago
It works for me with 2.0 RC3 - snapshot dated 23 june 2011
I just tested with a fresh install with pfSense-1.2.3-RELEASE-LiveCD-Installer.iso on VMware ESXi 4.1, installed on harddisk and installed Open VMware tools and rebooted the system.
Switched updater to 2.0 and upgraded. On the console I could see that Open VMware tools was reinstalled after upgrade and it booted up just fine. I checked with ps ax | grep vmware and kldstat and the modules was running.
vCenter also reported that VMware tools was installed as "Unmanaged"