Tuatara

Members
  • Content Count

    60
  • Joined

  • Last visited

Everything posted by Tuatara

  1. I didn't have anything to do with the original patches, but due to the nature of my work I am very interested in keeping the ESXi hardware virtualization of Synology DSM 4.x up to date and current. I'll have a look at jukolaut's work - some century when I have "free time" [what's that? ] and see what is involved in updating the kernel/patches and making a new PAT file. No promises ... but being interested will keep this on the front of my 'To Do List'. If anyone else is keen - AFAIK all the details are available on the site - for skillset - Linux kernel building, Binary Hex File editing, a
  2. I only made the guide - others made the modifications, so thanks go to all who made it possible. So if i well understand, I should switch the RDM paravirtual to VMDirectPathIO - which shouldn't affect performances but will allow HDD to rest with SMART. And so reduce power consumption and hopefully extend their lifetime. I'm a total newbie with ESXI and actually don't know how to do that... If you absolutely need SMART, then you will need to go VMDirectPathIO. This requires VT-d extensions within ESXi, which permits you to map the physical hardware into the Virtual Machine. i.e.
  3. I'm not sure what's happening for you, but the RDMs I'm using are all fine and survive reboots without any issues. Potentially there is something in your ESXi installation at issue. Are you using any 3rd party drivers on your ESXi whitebox? Anything special in your configuration or hardware?
  4. You can install ESXi to SD card (>=2GB) instead of USB. Its there specifically for embedded installs. Learn something every day. I wasn't sure if ESXi supported SD cards - good to know! P.S> I use these USB drives for all my ESXi installations. They're almost invisible, and you won't have anyone pulling them out accidentally. Cruzer Fit™ USB Flash Drive (4Gb)
  5. Hello Tuatara, thanks for your guide. No worries ... glad it's helping. If you can successfully install ESXi on the machine (USB keys are perfect for this), and all physical devices are recognized (CPU, RAM, Perc controller, etc.) then yes - you will be fine. Making the RDM files - yes - just follow the instructions but substitute your drives obviously! BTW: That would be one *kick-ass* machine! Not sure about the SD Slot, but you probably can map that to another VM through VMDirectPathIO.
  6. How did you shut down the VM or perform the reboot? Do you have the drives mapped as RDM or as VMDK? Depending on how you shut down the host (don't do it through vSphere!) there may be cached files which are not written to disk by the time the VM is powered off. Think of it as "pulling the power" on the machine.
  7. Unfortunately this is a "known" bug ... something I just automatically do. It has something to do with adding the virtual hardware to the machine ... sometimes the virtualized drivers "stick", but sometimes they don't. No idea why. I guess I could add that into the "rev 2" of the Guide ... sometime.
  8. You're welcome. Glad it's been working for everyone. From my testing the difference between using a VMDirectPathIO mapped controller and a Paravirtual RDM is negligible. I was unable to find any real difference in performance, and would estimate the performance difference is under 1% - well within my experimental error in testing. Stick with RDM, since you can then use ANY disk controller supported under ESXi without any driver changes/additions required for the Synology. It would also be much more stable IMHO. Unfortunately this is the trade-off. The PVSCSI driver does not
  9. Ok ... this means that the synotify_add_watch error has been removed from the ESXi patches. If you're happy having the sync operate the other way, then you have a solution. I'll see if I can find the function call/stub/omission in jukolaut's code updates, but I don't have the time right now to do so. Maybe when the 3211 version GPL code is available.
  10. Ummm ... I don't understand the question. This entire thread is about running DSM in ESXi. By re-reading the thread, you'll find all the information you need to run DSM on ESXi. You need a different set of installation files for ESXi than what is needed for VMWare Workstation or VirtualBox or Hyper-V or for a physical machine (HP N40, etc.) For ESXi, read (and follow exactly) the "Idiot's Guide" to install on ESXi. Idiot's Guide to DSM 4.2 and ESXi 5.1 For other VMWare or VirtualBox installations, check other forum threads. The best one would probably be "XPEnology for dummies LIN
  11. "synotify_add_watch" with a path sounds suspiciously like the "inotify_add_watch" function ( Reference ) in Linux. It's possible that Synology has extended this function to support their special disk configurations (SHR?), and this support is not available (or not present) in the PVSCSI drivers being used for VMWare/ESXi. In which case, it will take some reverse engineering to resolve. Alternatively, there could be an error in the DSM Shared Folder Sync functionality. The first thing that comes to mind is the [space] in the directory name. It's possible that there is an error in the code,
  12. First off, don't try to upgrade through DSM itself - you will overwrite all modifications which were made to 3202 (kernel, drivers, etc.) which were done in order to get it to run on ESXi. The changes for DSM 4.2 3211 sound significant enough (don't they always), that an update will probably be coming ... from someone ... sometime. Patience. ( DSM 4.2 3211 Release Notes ) Synology have also not as yet released the GPL sources to Sourceforge ( Synology GPL Source ). Since jukolaut has posted his modifications, it would only be a matter of time before the next version is created. Rem
  13. Good to hear. As for the upgrade, I don't believe this is possible without replacing the kernel & changed files before importing the Synology .pat file. Using the actual files will remove the PVSCSI driver/etc. and the VM will no longer boot. Stick with 3202 until an updated version is released. I'm hoping jukolaut will return to the forum and provide the sources for his modifications.
  14. French, German, English ... all good here. From the dump it looks like exactly 1 packet every 5. This looks very suspicious. Have you got the "Denial of service (DoS) protection" enabled on the DiskStation? If so, then the DiskStation is deliberately dropping the packets to prevent a flood. This would be by design.
  15. Hi johndoe, I don't believe the current build can be installed on ESXi 4.1, as the PVSCSI driver has been built against ESXi 5.x. I can confirm that it will successfully install on ESXi 5.0 (with or without updates), ESXi 5.1 (with or without updates). Unfortunately I do not have an ESXi 4.1 installation available to test this on. My recommendation - give it a try. It only takes about 15 minutes to get it all set up. If the VM boots, then there is a good chance everything will work. Failing that ... upgrade the box to ESXi 5.x and make use of the increased functionality/stability which
  16. My bet is that the CPU shares for the Synology instance are limiting the overall performance. If the CPU (virtual) is maxed out due to the SHR rebuild, then there will be little (if any) horsepower available for anything else. It's just too busy to service all requests. Now, the reason it's not dropping anything else is due to how TCP is designed. A ping is a UDP packet - it is sent with no expectation of a reply. A FTP connection (or NFS, Samba, etc.) are TCP connections, which by design expect a reply. If there was no reply, the packet is re-sent. This guarantees the communications strea
  17. From this german forum, it's apparently fine to use the Atom bootstrap. You would then need to do the process manually (Info Here). The other "possible" option is that we change the model which the XPEnology thinks it is - something smaller ... but then "drives would be lost".
  18. Fantastic - great to hear it's now sorted. For everyone else - yes, the guide is proven and tested. Follow it, and it will work every time.
  19. Sweet! If you do get it compiled, having open-vm-tools installable through IPKG would be perfect! I'm going to give it a go shortly ... setting up the development environment soon. jukolaut - if you can provide your modified sources - I've already downloaded the Synology GPL sources and will look into the modifications required myself. I'll continue jukolaut's work and remove the remaining SYNOIO_GET_xxxx ioctl calls which are being logged and see if I can "simply" integrate a few other VM friendly elements.
  20. I did choose that option ... I'll send it tonight when I get home. I'm having no problems with otherVM's though ... vmx File: link Hey devastator, you'll be devastated to hear ... you've got the "lsilogic" controller in your configuration, not the "pvscsi" controller. You will need to power down the VM, and then change the SCSI controller type. Exactly the same issue as Portnawak had. Do this, and it should fix your problem. Additionally, you have not reserved the memory for the Synology OS. I'd recommend reserving the memory (dedicated), as a real Synology box does not have virtualis
  21. 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).
  22. Had the same problem until I changed the SCSI controler type to Paravirtual, and then, it worked (ESXi 5.1 on a Microserver N40L, and a VMFS disk as well - just testing...) Guys! Following the guide "to the letter" means choosing all the same options!
  23. Did you install DSM, and the timeout is in the manager? Or are you timing out pre-install of the pat file? What ESXi hardware are you running this on? Intel / AMD, memory, disk, motherboard, etc. Are there any other VMs on the same machine? Are you using a VMFS Disk or a RDM Disk? You may have faulty hardware (fails to virtualise). Follow the guide, use a VMFS Disk first to test that it installs and works, then delete/disconnect the disk and redo it properly with the desired Drive. All else being the same, the guide setup will work, since it is purely virtual.
  24. As requested, I've created an Idiot's Guide document which details the installation steps and options required in order to install DSM 4.2 on ESXi 5.1. A complete screen-shot example of all configuration steps is provided, with a fully virtual configuration for testing purposes. Details are also included about creating RDM VMDK disk images instead of VMFS based virtual disks. Thanks again go to jukolaut and odie82544 for making DSM 4.2 on ESXi 5.1 possible. http://depositfiles.com/files/virzefc1a[/url] Idiot's Guide to DSM 4.2 and ESXi 5.1.pdf