VMware tools still not working on newest 2.2.3, can't gracefully shutdown
-
Yes. No problem.
Just right click the VM and chose shut down guest. THen it shuts down gracefully.
Ok, there is definitely something different now. The main console screen of the VM, if you click the stop button it power off the VM instead of invoking shutdown even though if you hover the mouse cursor on tops is says shutdown guest. Before on version 2.2 when the openvm tools last worked fine to shutdown guest, you could click the stop button and it would gracefully shutdown the VM.
Indeed, going to VM, Power, Shutdown guest work fine as you said. I didn't try that before.
I tried on a Windows VM, pressing the stop button gracefully shutdown the guest. So I believe there is still something weird with this open vm tools.
I'mm try to restart a host and see if the host triggers graceful shutdown of pfsense as it used to in the past.
-
It will.
But it depends on how your configure your gueat OS.
Edit settings -> Options -> Power controls
-
Mine is set up exactly the same. Can you hover the mouse cursor over the stop button, and then click on it to check what message do you get? Mine says guest shutdown when you hover it, but then when you click it says power off. The vmware tools power controls in the options tab are all set up like yours
Please check the attached images
-
I run virtual Machine version 7. That could be the difference.
-
I created a VM7 version here, installed from scratch. Still the same. What ESXi version are you using?
I'm going to try across a few different clients, but at least across 2, the same issue for me, all ESXi 5 or 5.5 update 1-2
-
4.1U3
-
1280544_10
Have you updated the package?
Its working here.
just curious
on which version tools are you on ?you are running a old VM hardware.
VMware tools are broke.
on the new release 2.2.X the vmx drivers are included. -
It works fine here.
So not broke for me. Despite running on old vmware version. CMB has reprogrammed the tools so the .ko errors went away since the drivers was included in 10.1
-
So what exactly is not working.. I just installed clean pf 2.2.3 64bit clean on esxi 6, latest build 2715540
Installed the opnevmtools package.. vm is hardware 11 which is default for 6.. I am having no problems - tools show installed 3rd party.. Seems like current version to me if you run the cmd to show version.
I shut it down twice from vclient – goes down smooth, etc.. So what is the problem exactly?? Are you trying to run some modified shutdown script?? Is you issue that it shows _10 in the package but downloads _9 pbi? That seems to be cosmetic issue with no real consequence
-
So what exactly is not working.. I just installed clean pf 2.2.3 64bit clean on esxi 6, latest build 2715540
Installed the opnevmtools package.. vm is hardware 11 which is default for 6.. I am having no problems - tools show installed 3rd party.. Seems like current version to me if you run the cmd to show version.
I shut it down twice from vclient – goes down smooth, etc.. So what is the problem exactly?? Are you trying to run some modified shutdown script?? Is you issue that it shows _10 in the package but downloads _9 pbi? That seems to be cosmetic issue with no real consequence
The problem is just when you open the console and hit the stop button or hit the stop button from the vsphere client when highlighting the VM. If you hover the mouse cursor on top of the button it says guest shutdown, but then when you click on it, it says do you want to power off? then it powers off the VM. The way around is to go to power and then manually select guest shutdown.
I've tested rebooting the server and it indeed switched off the guest gracefully before rebooting the host.
-
When I push the little red button in my console it does a normal shutdown..
See 1st attachment.
My guess is you have it set to power off - see 2nd pic.
-
When I push the little red button in my console it does a normal shutdown..
See 1st attachment.
My guess is you have it set to power off - see 2nd pic.
I've tested this now and managed to isolate do hosts using 5.5 U1, U2 and latest build doesn't suffer from this problem.
So it seems it is basically a ESXi bug :/
-
https://doc.pfsense.org/index.php/Versions_of_pfSense_and_FreeBSD
FreeBSD 10.0
Posted on September 9, 2014 by Guest OS TeamSupport for FreeBSD 10.0 has been introduced for this product:
ESXi 5.5 Update 2
For more information about software support, please check the VMware Compatibility Guide
-
https://doc.pfsense.org/index.php/Versions_of_pfSense_and_FreeBSD
FreeBSD 10.0
Posted on September 9, 2014 by Guest OS TeamSupport for FreeBSD 10.0 has been introduced for this product:
ESXi 5.5 Update 2
For more information about software support, please check the VMware Compatibility Guide
good eye!
-
But it runs fine on 4.1U3 and dont have the issue and tools working fine.
-
As to it running fine in 4.anything is pure luck.. freebsd 10 was not supported until 5.5u2
Why anyone would still be running 4 or even 5.x I don't get - 6 has been out for quite some time.. I can see not going to it the first day it releases in a production setup. But 2 patches have already been released, etc.. I would think its safe to move too.
Support for 4.x ended back in 2014.. Over a year ago.. Why would you be using unsupported version?
-
Its the only cluster left on 4.1
The rest of the clusters run 5.5U2 on all the rest running the cloud servers.
Only the FW cluster run on 4.1 :)
-
Well that makes sense, lets run the latest version of firewall software on the oldest esxi cluster we have.. Yeah that makes sense not to update it, because having more than 1 esxi host makes it very difficult to move vms around to different versions of esxi.. So you can update the other host.. I can see your pain in trying to get off no longer supported version for well over a year.. ;)
So do you have it on 4.1 because it better at holding off DDOS as well? ROFL ;)
-
Does it matter?
It runs very good and very stable. Since its Enterprise Plus version then a lot is automated. I have better uptime than Amazon at the moment so yes. It works.
-
As to it running fine in 4.anything is pure luck.. freebsd 10 was not supported until 5.5u2
Why anyone would still be running 4 or even 5.x I don't get - 6 has been out for quite some time.. I can see not going to it the first day it releases in a production setup. But 2 patches have already been released, etc.. I would think its safe to move too.
Support for 4.x ended back in 2014.. Over a year ago.. Why would you be using unsupported version?
ESXi6 is full of bugs, I use Veeam for several clients and there are many problems involving the latest VMFS 6 as well. I downgraded everything back to 5.5. I don't want my client backups risking to corrupt.
