Mittel Posted February 22, 2015 Share #126 Posted February 22, 2015 And by the way, does the exportation - importation appliance worked without any issue during the migration ? Thanks a lot! Quote Link to comment Share on other sites More sharing options...
jagwaugh Posted February 23, 2015 Share #127 Posted February 23, 2015 Just noticed something strange tonight. If I start a VM (in this case a Win XP machine), it slowly fills up /dev/md0. Note, the VM itself is stored on /volume1/Virtualmachines, but something must be generating log or temp files at an alarming rate. I couldn't login to the DSM GUI because the volume was full. The space does not get cleared down when I stop theVM, only when I restart the NAS itself. This only started happening since I upgraded to DSM5.1, The VMs worked fine before the upgrade, and the md0 didn't get filled up. Since the DSM Update the VMs are a lot slower than they were before. Anyone else seen this? Andrew Quote Link to comment Share on other sites More sharing options...
tomcarmen Posted February 23, 2015 Share #128 Posted February 23, 2015 today and ' happened to me .. but I had imported a virtual machine and thought it was it .. rather than what you say to be like you. to me with windows 7 sorry for my bad english nb.. sorry .. a few posts above ... find how to change administrator password ... have under eyes Quote Link to comment Share on other sites More sharing options...
Mittel Posted February 24, 2015 Share #129 Posted February 24, 2015 Actually, I tried on a VMware the new DSM5.1 and the package and it works. Unfortunately, I cannot import any appliance, VitualBox keeps loading it forever.. Did anyone have the same problem? Thanks Quote Link to comment Share on other sites More sharing options...
jagwaugh Posted February 24, 2015 Share #130 Posted February 24, 2015 Mittel, Did you change the storage location to somewhere other than the default? The default stores the vms in /root/Virtualbox (or similar), the point being that it is on /dev/mdo which is the "system" disk, and doesn't have much space. Andrew Quote Link to comment Share on other sites More sharing options...
jagwaugh Posted February 24, 2015 Share #131 Posted February 24, 2015 Further to my earlier post about md0 filling up: After I upgraded to DSM51 virtualbox wasn't working anymore, so I uninstalled it, then reinstalled it and updated the modules. Since then: The md0 fills up to 100% in about 30-45 minutes if I use a bridged network, it does NOT happen with NAT (this did not happen before DSM51) The VM cannot reach the internet with bridged connection (it could before the upgrade to DSM5.1) The VM CAN reach the internet if I use NAT. VBoxManage command is not in the PATH (it was before the DSM upgrade) Has anyone else had the same issues? I'm wondering if something went wrong with the installation of virtualbox, although there were no error messages). Seba? Andrew Quote Link to comment Share on other sites More sharing options...
Mittel Posted February 25, 2015 Share #132 Posted February 25, 2015 Mittel, Did you change the storage location to somewhere other than the default? The default stores the vms in /root/Virtualbox (or similar), the point being that it is on /dev/mdo which is the "system" disk, and doesn't have much space. Andrew Actually I did but still not working. Quote Link to comment Share on other sites More sharing options...
jagwaugh Posted February 25, 2015 Share #133 Posted February 25, 2015 Mittel, Where did you install the package from, and did you upgrade the modules after installing? Can you create a new VM, as opposed to importing? Andrew Quote Link to comment Share on other sites More sharing options...
Mittel Posted February 25, 2015 Share #134 Posted February 25, 2015 Mittel, Where did you install the package from, and did you upgrade the modules after installing? Can you create a new VM, as opposed to importing? Andrew I downloaded the package on page 11 made by dodo-dk. Actually I don't see where I can update it, I guess this is already the latest version for dsm 5.1 I have just noted that I cannot create 64bits virtual machine! only 32bits! I guess it is the reason. Now why I cannot do it, I have no idea. Quote Link to comment Share on other sites More sharing options...
jagwaugh Posted February 25, 2015 Share #135 Posted February 25, 2015 Mittel, Does your xpenology box show as a DS3615xs in Synology Assistant? (i.e. are you using the 64 bit xpeno?) What does "cat /var/log/vbox.log" show? I'm not sure if you still need to scp the modules or not with the latest download from dodo, did you? Andrew Quote Link to comment Share on other sites More sharing options...
dodo-dk Posted February 25, 2015 Share #136 Posted February 25, 2015 Hi, the lastest spk in Page 11 is the Same as Seba but with updated Kernels. In my system it works now over a week Without reboot and without Problems. 3 Guest Systems are Running. 64Bit Too. Quote Link to comment Share on other sites More sharing options...
jagwaugh Posted February 25, 2015 Share #137 Posted February 25, 2015 I suspect I may have an outdated spk then, I am just downloading and will try a remove/install with the latest .spk Andrew Quote Link to comment Share on other sites More sharing options...
Mittel Posted February 25, 2015 Share #138 Posted February 25, 2015 Mittel, Does your xpenology box show as a DS3615xs in Synology Assistant? (i.e. are you using the 64 bit xpeno?) What does "cat /var/log/vbox.log" show? I'm not sure if you still need to scp the modules or not with the latest download from dodo, did you? Andrew There is no 32bits version, so I guess I have the 64bits When I type cat /var/log/vbox.log i get a bunch of those lines: 02:22:43.964194 SQW03 Processing connection from IP=127.0.0.1 socket=11 (2 out of 3 threads idle) 02:22:46.966576 SQPmp Request 3252 on socket 10 queued for processing (1 items on Q) 02:22:46.966617 SQW03 Processing connection from IP=127.0.0.1 socket=10 (2 out of 3 threads idle) 02:22:48.326794 SQPmp Request 3253 on socket 11 queued for processing (1 items on Q) 02:22:48.327042 SQW02 Processing connection from IP=127.0.0.1 socket=11 (2 out of 3 threads idle) 02:22:49.973308 SQPmp Request 3254 on socket 10 queued for processing (1 items on Q) 02:22:49.973348 SQW03 Processing connection from IP=127.0.0.1 socket=10 (2 out of 3 threads idle) 02:22:52.984255 SQPmp Request 3255 on socket 11 queued for processing (1 items on Q) 02:22:52.984295 SQW02 Processing connection from IP=127.0.0.1 socket=11 (2 out of 3 threads idle) 02:22:53.328508 SQPmp Request 3256 on socket 10 queued for processing (1 items on Q) 02:22:53.328545 SQW01 Processing connection from IP=127.0.0.1 socket=10 (1 out of 3 threads idle) 02:22:56.123417 SQW03 Processing connection from IP=127.0.0.1 socket=13 (2 out of 3 threads idle) Quote Link to comment Share on other sites More sharing options...
jagwaugh Posted February 25, 2015 Share #139 Posted February 25, 2015 So, after removing virtualbox, a reboot, and reinstalling from the latest download (file name: virtualbox-x64-4.3.12_DSM-5.1_fixed.spk) everything seems to be working fine again. After the reinstall all my VMs and settings were still there in the web interface, bridged mode now works, and the md0 filling up issue is gone. The .spk that I had installed from was an earlier version, named:virtualbox-DSM5.1-4.3.12-93733.spk - I am not sure where I downloaded it from, but it was apparently not "fixed", as the latest download _is_ Mittel, what was the name of the .spk file you had installed? Andrew Quote Link to comment Share on other sites More sharing options...
Mittel Posted February 26, 2015 Share #140 Posted February 26, 2015 So, after removing virtualbox, a reboot, and reinstalling from the latest download (file name: virtualbox-x64-4.3.12_DSM-5.1_fixed.spk) everything seems to be working fine again. After the reinstall all my VMs and settings were still there in the web interface, bridged mode now works, and the md0 filling up issue is gone. The .spk that I had installed from was an earlier version, named:virtualbox-DSM5.1-4.3.12-93733.spk - I am not sure where I downloaded it from, but it was apparently not "fixed", as the latest download _is_ Mittel, what was the name of the .spk file you had installed? Andrew Hi I think I installed this one virtualbox-x64-4.3.12_DSM-5.1_fixed.spk Quote Link to comment Share on other sites More sharing options...
Mittel Posted February 26, 2015 Share #141 Posted February 26, 2015 So, after removing virtualbox, a reboot, and reinstalling from the latest download (file name: virtualbox-x64-4.3.12_DSM-5.1_fixed.spk) everything seems to be working fine again. After the reinstall all my VMs and settings were still there in the web interface, bridged mode now works, and the md0 filling up issue is gone. The .spk that I had installed from was an earlier version, named:virtualbox-DSM5.1-4.3.12-93733.spk - I am not sure where I downloaded it from, but it was apparently not "fixed", as the latest download _is_ Mittel, what was the name of the .spk file you had installed? Andrew Hi I think I installed this one virtualbox-x64-4.3.12_DSM-5.1_fixed.spk Quote Link to comment Share on other sites More sharing options...
DKeppi Posted February 26, 2015 Share #142 Posted February 26, 2015 Installed the virtualbox-x64-4.3.12_DSM-5.1_fixed.spk on my "real" Synology! When i start the VM my Synology DS415+ is restarting on its own! My package from this post is working very well on "real" synology boxes Maybe its the exactly reverse situation on "fake" Synologys Quote Link to comment Share on other sites More sharing options...
jagwaugh Posted February 26, 2015 Share #143 Posted February 26, 2015 DKeppi, I presume you edited the INFO file in the .spk, changing the arch= from "bromolow" to "avoton", otherwise I don't think the install will contine, but it is worth asking. Is the reboot immediate, or does it take a while? What happens if you remove the "fixed" spk and install the package via packagemanager? (Add http://spk.synologyitalia.com/ to your Synology NAS Package Center sources) If the "fixed" package is specific to xpenology then it may be making calls to modules that are not present on a real synology. Andrew Quote Link to comment Share on other sites More sharing options...
DKeppi Posted February 27, 2015 Share #144 Posted February 27, 2015 The reboot is immediate! Package from spk-repository did not work because its for 5.0, but it doesnt matter because my spk works very well! Have a nice weekend! Quote Link to comment Share on other sites More sharing options...
jagwaugh Posted February 27, 2015 Share #145 Posted February 27, 2015 DKeppi, Am I correct, on a real ds415+, with the real synology DSM5.1, and the fixed spk, the machine spontaneously reboots when you start a VM? What do /var/log/vbox.log and vboxscripts.log show? Are these imported VMs? Any chance you are importing a 64bit VM, but your VB host is 32bit - this would cause a reboot in VB 4.0.18, perhaps the error is back. Try creating a VM from scratch, single disk, booting from a simple install .iso like DSL or such, can you complete the install? Will the VM run? Andrew Quote Link to comment Share on other sites More sharing options...
DKeppi Posted February 27, 2015 Share #146 Posted February 27, 2015 Yes you are right Andrew! I created the VM's with virtualbox spk from seba, so they are not imported (all 64bit)! Sorry i have no logs from that version, i deinstalled it and installed my spk! Quote Link to comment Share on other sites More sharing options...
Mittel Posted February 28, 2015 Share #147 Posted February 28, 2015 Can anyone say which spk to use? I am a little bit lost now as we are mixing xpenology and synology ... Any other baremetal user with dsm5.1 and Virtualbox working properly? Quote Link to comment Share on other sites More sharing options...
dodo-dk Posted February 28, 2015 Share #148 Posted February 28, 2015 What system du you have? Real Synology or XPEnology? On XPEnology (XPEnoboot 5.1-5022.2 / DSM 5.1-5022 Update 2 / X64 DS3615xs) install this: https://mega.co.nz/#!RcJShazA!C1Qax4M6o ... 72ibUa_0g4 Dodo Quote Link to comment Share on other sites More sharing options...
dodo-dk Posted February 28, 2015 Share #149 Posted February 28, 2015 (edited) Hi, i have compiled the VirtualBox and Kernels with newer Version. The newest phpvirtualbox i have added too. Virtual Box 4.3.22 (98236) phpVirtualBox 4.3-2 Here you can Download it: https://mega.co.nz/#!4F5gRRrI!EaCkp_7ct ... ByJQMlUP6Q Please Stop all Virtual Machines and the VirtualBox before you deinstall the old VirtualBox. Testet on XPEnology (XPEnoboot 5.1-5022.2 / DSM 5.1-5022 Update 2 / X64 DS3615xs) Use it of your own risk. Dodo Edit: I have add arch="x86 cedarview avoton bromolow" in the SPK and updated the Download link. Edited February 28, 2015 by Guest Quote Link to comment Share on other sites More sharing options...
Mittel Posted February 28, 2015 Share #150 Posted February 28, 2015 Hi, i have compiled the VirtualBox and Kernels with newer Version.The newest phpvirtualbox i have added too. Virtual Box 4.3.22 (98236) phpVirtualBox 4.3-2 Here you can Download it: https://mega.co.nz/#!pV4HCKBJ!DF29ArX2b ... jugqKcrzpw Please Stop all Virtual Machines and the VirtualBox before you deinstall the old VirtualBox. Testet on XPEnology (XPEnoboot 5.1-5022.2 / DSM 5.1-5022 Update 2 / X64 DS3615xs) Use it of your own risk. Dodo Ok thanks a lot! 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.