Upgrade to 2.1 and vmware 5.1 gone wrong
-
That seems to be a mismatch between servertime in Vmware tools and your NTP used in Pfsense….
-
There is no NTP client on Vmware host and on psfense there is the normal NTP client setup.
I have kern.timecounter.hardware=i8254 -
Is the host configured to use NTP and is the client running on the host?
-
No the host is not running NTP the NTP is stopped.
-
I am not able to get more than 5-6 hours without a crash. I am already very annoyed with this update experience, and the many problems of FreeBSD and Vmware.
Filename: /var/crash/info.0
Dump header from device /dev/label/swap0
Architecture: amd64
Architecture Version: 1
Dump Length: 82432B (0 MB)
Blocksize: 512
Dumptime: Wed Sep 18 16:51:36 2013
Hostname: pfsense.localdomain
Magic: FreeBSD Text Dump
Version String: FreeBSD 8.3-RELEASE-p11 #1: Wed Sep 11 18:59:48 EDT 2013
root@snapshots-8_3-amd64.builders.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.8
Panic String: softdep_setup_freeblocks: inode busy
Dump Parity: 3431883880
Bounds: 0
Dump Status: good -
No the host is not running NTP the NTP is stopped.
So that obviously would be a problem, no??? Why's it disabled where you clearly have issues with time going backwards?
-
Because if you use both the NTP form the guest and the one form the host, and those are not synchronized (something is slow usually on the guest) the guest can crush. This is at least what I get from the vmware forums and also somewhere here it says the same. If I am wrong please let me know but also with NTP enabled on the host vmware I had the same problems.
-
Id have the host getting NTP updates and then have the guests sync (often) with the host.
-
Ok I will try to do this and see if it works but I think the crash is not related to the clock going backwards.
-
Is it 64bit? Is it a VM?
I think I've become pretty convinced that the 64bit version has issues when ran as a VM.Try this. Back up all settings, do a clean install of 32 bit version, restore settings.
Then tell results. If it works, the dvs need to know your hypervisor type, ect ect ect.
-
It is 64 and it is on VMware 5.1.
-
I think I've become pretty convinced that the 64bit version has issues when ran as a VM.
Try this. Back up all settings, do a clean install of 32 bit version, restore settings.
Then tell results. If it works, the devs need to know your hypervisor type, ect ect ect.
(More info - In my first install of 2.1 on ESXi long ago I had issue with 2.1RC crashing NTP but that was my smaller problem. When I added more than 4 interfaces, always crashed - Recently with others, after much hairpulling to figure out why their NTP was core-dumping, I recommended 32bit as experiment to see if it was related to my old issue. Seems it was because 32bit worked for them. So, now I'm recommending anyone getting flakey results in any 64bit 2.1 pfsense running as VM to try the 32bit version right away rather than pulling hair all day for days.)
-
Ok I will try to do this and see if it works.
-
I did try the 32bit version but the behavior is the same I cant get more than a day without a crash and automatic restart.
i don't know what to do anymore.
-
I have run 2.1 all through its development and after final in esxi 5.0 and 5.1 and never any issues. Now even on 5.5 without one problem related to it being a VM.
I have not updated anything from the default for time settings.. My esxi host runs ntp server that syncs to internet - and all my vms and physical use it to sync time.
I don't believe the vmtools you have installed even work Open-VM-Tools-8.8.1, use the 8.7 version.
