ESXi 6.5.0 Guest OS errors…
-
"we kill everything at night to save money on the light bill and everything auto-starts in the mornings."
Wow… what a BAD idea that is! So did you do the math on that? What exactly is your host drawing at night when cpus are all idle anyway?
So how many watts this host drawing? Now how much you pay per kwh, do the math for it being off at night.. What you save a $1.20 a month? ;) You eat up 10 years worth of saving with 1 oh shit this didn't boot..
-
The closet pulls ~650w minimum at all times, under load, the closet will reach about 1300w, it's not just the host that gets killed at night either. Switches (that's about 140w alone), 4 satellite modems (between 20w and 45w each depending on weather conditions, signal quality and other factors), and other devices all get powered off shortly after the host shuts down and back on automatically when the host starts back up.
It also keeps the AC from having to run as much at night even though it's easier to cool at night, it still saves on the bill.
No need to do the math, real world testing I average between $20 to $45 lower on the bill on months that I kill everything. While that doesn't seem like a lot per month, over the course of a year, that's a nice savings that can go to other things :)
-
I wonder if whoever maintains the VM Tools Package for PFSense could make modifications to report the "proper" OS?
The pfSense package only uses the FreeBSD port. This issue also affects FreeBSD, so any fix needs to happen on FreeBSD and then it will make its way into our package after.
Maybe it just hasn't shown up yet, but I used "Upgrade VM Compatibility" to upgrade two VMs to "VM version 13", or ESX 6.5 level, and they no longer report the version mismatch warning.
-
I wonder if whoever maintains the VM Tools Package for PFSense could make modifications to report the "proper" OS?
The pfSense package only uses the FreeBSD port. This issue also affects FreeBSD, so any fix needs to happen on FreeBSD and then it will make its way into our package after.
Maybe it just hasn't shown up yet, but I used "Upgrade VM Compatibility" to upgrade two VMs to "VM version 13", or ESX 6.5 level, and they no longer report the version mismatch warning.
Spoke too soon, it just hadn't shown back up yet. Disregard.
-
Anyone that can reproduce that vga_bitblt_text() crash relaibly (I still can't), try adding this to your /boot/loader.conf.local:
debug.debugger_on_panic=0It won't stop the crash but it should allow the VM to restart itself automatically if it happens, rather than sitting at a debug prompt. Though that would also stop it from gathering panic data if you have an actual crash later. Could add a tunable in the GUI to set it back to 1 at boot time which should be late enough to work around that.
-
Another possible workaround is to set kern.vty=sc in /boot/loader.conf.local since this appears to be a race condition in the VT console, according to the FreeBSD bug report.
I did manage to make one of my VMs crash once, finally.
I opened a bug report for it here: https://redmine.pfsense.org/issues/7925
-
"While that doesn't seem like a lot per month, over the course of a year, that's a nice savings that can go to other things :)"
Are you paying this bill? Is this your house or a place of business? Lets call it $50 a month savings.. Or $600 a year… How much does it cost the company when something doesn't come back up and you have people sitting at their desk not able to work?
"Switches (that's about 140w alone),"
What switches are you running that pull 140watts? You running POE? A cisco 3850-48 doesn't even pull 140W under full load.. This doesn't sound like a home setup...
-
FYI- There was a patch for the vga/vt race crash in FreeBSD-CURRENT so be brought it in, if we end up having to rebuild 2.4.0 it may end up in the release, otherwise it will be in 2.4.1 which will be very close behind (a week or two at most).
-
The kern.vty=sc workaround worked for me.
I rebooted a dozen times and didn't see the panic, which is definitely an improvement.
Thanks so much for the workaround and for incorporating the fix!
-
Smoke'm if you got'em?
This is a tangent from the original post, but you can actually get worse performance with additional cores. The way VMware does its scheduling, it will only give a VM a time slice if there are as many cores free as the max defined, regardless of what the VM is currently using. If you have a 12-core box and have defined pfSense as using 8 of those cores, then it's only going to get time when 8 cores are free – even if pfSense is only using 2 for example. Depending on load from other VMs, this can delay a VMs scheduling of CPU time in a detrimental way.
-
The kern.vty=sc workaround worked for me.
I rebooted a dozen times and didn't see the panic, which is definitely an improvement.
Thanks so much for the workaround and for incorporating the fix!
Great news! That's a much better workaround than letting it crash and reboot.
-
@KOM:
Smoke'm if you got'em?
This is a tangent from the original post, but you can actually get worse performance with additional cores. The way VMware does its scheduling, it will only give a VM a time slice if there are as many cores free as the max defined, regardless of what the VM is currently using. If you have a 12-core box and have defined pfSense as using 8 of those cores, then it's only going to get time when 8 cores are free – even if pfSense is only using 2 for example. Depending on load from other VMs, this can delay a VMs scheduling of CPU time in a detrimental way.
Understand, and thank you. I have 16 cores and 48GB RAM for three VM’s. FreeNAS, an Ubuntu web server, and pfSense. The web traffic is minimal and FreeNAS is more static storage. PfSense pulls the greatest load through VPN traffic. Really, it’s massive overkill for all guests. Our encryption settings for a site-to-site trunk are maxed out, so I provide the CPU for OpenVPN.
-
jimp, thanks for looking into the crash so much as well as reporting it :)
So, back to the original posting/question… I guess we will have to wait for FreeBSD to fix the issue then, thankfully the original issue isn't detrimental.
Once again, thanks to all, it's much appreciated. :)
-
Another possible workaround is to set kern.vty=sc in /boot/loader.conf.local since this appears to be a race condition in the VT console, according to the FreeBSD bug report.
I did manage to make one of my VMs crash once, finally.
I opened a bug report for it here: https://redmine.pfsense.org/issues/7925
This bug can also seems to be avoided by using safe mode during install, for those that may be creating a new VM from the ISO.
Interrupt the boot with <space>, then 6 4 1 1.
As you said, to make the workaround persist after the install is complete, invoke a shell and run:
echo set kern.vty=sc >> /boot/loader.conf.local</space>
-
This bug can also seems to be avoided by using safe mode during install, for those that may be creating a new VM from the ISO.
Interrupt the boot with <space>, then 6 4 1 1.
As you said, to make the workaround persist after the install is complete, invoke a shell and run:
echo set kern.vty=sc >> /boot/loader.conf.local</space>
If you are going to that trouble, drop to a loader prompt and run:
set kern.vty=sc bootAlso you don't need "set" in /boot/loader.conf.local, just "kern.vty=sc"
-
I don't think that warning really matters. VMWare is simply not properly identifying the Guest OS but you already manually selected FreeBSD, so the drivers and hardware emulation is accurate. The same occurs when I update to brand new releases of macOS or Ubuntu builds.
I arrived here via Google looking for the answer to this problem and wanted to comment on this because it does matter.
In ESXi you can't do snapshots (or backups via tools like Veeam) unless ESXi thinks the host is in a consistent state. As long as this message appears, ESXi thinks the host is inconsistent, so no snapshots/backups.
-
@El:
I arrived here via Google looking for the answer to this problem and wanted to comment on this because it does matter.
In ESXi you can't do snapshots (or backups via tools like Veeam) unless ESXi thinks the host is in a consistent state. As long as this message appears, ESXi thinks the host is inconsistent, so no snapshots/backups.
I just just took a snapshot of pfSense 2.4.1 CE vm in ESXI 6.5. Whatcha talking about?
-
@El:
I arrived here via Google looking for the answer to this problem and wanted to comment on this because it does matter.
In ESXi you can't do snapshots (or backups via tools like Veeam) unless ESXi thinks the host is in a consistent state. As long as this message appears, ESXi thinks the host is inconsistent, so no snapshots/backups.
I just just took a snapshot of pfSense 2.4.1 CE vm in ESXI 6.5. Whatcha talking about?
I'm running ESXi 6.5.0 Update 1 (Build 6765664). I'm running pfSense 2.4.1-RELEASE (amd64).
ESXi reports "The configured guest OS (FreeBSD (64-bit)) for this virtual machine does not match the guest that is currently running (FreeBSD 11.1-RELEASE-p2). You should specify the correct guest OS to allow for guest-specific optimizations." for my pfSense VM.
If I attempt to take a snapshot of the pfSense VM ESXi errors out with "Failed - The operation is not allowed in the current state."
That's what I'm talking about.
-
@El:
I'm running ESXi 6.5.0 Update 1 (Build 6765664). I'm running pfSense 2.4.1-RELEASE (amd64).
ESXi reports "The configured guest OS (FreeBSD (64-bit)) for this virtual machine does not match the guest that is currently running (FreeBSD 11.1-RELEASE-p2). You should specify the correct guest OS to allow for guest-specific optimizations." for my pfSense VM.
If I attempt to take a snapshot of the pfSense VM ESXi errors out with "Failed - The operation is not allowed in the current state."
That's what I'm talking about.
How do you conclude that one has anything to do with the other? Check vmware.log for details of snapshot request.
-
Just going to bump this as it's still an issue even in 2018.
I'm on Esxi version: 6.5.0 Update 1 (Build 7388607)
PfSense version: 2.4.2-RELEASE-p1 (amd64)The warning keeps appearing every time I go to the "Virtual Machine" section on the ESXI web portal. Here's a screenshot of the bugger: https://image.prntscr.com/image/zN7e5RPmQbCYjVYcv_Qymg.png
It doesn't really seem to hurt anything for me, I can still run all features just fine but it's just a little annoying.
