Bug #1156
closed
Upgrade from 1.2.3 to 2.0 with VMware tools installed will panic
Added by Jim Pingle over 13 years ago.
Updated almost 13 years ago.
Affected Architecture:
All
Description
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.
- Status changed from New to Feedback
Marking as feedback, the recent package changes should have resolved this.
After upgrade, still panics and reboots.
Probably the same issue now as #1251 - /tmp/post_upgrade_command.php is not executing when going from 1.2.3 to 2.0, so the packages aren't getting reinstalled at bootup on the 2.0 upgrade.
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.
Boot to single user mode, touch /conf/needs_package_sync, and then reboot.
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"
// rancor
- Status changed from Feedback to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by