frank_zero

[SOLVED] Install on vmware ESXI

Recommended Posts

VMTools can be installed, after using the bootstrap for optware. After installing the modified VMTools kernel files, the VMTools themselves are installed as the standard ipkg. Add in a startup script, and everything is (should be) running.

 

The steps to install the bootstrap (provided as .xsh files) ...

----------------8<--------------[ SNIP ]------------------>8---------------------

Nice Cookin' Doc! :mrgreen:

I've tried now on Trantor's 4.3 version. Works like a charm :ugeek:

Sweet! That's great news! :grin:

 

The problem is inside the S22open-vm-tools.sh, each line ends with a bloody ^M character.

I blame my SFTP transfer program - I had exported the file from the running Synology and saved it to a Windows Machine to attach to my post. :roll:

 

Edit the script with vi and remove the ending ^M character from each line.

Fantastic News! Easy fix ... and I'll go update my post with a fixed version immediately.

This means that I did not miss anything in my notes, and the Idiot's Guide to VMTools could have been written! However, I hope that for everyone, the above post is good enough. :wink:

 

Thanks Tuatara!

You're (all) very welcome!

 

[EDIT: Link to post for opware bootstrap and open-vm-tools installation]

viewtopic.php?f=2&t=558&start=280#p9968

 

Now, seeing that everyone is having a lot of success with 4.3, and the VMTools installation method I'd worked out before is working on DSM 4.3 and ESXi 5.5, I can see an upgrade process happening in the coming week. :ugeek:

Edited by Guest

Share this post


Link to post
Share on other sites

hi tuatara !

 

the only things we have to know is that if you have rdm disk like me , you can't do snapshot.

Share this post


Link to post
Share on other sites
Check the logs to see if there is anything failing, or if the vmtools daemon can't start, etc.

can you tell which logs should contain VMware tools entries and is there any tools specific logging which can be enabled?

I don't have the time to research/debug what it is I've done to get my version working (I do remember spending a reasonable amount of time on it though). I've probably forgotten something somewhere. It may be a few days (weekend?) before I can get back to you on this.

 

After following the guide for wmware tools I could not get shutdown and reboot to work from the vSphere client. The problem was that the "shutdown" binary did not function on my Synology install. I decided to just create my own "shutdown" script and replace the binary that was in /sbin/ with it:

 

mv /sbin/shutdown /sbin/shutdown_old

vi /sbin/shutdown

 

paste the following code:

#!/bin/sh

 

for var in "$@"

do

if [ "$var" = "-r" ]

then

reboot

exit 0

fi

done

 

poweroff

 

Then change the permissions so teh script is executable.

chmod 755 /sbin/shutdown

 

This worked for me!

Share this post


Link to post
Share on other sites
I decided to just create my own "shutdown" script and replace the binary that was in /sbin/ with it:

 

super! will give this a try. Thanks!

Share this post


Link to post
Share on other sites
I don't have the time to research/debug what it is I've done to get my version working (I do remember spending a reasonable amount of time on it though). I've probably forgotten something somewhere.

After following the guide for wmware tools I could not get shutdown and reboot to work from the vSphere client. The problem was that the "shutdown" binary did not function on my Synology install. I decided to just create my own "shutdown" script and replace the binary that was in /sbin/ with it:

You beauty! :grin: I remember doing a similar thing now! :lol:

 

This worked for me!

Umm ... yeah ... :oops: ... works great for me too.

 

The script I had written was much simpler though ... mine only called poweroff, since that was all I cared about doing through vSphere at the time.

I've updated my DSM 4.2 to your script - which IMHO is much better as it provides full shutdown & restart functionality. Cheers!

