ESXi 6.5.0 Guest OS errors…
-
ESXi Build 5310538, guess I will update that when I am able and see how it goes.
Strange this has never happened before, even on severely out-dated builds till the more recent PFSense snapshots… Yes, Open-VM-Tools is installed.
Will post back soon, hopefully... Rather dislike touching that ESXi install.
UPDATE #1:
OK, I am back... No dice... Updated and made sure everything is on the latest code from what I can tell.ESXi 6.5.0 Update 1 (Build 6765664)
All three PFSense virtual machines are on VM Version 13
PFSense has been updated to 2.4.0.r.20171007.0850
Open-VM-Tools is 10.1.0,1
Guest OS is set to "Other > FreeBSD (64bit)"ESXi is seeing that the OS reports back as "FreeBSD 11.1-RELEASE-p1" instead of "FreeBSD(64bit)".... This is a rather recent change (like in the last week, in PFSense wasn't happening on a snapshot from a week or so ago), and affects 3 different virtual machines, so why would this impact just me, and not others?
Update #2:
Have been noticing performance issues with all three of those VM's now, various glitches where it hangs purely at random before it has ever mounted the file system? Set to Other 64bit and that seems to have gone away, however, the message is still there.
-
I'm on 6.5.0 (Build 5310538) and though I do see that guest OS difference message, I don't have any problems with VMs underperforming or hanging.
-
I am on ESXi 6.5.0 (Build 6765664). I have to use the old Kernel (Option 5 in GRUB at Boot). I am currently on the newest Snapshot, built on Mon Oct 09 17:58:12 CDT 2017. The following picture shows what happens if I try to boot normally. The system hangs at "Stopped at via_bitblt_text…"
-
Same here, ESXi 6.5.0 latest patch level, and getting same message with 2.4.0 RC builds. Interestingly the VM sometimes doesn't boot (same error as mentioned above by jasonsansone), however a reboot usually helps…
-
i just updated my lab box to 6.5.0 Update 1 (Build 6765664) and all of my 2.4/2.4.1 VMs powered up fine. No errors.
-
Any other log, pic, or info I can provide to help?
-
Was this a new 2.4.0 install or an upgrade? If it was a new install, what filesystem and partition options were used?
-
I installed 2.4 RC new when it was first released and then restored a config in order to take advantage of ZFS. It’s ZFS on Bios. I have updated each successive snapshot since the initial RC release.
-
I have a mix here, some upgrades, some new installs, most on UFS, one or two on ZFS, I think they're all on GPT/BIOS though. None have issues.
Any special hardware involved in the hypervisor? Passing anything through? Any special options enabled?
-
Nothing special. It’s a Lenovo Thinkstation C20. Dual Xeon Quad Core with 48GB ECC DDR3. No pci passthrough although VT-d is fully enabled for other guest VM’s. No tweaks or special options in the guest or host.
-
Looks like it could be a FreeBSD issue: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220923 and/or https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217282
Seems intermittent and doesn't appear to happen to everyone, not many hits out there for it.
Maybe something in the video/console settings of the virtual hardware itself.
-
So you stated "I'm on 6.5.0 (Build 5310538) and though I do see that guest OS difference message"
Then you updated to "6.5.0 Update 1 (Build 6765664)" Did this make the OS message go away?
-
So you stated "I'm on 6.5.0 (Build 5310538) and though I do see that guest OS difference message"
Then you updated to "6.5.0 Update 1 (Build 6765664)" Did this make the OS message go away?
No, that message is still there, and there is no OS option in the ESX settings for the VM to make it match. Not sure if that's something that FreeBSD or VMware is going to have to fix.
I should also add that the exact same message shows up on a FreeBSD 11.1 VM, so it isn't specific to pfSense. It does go away if you stop the tools guestd daemon, so maybe an update to the open-vm-tools package will eventually fix it.
-
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 have not seen this OS message.. Curious why some people are and I am not.. Guess I could try a clean install.. I am running current open-vm-tools..
I am not using zfs that is for sure.. But I could try installing pfsense clean and freebsd clean and see if I can get it to come up..
-
Here is the warning
-
Yeah I do not get that.. Wow 8 cpus for your pfsense - bit of overkill ;) heheeh
-
Yeah I do not get that.. Wow 8 cpus for your pfsense - bit of overkill ;) heheeh
Smoke'm if you got'em?
-
I just bumped pfsense to
2.4.0-RC (amd64)
built on Mon Oct 09 17:58:12 CDT 2017
FreeBSD 11.1-RELEASE-p1And now I am getting it.. Hmmmmmm?
edit:
I just closed that notice with its little x, and then logged out of esxi, then back in.. And doesn't seem like its coming back?? Huh… Wonder if it only comes up if your watching pfsense boot on esxi? -
Looks like it could be a FreeBSD issue: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220923 and/or https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217282
Seems intermittent and doesn't appear to happen to everyone, not many hits out there for it.
Maybe something in the video/console settings of the virtual hardware itself.
I'm seeing this vga_bitblt_text() bug as well in VMs.
I had no success varying most of the guest VM vga configuration - ram from 4M to 256MB, with or without 3d support, etc.
It occurs in VMs with both legacy bios and EFI bios.
On the bright side, it is intermittent – about 1/4 of reboots. It seems to occur early enough that file system damage doesn't seem to be an issue when invoking a reboot in the debugger.
