Djey Posted December 31, 2013 Share #276 Posted December 31, 2013 My bad, I forgot controller index start from 0 So, my disks are attached to #0 : (SCSI 0:0, 0:1, 0:2, 0:3) => 4 RDM disks Concerning VMDK boot disk : (IDE 0:0) => provided image (4.3-3810 V1.0 ESXI) Please note this virtual disk is attached to IDE controller, not SCSI ! Quote Link to comment Share on other sites More sharing options...
LAH Posted December 31, 2013 Share #277 Posted December 31, 2013 That is exactly what i do now, but i have an additional virtual HDD from my ESXi Datastorage (5GB) (NOT raw mapped) for synology apps and so on so that the raw HDD just has to do the storage-job! It seems to be working with the VM HDD and the raw mounted HDD on one SCSI Controller but there must be a reason why usually not hang them up on the same controller?! I dont know right know if its an error of xpenology (that it can only handle one scsi controler), or of my esxi configuration or maybe my bios setup (i use HP N54L with the modded bios) Quote Link to comment Share on other sites More sharing options...
jpopfans1 Posted January 1, 2014 Share #278 Posted January 1, 2014 I downloaded the VMDF file from ESXi datastore onto PC, then I use a hex editor to change the MAC address and serial number in the vmdk. then I uploaded back to the datastore, and I bootup the VM. I can see from the Synology assistant that my VM has the modified serial number and MAC address. but when I check inside the VM by bring out the system info, I have a blank serial number, do I need any more edit ? Quote Link to comment Share on other sites More sharing options...
LAH Posted January 2, 2014 Share #279 Posted January 2, 2014 why do you want to change the mac adress? is it possible to activate HDD hibernate (spin down) while using esxi? I am using WD Green HDD (took it from WD Elements) and this hdd supports auto-hibernation by time. I enabled HDD Suspend by 20mins in XPEnology, But it seems not to be working in the N54L with esxi?! Quote Link to comment Share on other sites More sharing options...
jpopfans1 Posted January 3, 2014 Share #280 Posted January 3, 2014 why do you want to change the mac adress? is it possible to activate HDD hibernate (spin down) while using esxi? I am using WD Green HDD (took it from WD Elements) and this hdd supports auto-hibernation by time. I enabled HDD Suspend by 20mins in XPEnology, But it seems not to be working in the N54L with esxi?! i am trying HA then I chang MAC addresses. have you tried this : viewtopic.php?f=2&t=1999 not sure if it works for ESXi Quote Link to comment Share on other sites More sharing options...
LAH Posted January 3, 2014 Share #281 Posted January 3, 2014 Mmmh, sounds good, but if i do that within an virtual machine, there is no usb stick mounted, so there is nothing to unmount?! But for sure i have a usb stick in the internal usb port which is has my esxi host system installed - would nit be a good idea to unmount it while esxi is running, wouldn't it? Quote Link to comment Share on other sites More sharing options...
NetSpider Posted January 4, 2014 Share #282 Posted January 4, 2014 Guys! Following the guide "to the letter" means choosing all the same options! I did choose that option ... Post or PM me your VMX file (about 3Kb in size) ... I'm sure I'll then easily spot the configuration difference. Otherwise, the only other option is that the machine you're running ESXi on has some other failure (hardware, or virtualization failure). Tuatara I have run out of options. My DSM does not see any Disks, Volues VM loads and DSM runs, But no storage devices of any kind in Storage Manager. Build 4.3 v1.1 Config: HP Proliant Gen 8 16gb DDR Intel G1610 CPU 4 x WD-RE4 RDM's Separate SCSI Channel Would you look at my VMX? Thanks Synology-DiskStation.zip Quote Link to comment Share on other sites More sharing options...
Tuatara Posted January 5, 2014 Share #283 Posted January 5, 2014 Post or PM me your VMX file (about 3Kb in size) ... I'm sure I'll then easily spot the configuration difference. Tuatara I have run out of options. My DSM does not see any Disks, Volues VM loads and DSM runs, But no storage devices of any kind in Storage Manager. Build 4.3 v1.1 Config: HP Proliant Gen 8 16gb DDR Intel G1610 CPU 4 x WD-RE4 RDM's Separate SCSI Channel Would you look at my VMX? Thanks Hi NetSpider, No worries ... a quick look indicates that you have created a new SCSI Controller as Controller 1 and attached all of the drives to this controller. AFAIK the only controller supported must be SCSI Controller 0. You also have two E1000 network cards assigned to the VM ... not certain what the second one is for, but you could/should remove it in my opinion. It won't bring you any benefits unless your using your virtual XPEnology as a bridge or router. I've (quickly) edited your vmx file to remove the second ethernet, move the SCSI controller to 0 (from 1), and also to place all the VMDK drives in sequential order (0,1,2 not 0,1,3). I don't have the ability to test my changes, but I'm confident in the modifications. You can use WinDiff to see the modifications I made. Shutdown the VM. Backup your current VMX. Upload this VMX in place. Start the VM again. This time the drives should come up and all be visible as Disk 0, 1, 2. Regards, Tuatara. Synology-DiskStation-SCSI0.zip Quote Link to comment Share on other sites More sharing options...
mcdull Posted January 5, 2014 Share #284 Posted January 5, 2014 I intended to use SCSI controller 1 instead of 0 for all my vmdk. and it works fine. My current set up is 4 HDD with RDM. from 1:0 to 1:3. Quote Link to comment Share on other sites More sharing options...
mcdull Posted January 5, 2014 Share #285 Posted January 5, 2014 I have a question on the ESXi 1.1 version. Can this version be shut down properly? On my Esxi, it takes forever for the DSM to shutdown. And most importantly, the console blank at some time after the DSM boot up. Any way to stop it from disappearing? Thanks. Quote Link to comment Share on other sites More sharing options...
mcdull Posted January 5, 2014 Share #286 Posted January 5, 2014 I have one more question, After using the 1.1 image, I have call trace every time I got server started. [ 47.371813] Pid: 11634, comm: openvpn Tainted: P O 3.2.40 #30 VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform [ 47.372125] RIP: 0010:[] [] tun_chr_open+0x40/0x53 [tun] [ 47.372321] RSP: 0000:ffff8800680d1cb8 EFLAGS: 00010282 [ 47.372429] RAX: 0000000000000000 RBX: ffff88007ba2e7c0 RCX: 00000000000000ff [ 47.372556] RDX: ffff8800680aba80 RSI: 00000000000000d0 RDI: 0000000000000202 [ 47.372683] RBP: ffffffff81654240 R08: ffff88007f239f00 R09: ffff88007bcd1009 [ 47.372810] R10: 00000048ffffff9c R11: 00000000080cb818 R12: ffff88007ba2e7c0 [ 47.372937] R13: 0000000000000000 R14: ffff88007eeba870 R15: ffff88007eeb5080 [ 47.373065] FS: 0000000000000000(0000) GS:ffff88007f700000(0063) knlGS:00000000f72d01c0 [ 47.373222] CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033 [ 47.373335] CR2: 0000000000000028 CR3: 0000000077f90000 CR4: 00000000000006e0 [ 47.373505] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 47.373653] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [ 47.373782] Process openvpn (pid: 11634, threadinfo ffff8800680d0000, task ffff8800682813d0) [ 47.373987] Stack: [ 47.374099] ffffffffa05ad2b0 ffffffff81220d02 0000000000000000 ffff88007f33ed40 [ 47.374409] 0000000000000000 ffff88007eeba870 ffff88007ba2e7c0 ffffffff810c9a3d [ 47.374720] 0000000000000000 000000c8810cfdce ffff88007ba2e7c0 ffff88007eeba870 [ 47.374996] Call Trace: [ 47.375078] [] ? misc_open+0x10d/0x170 [ 47.375204] [] ? chrdev_open+0x11a/0x139 [ 47.375332] [] ? chrdev_show+0x5e/0x5e [ 47.375442] [] ? __dentry_open+0x13e/0x231 [ 47.375558] [] ? do_last+0x549/0x574 [ 47.375668] [] ? path_openat+0xd3/0x2e3 [ 47.375781] [] ? do_filp_open+0x28/0x56 [ 47.375893] [] ? mntput_no_expire+0x24/0xd4 [ 47.376008] [] ? do_sys_open+0x60/0xee [ 47.376118] [] ? ia32_do_call+0x13/0x13 [ 47.376229] Code: 48 89 c2 b8 f4 ff ff ff 48 85 d2 74 2f c7 02 00 00 00 00 48 c7 42 08 00 00 00 00 65 48 8b 04 25 40 b7 00 00 48 8b 80 f0 03 00 00 <48> 8b 40 28 48 89 42 10 48 89 93 98 00 00 00 31 c0 5b c3 48 83 [ 47.378649] RIP [] tun_chr_open+0x40/0x53 [tun] [ 47.378803] RSP [ 47.378891] CR2: 0000000000000028 [ 47.379014] ---[ end trace 3ae4591e608c3e06 ]--- I think it is related to openvpn but I have tried to uninstall the vpn server with no luck. Thanks for your help. Quote Link to comment Share on other sites More sharing options...
Tuatara Posted January 6, 2014 Share #287 Posted January 6, 2014 I intended to use SCSI controller 1 instead of 0 for all my vmdk. and it works fine.My current set up is 4 HDD with RDM. from 1:0 to 1:3. Interesting ... I'm using 4.2, and with this version only SCSI controller 0 can be active (AFAIK). I didn't extensively try SCSI 1 - no need. In any case, why would you want to skip controller 0? (i.e. the first in the scanning order) Quote Link to comment Share on other sites More sharing options...
Tuatara Posted January 6, 2014 Share #288 Posted January 6, 2014 I have a question on the ESXi 1.1 version. Can this version be shut down properly? On my Esxi, it takes forever for the DSM to shutdown. And most importantly, the console blank at some time after the DSM boot up. Any way to stop it from disappearing? I have not yet migrated to DSM 4.3 (still watching the threads), and am personally still using DSM 4.2, so I can't really answer for any differences in DSM 4.3. I have VMWare tools compiled and installed under DSM 4.2, and have startup/shutdown/IP monitoring/etc. all working well for me. I'm not experiencing any (undue) long delays during shutdown. Quote Link to comment Share on other sites More sharing options...
patmtp35 Posted January 6, 2014 Share #289 Posted January 6, 2014 hi was it possible to share vmware tools for dsm 42 ? Quote Link to comment Share on other sites More sharing options...
Tuatara Posted January 6, 2014 Share #290 Posted January 6, 2014 (edited) hi was it possible to share vmware tools for dsm 42 ? How to install optware bootstrap and open-vm-tools into DSM 4.2 and 4.3 (to Update 3 - tested & confirmed) open-vm-tools can be installed, after installing the bootstrap for optware. After installing the syno open-vm-tools kernel files, the open-vm-tools themselves are installed as the standard ipkg. Add in a startup script, for DSM 4.2 only replace the shutdown binary with a script, and open-vm-tools are running in ESXi. The steps to install the optware bootstrap (provided as .xsh files) are below: Enable and then Login to the Command Line Interface as user "root", password is the same as for admin. Change to a temporary directory: cd /volume1/@tmp Get the NAS to download the bootstrap: wget http://ipkg.nslu2-linux.org/feeds/optware/syno-i686/cross/unstable/syno-i686-bootstrap_1.2-7_i686.xsh Set the .xsh script to be executable: chmod +x syno-i686-bootstrap_1.2-7_i686.xsh Now run the .xsh script: sh syno-i686-bootstrap_1.2-7_i686.xsh Delete the script file: rm syno-i686-bootstrap_1.2-7_i686.xsh Check and Fix up the PATH in the root .profile: vi /root/.profile 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": Update the ipkg list of available packages: ipkg update Upgrade any ipkg installed packages to the latest versions: ipkg upgrade Finished! You can now install ipkg packages using the command "ipkg install xxxx" where xxxx is the name of the package. You can list all the available packages using the command "ipkg list | more". The steps to install the open-vm-tools are below: Enable and then Login to the Command Line Interface as user "root", password is the same as for admin. Install the open-vm-tools Kernel Binaries: Change to a temporary directory: cd /volume1/@tmp Get the NAS to download the open-vm-tools: wget http://users.skynet.be/synology/i686/syno_vmware_kernel_mod_x86_64_3.2.30.zip Unarchive it: unzip syno_vmware_kernel_mod_x86_64_3.2.30.zip Go in the directory: cd syno_vmware_kernel_mod_x86_64_3.2.30 Set the .sh script to be executable: chmod +x S37vmware.sh Now run the S37vmware.sh script: sh S37vmware.sh start Install the Tools Binaries: ipkg install http://users.skynet.be/synology/i686/open-vm-tools_9.2.3-1031360-1_i686.ipk Install Opt Startup Script for open-vm-tools: cd /opt/etc/init.d/ Unzip the attached S22open-vm-tools.zip: Copy/Transfer S22open-vm-tools.sh into the current directory: Mark the script as executable: chmod +x S22open-vm-tools.sh Alternatively, you can create the script using vi: vi S22open-vm-tools.sh Set to Insert Mode: i Copy and paste into vi the following: ----->8------ #! /bin/sh # # /opt/etc/init.d/S22open-vm-tools.sh # case "$1" in start) echo "Starting VMWare Tools:" /opt/bin/vmtoolsd --background /var/run/vmtoolsd.pid ;; reconfig) true ;; stop) echo "Shutting down VMWare Tools:" true ;; *) echo "Usage: $0 {start|stop|reconfig}" exit 1 esac exit 0 -----8<------ Save and Close vi: :wq Mark the script as executable: chmod +x S22open-vm-tools.sh If (and ONLY if) you are using DSM 4.2 then: [Thanks go to erocm123!] cd /sbin Move the existing shutdown binary to a backup (if it exists): mv shutdown shutdown_old Unzip the attached shutdown-erocm123.zip: Copy/Transfer shutdown into the current directory: chmod +x shutdown Alternatively, you can create the script using vi: vi shutdown Set to Insert Mode: i Copy and paste into vi the following: ----->8------ #! /bin/sh # # /sbin/shutdown # for var in "$@" do if [ "$var" = "-r" ] then reboot exit 0 fi done poweroff -----8<------ Save and Close vi: :wq Reboot to start the open-vm-tools automatically on boot or ... To (re)start the open-vm-tools: /opt/bin/vmtoolsd --background /var/run/vmtoolsd.pid Good Luck! Tuatara UPDATE: Fixed the ^M (linefeed) characters from the end of each line. I blame my SFTP transfer application on Windoze. UPDATE 2: erocm123 figured out the step I'd forgotten about and created a better script for DSM 4.2 to handle shutdown and restart properly. [Ref: viewtopic.php?p=10163#p10163] NOTE: The shutdown script is NOT required for DSM 4.3 as the existing binary performs a shutdown/restart properly. S22open-vm-tools-v1.1.zip shutdown-erocm123.zip Edited January 9, 2014 by Guest Quote Link to comment Share on other sites More sharing options...
patmtp35 Posted January 6, 2014 Share #291 Posted January 6, 2014 thanks i'll test this tonight after work ! Quote Link to comment Share on other sites More sharing options...
tsygam Posted January 7, 2014 Share #292 Posted January 7, 2014 Hi Tuatara! I am on 4.2 also. Followed your guide and see vmtools running, but not able to shut down, restart, etc. Also on reboot kernel modules do not load automatically. May be start up script should be different or some config added? I did not find tools.conf Please advise if you can. Regards, tsygam Quote Link to comment Share on other sites More sharing options...
Tuatara Posted January 7, 2014 Share #293 Posted January 7, 2014 I am on 4.2 also. Followed your guide and see vmtools running, but not able to shut down, restart, etc.Also on reboot kernel modules do not load automatically. May be start up script should be different or some config added? I did not find tools.conf Ok ... I've got my installation working, and the vmtools always start up automatically without issue. Did you set the script to be executable? [chmod +x S22open-vm-tools.sh] Upon startup you should see "Starting VMWare Tools:" in the logfile if the [s22open-vm-tools.sh] script is executed. When starting the VMTools manually do they start up, and are visible in ESXi vSphere? [/opt/bin/vmtoolsd --background /var/run/vmtoolsd.pid] Can you control the running VMTools through vSphere [manually or automatic?] Check the logs to see if there is anything failing, or if the vmtools daemon can't start, etc. Quote Link to comment Share on other sites More sharing options...
tsygam Posted January 7, 2014 Share #294 Posted January 7, 2014 Did you set the script to be executable? [chmod +x S22open-vm-tools.sh] Yes, I did Upon startup you should see "Starting VMWare Tools:" in the logfile if the [s22open-vm-tools.sh] script is executed. actually I do not see this since kernel modules are not loaded at boot for some reason and probably because of this tools fails to load. How modules installed by S37vmware.sh should be started? When starting the VMTools manually do they start up, and are visible in ESXi vSphere? [/opt/bin/vmtoolsd --background /var/run/vmtoolsd.pid] after I load modules manually and then run S22open-vm-tools.sh or /opt/bin/vmtoolsd --background /var/run/vmtoolsd.pid, tools are started and are seen by vSphere Client as third party tools Can you control the running VMTools through vSphere [manually or automatic?] I can send reboot or other command once without effect on DSM machine, but next time vSphere client fires an error 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? Thanks for your help! Quote Link to comment Share on other sites More sharing options...
Tuatara Posted January 7, 2014 Share #295 Posted January 7, 2014 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. Quote Link to comment Share on other sites More sharing options...
tsygam Posted January 7, 2014 Share #296 Posted January 7, 2014 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. I will really appreciate your help and will wait patiently Quote Link to comment Share on other sites More sharing options...
costib Posted January 8, 2014 Share #297 Posted January 8, 2014 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) are below: Reboot your NAS. Enable and then Login to the Command Line Interface as user "root", password is the same as for admin. Change to a temporary directory: cd /volume1/@tmp Get the NAS to download the bootstrap: wget http://ipkg.nslu2-linux.org/feeds/optwa ... 7_i686.xsh Set the .xsh script to be executable: chmod +x syno-i686-bootstrap_1.2-7_i686.xsh Now run the .xsh script: sh syno-i686-bootstrap_1.2-7_i686.xsh Delete the script file: rm syno-i686-bootstrap_1.2-7_i686.xsh Fix up the PATH in the root .profile: vi /root/.profile (in vi, then type) :%s/PATH=/PATH=$PATH:/ :wq! Reboot the NAS and login again to the Command Line Interface as user "root" Update the ipkg list of available packages: ipkg update Upgrade any ipkg installed packages to the latest versions: ipkg upgrade Finished! You can now install ipkg packages using the command "ipkg install xxxx" where xxxx is the name of the package. You can list all the available packages using the command "ipkg list | more". --- Install open-vm-tools: Install the Kernel Binaries: Change to a temporary directory: cd /volume1/@tmp Get the NAS to download the open-vm-tools: wget http://users.skynet.be/synology/i686/sy ... 3.2.30.zip Unarchive it: unzip syno_vmware_kernel_mod_x86_64_3.2.30.zip Go in the directory: cd syno_vmware_kernel_mod_x86_64_3.2.30 Set the .sh script to be executable: chmod +x S37vmware.sh Now run the .xsh script: sh S37vmware.sh start Install the Tools Binaries: ipkg install http://users.skynet.be/synology/i686/op ... 1_i686.ipk Install Opt Startup Script for open-vm-tools cd /opt/etc/init.d/ Unzip the attached S22open-vm-tools.zip Copy S22open-vm-tools.sh into the current directory chmod +x S22open-vm-tools.sh Reboot or ... To restart the open-vm-tools: /opt/bin/vmtoolsd --background /var/run/vmtoolsd.pid Let me know how it goes ... I do have them running on my DSM 4.2 installation, so I hope I haven't left out or forgotten any other steps. Good Luck! Tuatara Nice Cookin' Doc! I've tried now on Trantor's 4.3 version. Works like a charm The problem is inside the S22open-vm-tools.sh, each line ends with a bloody ^M character. Edit the script with vi and remove the ending ^M character from each line. Thanks Tuatara! Quote Link to comment Share on other sites More sharing options...
tsygam Posted January 8, 2014 Share #298 Posted January 8, 2014 yes, I removed those ^M chars. Anyway first command has no effect and following lead to: Call "VirtualMachine.RebootGuest" for object "Synology" on ESXi "____________" failed. Quote Link to comment Share on other sites More sharing options...
costib Posted January 8, 2014 Share #299 Posted January 8, 2014 What do you mean by "first command"? I suggest you to re-download the packages and make a fresh install of DSM. Quote Link to comment Share on other sites More sharing options...
patmtp35 Posted January 8, 2014 Share #300 Posted January 8, 2014 sorry for the delay but i wasen't home before .... on my DSM4.3 update 3 it work like a charm many thanks !!!!!!!!!!!!!!!!!!!!!!!!! just have to suppress the ^M in the script Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.