Project

General

Profile

Actions

Bug #1156

closed

Upgrade from 1.2.3 to 2.0 with VMware tools installed will panic

Added by Jim Pingle almost 11 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Package System
Target version:
Start date:
01/03/2011
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0
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.

Actions #1

Updated by Scott Ullrich almost 11 years ago

  • Status changed from New to Feedback

Marking as feedback, the recent package changes should have resolved this.

Actions #2

Updated by Craig Reynolds almost 11 years ago

After upgrade, still panics and reboots.

Actions #3

Updated by Jim Pingle almost 11 years ago

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.

Actions #4

Updated by Jon Gerdes almost 11 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.

Actions #5

Updated by Jim Pingle almost 11 years ago

Boot to single user mode, touch /conf/needs_package_sync, and then reboot.

Actions #6

Updated by rancor rancor over 10 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"

// rancor

Actions #7

Updated by Scott Ullrich over 10 years ago

  • Status changed from Feedback to Closed

Thanks for the update!

Actions

Also available in: Atom PDF