[i'll also update my posts, so people looking in the forum can find your script]

 

[EDIT: Link to post for opware bootstrap and open-vm-tools installation]

viewtopic.php?f=2&t=558&start=280#p9968

 

My upgrade to DSM 4.3 Update 3 will happen sometime soon. I'm certain this will be a smooth update process.

 

Thanks go to everyone for all their hard work!

Edited by Guest

Share this post


Link to post
Share on other sites

mv /sbin/shutdown /sbin/shutdown_old

vi /sbin/shutdown

 

paste the following code:

#!/bin/sh

 

for var in "$@"

do

if [ "$var" = "-r" ]

then

reboot

exit 0

fi

done

 

poweroff

 

Then change the permissions so teh script is executable.

chmod 755 /sbin/shutdown

 

This worked for me!

 

worked for me too, though I did not have /sbin/shutdown to rename

 

Many thanks!

Share this post


Link to post
Share on other sites

For those using the vmware tools for shutdown, are you getting errors when you restart your Synology VM? I've tried several things, but if I shutdown using the tools, my synology volume fails upon boot up. If I shut it down normally, I get no errors.

Share this post


Link to post
Share on other sites
For those using the vmware tools for shutdown, are you getting errors when you restart your Synology VM? I've tried several things, but if I shutdown using the tools, my synology volume fails upon boot up. If I shut it down normally, I get no errors.

 

I have three vms (2 x DSM 4.2 & 1 x DSM 4.3). When I use vSphere to shutdown or restart any of them I never get errors when they come back online.

Share this post


Link to post
Share on other sites

How to install optware bootstrap and open-vm-tools into DSM 4.2 and 4.3 (to Update 3 - tested & confirmed)

Just a quick question: what kernel is DSM 4.3 ?

S37vmware.sh script is hardcoded to "3.2.30" kernel version, whilst what I've just fetched from http://xpenology.com/forum/viewtopic.php?f=14&t=1939 does have "3.2.40" kernel. And all the module files don't work (if I change the script to match my kernel version):

 

syn> sh S37vmware.sh start
Package module-init-tools (3.5-1) installed in root is up to date.
Nothing to be done
Successfully terminated.
Loading VMware kernel modules...
vmblock.ko: failed
vmci.ko: failed
vmsync.ko: failed
vmxnet.ko: failed
vmhgfs.ko: failed
vsock.ko: failed

Can you please clarify?

 

Cheers,

Share this post


Link to post
Share on other sites

Yep.

 

I found the "problem".

After the bootstrap install the guide says: reboot.

After the reboot it does not work for me.

If I install the bootstrap, do NOT reboot and install the openvmtools directly after, it works! :grin:

 

Configure the PATH variable to retain the path (if/as needed):
 :%s/PATH=/PATH=$PATH:/
Save and Close vi:
 :wq
Reboot the NAS and login again to the Command Line Interface as user "root":

 

The step: Reboot the NAS and login again to the Command Line Interface as user "root": was the problem for me...

Share this post


Link to post
Share on other sites
I had to change out a fair few hardware controllers before I found one which was stable and worked in VMDirectPathIO mode.

Which one is this?

 

I've got Jetway NF9E-Q77 (6 "Panther Point" SATA ports) + i5-3470T so VT-d is supported. And I ordered simple / cheap SIL3132 based PCIe card just to attach ESXi datastore, but disappointing enough, I found in this thread already that people mentioned this SATA controller being not recognized by vSynology. So I need something that 100% works this time =)

 

My advice, use RDM unless you really, really need SMART monitoring.

Another approach would be to monitor ESXi host with RDM'ed disks and fetch their SMART stats (I don't if it's all possible). It's beneficial to know health of your hypervisor even if it's a home lab.

Share this post


Link to post
Share on other sites

I am now using RDM with SMARTd to fetch the health status.

But I am not sure if it is working well. As it sometimes stops emailing me the report.

Share this post


Link to post
Share on other sites
I am now using RDM with SMARTd to fetch the health status.

SMARTd is running on vSynology? I thought if one does RDM (ie created via vmkfstools {-z,-r} ), then SMART stats are not being exposed to a guest VM, vSynology in this case.

Share this post


Link to post
Share on other sites
I am now using RDM with SMARTd to fetch the health status.

SMARTd is running on vSynology? I thought if one does RDM (ie created via vmkfstools {-z,-r} ), then SMART stats are not being exposed to a guest VM, vSynology in this case.

 

Absolutely correct. There are NO SMART STATISTICS when using a RDM drive. This is BY DESIGN.

 

However, we all know about pushing design limits! :ugeek:

 

If you are using ESXi 5.1, and are willing to push boundaries, you can follow the guide available here:

ESXi 5.1 and SMART monitoring

 

In a nutshell (first post in the thread):

All you need to do is the following and then any disk (not USB) you plugin in thereafter will be available for RDM:
In the ESXi Console window, highlight your server
Go to the Configuration tab
Under Software, click Advanced Settings
Click RdmFilter
Uncheck the box for RdmFilter.HbaIsShared
Click OK

This will set the RDM Filtering to assume that NO DRIVE IS SHARED. You eliminate all virtualization capabilities provided by RDM.

By doing this, using an application which has Direct access to the drive "hardware" you should be able to retrieve the SMART data.

 

I have not personally done this (I'm still running ESXi 5.0 and DSM 4.2), but if you absolutely must have it ... AFAIK it's possible now without VT-d passthrough of the controller.

 

YMMV. No guarantee it won't crash/hang/core dump.

 

Regards,

Tuatara

Share this post


Link to post
Share on other sites

If you are using ESXi 5.1, and are willing to push boundaries, you can follow the guide available here:

ESXi 5.1 and SMART monitoring

Thanks for the hint =) I'm keen to try it, even though I'm running 5.5 currently, but can easily rebuild it with 5.1 as I'm not 'live' yet with my home lab.

 

Cheers

Share this post


Link to post
Share on other sites

If you are using ESXi 5.1, and are willing to push boundaries, you can follow the guide available here:

ESXi 5.1 and SMART monitoring

Thanks for the hint =) I'm keen to try it, even though I'm running 5.5 currently, but can easily rebuild it with 5.1 as I'm not 'live' yet with my home lab.

