maelstromm

If this is similar to the 4.3 builds, have you tried replacing the boot .vdi file and restarting the machine?

Hi Trantor, tried to send you a PM to ask for your help with adding me as a member to edit the Wiki. I'd be glad to help out!!

It is likely. Have you just tried creating a 32bit VM with any other OS and see if you run into Kernel panic?

Good start, I made some edits Index - Getting started --What is Xpenology --Dictionary of Xpenology terms - Hardware -- Compatibility list / Driver support -- Driver request - Downloads --Stable builds --Experimental builds - Installation guides --General (USB) --Virtual Machines ---Esxi ---Virtualbox ---Hyper-V --Hardware Specific ---HP40/54 - Build your own kernel -FAQ --Updates --Security --Known problems etc -etc

I could help out with the wiki pages. I've written FAQs before so maybe I can be of some help. I've only just begun using Xpenology for the better part of a month using virtualbox but it's pretty fresh in my head considering I didn't exactly get all the information about installing without reading multiple posts or having others answer my questions. I see Andy (site admin) has a Wiki page but it's blank. Any other takers for topics?

From what I've read, which is conflicting, either the X2 4400+ doesn't have AMD-V or you need to enable IO-APIC in the processor tab. Are you running virtualbox as administrator mode?

My support to Gnoboot and Trantor as well. Their excellent work shouldn't be tarnished by a few ingrates.

Have you enabled virtualization in the BIOS? Have you tried using a different 64bit linux option like Debian?

No need to double post. Are you using the beta files? I found this guide better but used 2GB as memory for the VM instead http://www.wijngaard.org/virtual-synology-with-dsm-4-3/. Do you plan on using any physical disks or is your plan to only test using a VM before switching to a dedicated device?

Available in this thread http://xpenology.com/forum/viewtopic.php?f=2&t=1361&p=12750#p12750

I think I may have overstated the grub22 error. I followed the same guide and got past the first grub22 error. Unfortunately in the middle of migrating data, I got a volume crash claiming two of the hard drives had crashed. They are brand new drives so this was curious. I am now in the process of chkdsk on both the supposed crashed drives to see what went wrong. Thank god I had backups of everything. I only shut down the VM yesterday but saved a snapshot. I understand that there is no recovery from a crashed volume except through synology support. I'm not worried about data loss right now, I just don't want this to happen again when it is much harder to have backups.

I seem to be having trouble accessing the root file system using WinSCP. I'm running DSM 4.3 on Virtualbox with a fixed IP. The SFTP service is set to run with Port 22 in the Control Panel but I get errors like "Unexpected end of SFTP stream" in CyberDuck and "Is the host running an SFTP server" in WinSCP. I have no problem accessing the Shared Folders using SFTP, just not root. Ideas?

After finally getting through an initial painful data scrubbing that lasted 24 hours for 4x2TB drives with SHR, my intial testing has file transfers at about 50-55 Mb/sec on average. Not sure what I can do to up those numbers. Download station is able to fully achieve the 1.8Mbps download rate for nzbs. Pleased so far and will continue to do more testing. Now, if only there was a way to get WOL working and a restart without a Grub 22 error. Currently using Virtualbox v4.3.8 on Windows x64.

Gonna try this now. Do I still need to set up a dynamic drive in addition to the raw mapped drives? What is the ideal size? Thanks for your help so far!! Edit: Solved, looks like I missed a critical part of the instruction which was to set up a dynamic drive in addition to the physically mapped drives. Will now proceed to commence testing!

Did you have to remove (offline) the drives in windows before they would be recognized? Also, do the drives need to be formatted in any special way before they can be attached? I also seem to not be getting past the connection problem. Whether I use a bridge connection or not, synology assistant fails to correctly detect the VM's IP address. This only happens after it installs the software and says the DSM is rebooting. I get the grub 22 error causing me to shut down the VM, recopy the synoboot.vdi file and restart the VM. The synology assistant is still running during this time.

I am trying to set up a VM with raw disk access in Windows 8. I get a VERR_ACCESS_DENIED when I try to add the mapped drives. Perhaps I have not understood the instructions correctly but do the drives need to be mapped and added as vmdks? I would assume so like the ESXI builds. When I follow the instructions as listed in the OP, I get a connection error and diskstation is unable to take the bridged IP address.

Thanks XPEH!! I think I've got it conceptually . Now for actual implementation. I've finally got all the parts needed so I'll start with testing.

Thanks XPEH!! I think I've got it conceptually . Now for actual implementation. I've finally got all the parts needed so I'll start with testing.

I think I'm getting closer and closer to what I want to do but most of the guides don't make things clear how the ESXI datastore works in relation to the virtual machines space. Can you help answer a few questions: 1. Does space of the datastore impact how big the VM virtual disk can be? For example if server datastore is 64GB, will the largest possible virtual disk be 64GB or can it be more? I am considering using a spare 64GB SSD. 2. Based on what you're saying and reading through the Idiot's guide to installation, should all the drives (5x2TB) that will be used as part of the storage system be RDM-ed first? I assume then that this is where the DSM files will reside and not on the ESXI datastore?

I think I'm getting closer and closer to what I want to do but most of the guides don't make things clear how the ESXI datastore works in relation to the virtual machines space. Can you help answer a few questions: 1. Does space of the datastore impact how big the VM virtual disk can be? For example if server datastore is 64GB, will the largest possible virtual disk be 64GB or can it be more? I am considering using a spare 64GB SSD. 2. Based on what you're saying and reading through the Idiot's guide to installation, should all the drives (5x2TB) that will be used as part of the storage system be RDM-ed first? I assume then that this is where the DSM files will reside and not on the ESXI datastore?

Very helpful! I think I'm starting to get it but have more questions . Some background, I'm building a mini-itx system with an AMD 6400k processor and 4GB RAM. I think my main concern with the N54L was the slow processor. Sorry to hijack this thread. I would like to create a primary data store for xpenology (5x2TB + 1x1.5TB) to house media backups + files. I want to add two VMs for Windows and Ubuntu, one of which I plan to use for media playback i.e. XBMC. I was hoping to keep the Windows and Ubuntu VMs on a separate drive if possible which is why I wanted to use the SSD (my thinking is that this would greatly improve performance for the Windows VM). I understand how ESXI works theoretically, but confused about the physical location of the virtual disks to run each VM. I'm approaching this from a Windows perspective, hence the confusion.

I stumbled across your post and very interested in learning how to set up virtualization on a custom build that will be 90% of the time used to run xpenology. Based on your suggestion, are you suggesting that a spare 250GB HDD be used for the ESXI datastore only but the server itself would run on the USB drive? What is the recommended size for each VM? How fast should the data store drive be and would an SSD do a better job? My intended usage will be - xpenology, windows, and ubuntu. Thank you in advance!!