Jump to content
XPEnology Community

Simon95

Rookie
  • Posts

    5
  • Joined

  • Last visited

Recent Profile Visitors

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

Simon95's Achievements

Newbie

Newbie (1/7)

0

Reputation

  1. Thanks for your answer. Initially I set it to 2 cores, but seeing the poor performance I set it to 4 cores, without noticing any benefits. From the windows task manager of the Vm I notice that the CPU is always at 100% and the maximum value is 2Ghz. It is standing there
  2. Goodmorning everyone. I am making an Xpenology device with this features: - Jun's Loader v1.03b loader DS3617xs - DSM version 6.2 - Motherboard: AsRock Q1900M - Processor: Intel Quad-Core J1900 (2 GHz) - RAM: 8Gb - Hard Disc: 2X SeaGate IronWolf 4Tb (each) I have an old PC based on intel core 2 duo and 4gb of ram with Windows 10 running a management software. I created an image of this PC and poured it into an instance of Synology Virtual Machine Manager with this specs attributed: - 4 CPUs - 4Gb RAM - 100Gb Space To my surprise, I found that the operation was successful and the system transferred to Vm works perfectly and the clients pc connect to the management system without problems. The only problem I noticed is that the management software is much slower. Example: From a client PC, to open the supplier list, the time taken before (old "server" pc) was about 0.5s, now it takes 1.5s. It is not a disproportionate time, but the difference is felt and it is annoying. What is the cause of this problem? Virtual Machine Manager Limit? Disc speed limit? (the new ironwolf and the WD red on the old "server" pc are all at 5.400rpm, so I don't think that's that) CPU J1900 limit too low? (as I believe it is) If I replace the motherboard and CPU with something more performing (GIGABYTE GA-H81M-DS2 + Core i7-4790K for example), could the performance of the virtualized instance increase? Thanks a lot to everyone for your advice
  3. Goodmorning everyone. I am making an Xpenology device with this features: - Jun's Loader v1.03b loader DS3617xs - DSM version 6.2 - Motherboard: AsRock Q1900M - Processor: Intel Quad-Core J1900 (2 GHz) - RAM: 8Gb - Hard Disc: 2X SeaGate IronWolf 4Tb (each) I have an old PC based on intel core 2 duo and 4gb of ram with Windows 10 running a management software. I created an image of this PC and poured it into an instance of Synology Virtual Machine Manager with this specs attributed: - 4 CPUs - 4Gb RAM - 100Gb Space To my surprise, I found that the operation was successful and the system transferred to Vm works perfectly and the clients pc connect to the management system without problems. The only problem I noticed is that the management software is much slower. Example: From a client PC, to open the supplier list, the time taken before (old "server" pc) was about 0.5s, now it takes 1.5s. It is not a disproportionate time, but the difference is felt and it is annoying. What is the cause of this problem? Virtual Machine Manager Limit? Disc speed limit? (the new ironwolf and the WD red on the old "server" pc are all at 5.400rpm, so I don't think that's that) CPU J1900 limit too low? (as I believe it is) If I replace the motherboard and CPU with something more performing (GIGABYTE GA-H81M-DS2 + Core i7-4790K for example), could the performance of the virtualized instance increase? Thanks a lot to everyone for your advice
  4. I was able to locate the problem and fix it. I did not enter the new MAC address on the NIC 1. Now it works correctly. Thanks a lot for the tutorial.
  5. Hello. Thanks for your tutorial, it's very helpful. I'm having a problem at step 8. I installed synoboot.img ((for DS918 +) - v1.04b) on the 50Mb partition, restart, when prompted I select the third line DS918 + 6.2.1./6.2 VMWare / ESXI, I see: Intro: .... Happy Cracking .... screen will stop updating shortly. Find.synology.com screen does not find anything, and the DSM IP does not appear in the router DHCP client table. I checked in the VM Network section and the VM network of the Vm in question is green, therefore connected. I don't understand why I can't find it in the local network. Am I wrong version of the synoboot? I ask you if you can help me. Thank you very much
×
×
  • Create New...