VMWare doesn't often remove base features in point updates. I'm positive that these options are also available in 5.5 ... it's just in 5.1 when they were first noted as being available.

 

Regards,

Tuatara

Share this post


Link to post
Share on other sites

I'm on ESXi 5.5, just checked now and the option is available (default check is ON).

- RdmFilter.HbaIsShared - ON

- Allow local disks to be RDM candidates for Virtual Machines.

Share this post


Link to post
Share on other sites
I'm positive that these options are also available in 5.5

And you were .. right!

[spoiler=smartclt -a output]syn> smartctl -a /dev/sdb

..

SMART Attributes Data Structure revision number: 16

Vendor Specific SMART Attributes with Thresholds:

ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE

1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0

3 Spin_Up_Time 0x0027 228 197 021 Pre-fail Always - 3575

4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 9

5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0

7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0

9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 64

10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0

11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0

12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 9

192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 8

193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 81

194 Temperature_Celsius 0x0022 115 111 000 Old_age Always - 35

196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0

197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0

198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0

199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0

200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0

..

 

 

Where vSynology's /dev/sdb is RDM disk running on ParaVirtualSCSI controller. Also "short-test" worked, didn't try full test though.

 

I'll see where I can get further with that, ideally would be to hack on DS's GUI so that it fetches tempriture and SMART status ..

Share this post


Link to post
Share on other sites

I've read through a number of the posts in this thread and it seems like VT-D Direct I/O works fine with a M1015 in IT mode, and the SMART status gets passed through to DSM is that correct? I have a E3 1240 and appropriate mobo to support a VT-D system and a N40L that is currently running DSM natively, I am deciding whether to migrate over to the E3 1240 and run other VMs on that box or stick with the N40L as a standalone NAS.

 

I am considering because I am getting new drives for a new array and deciding which route to go. Is the ESXI pretty stable with VT-D and DSM VM?

Share this post


Link to post
Share on other sites

Same here, I'm looking at PERC H310 (OEM LSI 9240-8i), it would be nice to if it's recognized by vDSM in passthrough mode.

 

Should we start a new thread with a list of supported controllers?

Share this post


Link to post
Share on other sites
I'm positive that these options are also available in 5.5

And you were .. right!

[spoiler=smartclt -a output]syn> smartctl -a /dev/sdb

..

SMART Attributes Data Structure revision number: 16

Vendor Specific SMART Attributes with Thresholds:

ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE

1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0

3 Spin_Up_Time 0x0027 228 197 021 Pre-fail Always - 3575

4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 9

5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0

7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0

9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 64

10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0

11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0

12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 9

192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 8

193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 81

194 Temperature_Celsius 0x0022 115 111 000 Old_age Always - 35

196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0

197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0

198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0

199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0

200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0

..

 

 

Where vSynology's /dev/sdb is RDM disk running on ParaVirtualSCSI controller. Also "short-test" worked, didn't try full test though.

 

I'll see where I can get further with that, ideally would be to hack on DS's GUI so that it fetches tempriture and SMART status ..

 

I suppose you rebooted the SYNOLOGY?

 

All I get so far (without reboot):

 

SYNOLOGY> smartctl -a /dev/sdc
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-3.2.30] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

Vendor:               VMware
Product:              Virtual disk
Revision:             1.0
User Capacity:        2,000,398,934,016 bytes [2.00 TB]
Logical block size:   512 bytes
Device type:          disk
Local Time is:        Wed Jan 29 22:07:32 2014 CET
Device does not support SMART

Error Counter logging not supported
Device does not support Self Test logging

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now