• Content Count

  • Joined

  • Last visited

Community Reputation

7 Neutral

About ilovepancakes

  • Rank
    Regular Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. They updated the page a few days ago to provide DSM 7 RC publicly. So while not a final release I suppose, it seems pretty damn close unless they find a major show-stopping bug at this point. No registration required either.
  2. @kiler129Nice progress on your last 2 analysis posts! Did you happen to try DSM 7 with the same approach to see if it installs the same with your franken-DSM method or you only stuck to 6.2.4 for now?
  3. I meant, any DSM 7 won't boot with jun's loaders directly.... but, virtual DSM 7 DOES boot when run through VMM even when the VMM host is in fact a 6.2.3 xpenology install. My point being, why does DSM 7 (in the form of Virtual DSM) work on non-syno hardware through VMM, but DSM 7 won't boot by one of jun's loaders. I know it's a complicated answer and if we knew where something was going wrong already we could work on a fix, but it's interesting to me and makes me wonder what exactly VMM is emulating/doing when booting Virtual DSM images. Obviously whatever it does makes Virtual D
  4. OK, any idea why DSM v7 works then on VMM running on Xpenology but we can't boot DSM 7 directly with loaders? Is it because the issue with DSM 7 not booting directly with 1.04 loader is the changed kernel rather than potential changed "checks" for real syno hardware?
  5. Ahh okay, yeah it was the first one. So seems to do with DSM 6.1, although I'm assuming unless major changes were made to how they check, it still checks in some similar way by verifying components, devices, some parts of the code, etc. I guess the question is..... where is the check function implemented and when does it run? I don't have a deep understanding of virtualization back ends but wouldn't a VMM based on KVM/QEMU have some sort of "loader" that boots the VDSM images? And that loader would have to emulate DSM hardware (assuming VDSM uses same checking mechanisms
  6. I believe I saw a post by @jun on this forum from a while ago about the current loader that said part of the check is DSM checks for a certain combination of components to verify if it is booting on legit hardware so he found a way to modify each piece of the code that does so to trick Xpenology into thinking it is seeing legit syno components/hardware. Also, since you are @Vortex seem to know what you're talking about.... I'll bring up a point I made previously on another thread. Do you think there is anything that can be gathered from Synology's Virtual Machine Manager in terms o
  7. Yeah my hope is more that Synology implementing this features provides resources to jun to implement a loader for DSM 7 since Synology will have to make a native "loader" of their own to boot DSM on ESXi, rather than actually using DSM that way as a replacement for Xpenology. However, I still would love to see Synology release an official "private cloud" version of DSM like Qnap did for their QuTS. For what I use DSM for, I would gladly pay Synology like people do for Qnap for the ability to run DSM on an ESXi VM.
  8. No, I really mean for DSM OS full image backups to run on a hypervisor as DSM, not just backups of VMs and bare metal like ABB does now. Synology said it themselves in this video (watch from 13:15 mark). Hopefully they actually pull through with coming out with that feature. There is a little note on bottom of video that says Coming Later in 2021 so we'll see but I am hopefully this code/feature either eliminated the need for Xpenology on ESXi or provides code that Xpenology can use to much better make a bootloader for ESXi DSM installs.
  9. I'm wondering if there is code/files in Virtual Machine Manager that can assist with developing a better loader, especially one that works with DSM 7. VMM can obviously deal with VDSM so there has to be some sort of "bootloader" as part of VMM that is capable of spinning up a VM of DSM. What I am more intrigued about though is the supposed plan for DSM 7 full image backups having the option to restore directly to and boot on hypervisors like ESXi and Hyper-V. Synology said themselves in one of their DSM 7 announcement videos about backups that Active Backup for Business will be abl
  10. Just a thought that maybe prompts a discussion or further looking into on a loader for DSM 7.0.... Is there something that can be reverse engineered out of Synology Virtual Machine Manager package that can be used towards a loader to boot 7.0? I'm assuming there is some sort of code/BIOS emulator in VMM for booting Virtual DSM.
  11. You can zero out the extra space in the VMDK from DSM then use ESXi commands to decrease the size of VMDK. I have done this with Windows and Linux with following guide in past and I am 99% sure I tried with DSM in past too and it worked, but use those commands with caution. Have a backup first. Hope this helps.
  12. I have 1.04b loader running DSM 6.2.3 on ESXi v7. One of my main data volumes in DSM is a single virtual disk, living on a vSAN datastore. ESXi was updated to v7 U1a and vSAN needed to update the on-disk format of all VMDKs/VMs on the datastore I guess. It is still working on this process of updating the format of vSAN disks but I guess the process of it doing this, causes DSM to think the volume has crashed. The VMDK is still mounted to DSM, I can still read data from the volume, but Storage Manager reports a crash, and I can't do anything other than hit remove and delete the stor
  13. I am running docker on a VM with Alpine OS. The VM host is ESXi v7.0.0. Only issue I found so far was the first run of container had some error about something missing (don't remember the exact error) but when I restarted the container then it all loaded and worked fine. DSM installed with no issue. Happy to test 3617xs and 918+ implementations when you have them, if that helps you.
  14. This is awesome! Thanks for your work on this. It worked for me. Is there a way to make it work with 1.04b loader for DS918+?
  15. This is a great point. One time fee would be nice for us.... but not for them. Hopefully the recurring revenue like that will allow them to improve QTS constantly and make it better, faster.