robvantol

Transition Members
  • Content count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About robvantol

  • Rank
    Newbie
  1. I tried to change the vender file of my image. I am running DSM 4.3 on Proxmox The strange thing is that xpenology doesn't seem to care what mac address is configured in the Proxmox VM settings. Even if there is a mismatch it will show the original pre-configured mac address of my boot image in the ARP table. When i change the vender file, my network activity of xpenology is completely gone. I did that by mounting the boot image on xpenology and copied the vender file to my desktop (linux) I changed the values with wxHexEditor and copied the file back to my xpenology boot image. Then i did a reboot of the VM. Is there anyone having the same problems with a virtual xpenology?
  2. Installation on Proxmox (with physical disk assignment)

    I have my system finally running well without having any problems at all. I added an extra storage controller to my system and configured the pass through to my xpenology VM. I also added an extra NIC which is also forwarded to the VM. I tried many setups with forwarded harddrivers. They all crashed almost instantly. After spending a lot of time searching on google, i found a really obvious cause. xpenology is a deticated system. it wants to control the hardware of your system. Proxmox wants to do the same thing. The result is a conflict. The conflict on storage controller is the reason the raid set was crashing and the disk io was really poor. After the modifications a did the performance is almost the same as a system without virtualization. network throughput is stable at almost 80 mb/s and peaks up to 100mb/s. The VM has 2 CPU cores which are running between 5% and 40% usage and memory usage is about 800MB
  3. Xpenology on Proxmox : Unaligned AIO/DIO on inode ...

    I have xpenology running on proxmox. just take a look at my original post. viewtopic.php?f=2&t=733 There are some facts you need to know. 1. Virtualisation platforms will lead to loss of performance. It is obvious because there is an extra system running which is taking some CPU power en memory. It will also reduce your network throughput because it's a virtual adapter. 2. Proxmox doesn't have the chipset support which is needed for xpenology. Result: dramatic disk io performance and raid crashes (level 5 crashes when you copy more then 4GB on it.) Now there is a way to make it work. I was even suprised with the performance of my system. Let's start with my setup: Mainboard: Gigabyte H77 Mainboard CPU: Intel Xeon 1230v2 Mem: 8GB DDR3 System hdd: 2x 500GB RAID1 (software mdadm) Storage hdd: 4x 2TB RAID 5 (software on xpenology) NIC: 1x 1000mbit onboard & 1x 100 mbit pci storage controller: Highpoint 4 port sata controller The trick is that Proxmox wants to control the hardware. Xpenology wants to do the exact same thing. Result is that the hardware is commanded from 2 sides. I added an extra storage controller to my system. It's configured as pass through to my xpenology VM. I also forwarded my 1000mbit NIC to my xpenology VM. Now xpenology has full control on the storage harddrives. All my problems i had before (my previous post) are gone. The network throughput is stable at almost 80 mb/s and peaks to 100 mb/s I gave the VM 2 CPU cores and 1GB of RAM and it's running really well.
  4. Installation on Proxmox (with physical disk assignment)

    ESXi supports my hardware on v5.1 U1. ESXi doesn't have a webbased GUI. The only way to manage the VM's, is with the VSphere client which requires Windows. I don't want any Microsoft Machine in my own network , not even a VM. I tried running Proxmox on KVM virtualization. That could be the reason why the RAID set degrades. Has anyone tried XPEnology on OpenVZ or KVM Paravirtualized?
  5. Installation on Proxmox (with physical disk assignment)

    I tried to build a RAID-5 with 4 physical drives. I assigned my harddrives by-id because a RAID-5 makes multiple partitions on each disk. I managed to install and configure the system completely but after 1 data copy to XPEnology, the RAID-5 set degrades almost immediately. The Synology DSM webinterface is now gone and i get a 500 Internal Server Error. When I re-install Synology DSM we shows a degraded RAID-5 which I cannot rebuild. My setup: Asus P8H77-I (ITX) mainboard Intel Xeon E-1230V2 quad-core 8GB DDR3 memory NVidia passive graphic-card 1x 320GB harddrive (OS + VM's) 4x 2000GB hardrive (RAID-5 deticated XPEnology) The only Virtual platform which runs Synology RAID-5 is Virtualbox. The option which causing this is the fixed chipset driver, i think. Is there an option for fixed chipset in the configuration of a VM?
  6. Installation on Proxmox (with physical disk assignment)

    ========================================== UPDATE ========================================== HDD Spindown is working within Proxmox Since the Synology VM can't control your hardware because of Proxmox, Proxmox must spin down your harddrives when idle for x time. You can do this with "hdparm". 1. Install hdparm --> login SSH (root@[your proxmox ip] --> apt-get install update --> apt-get install hdparm 2. Now configure the idle time for spin down (this goes for each drive) ** In the original post above I assigned /dev/sdb1 and /dev/sdc1 to my VM ** --> hdparm -S 120 /dev/sdb --> hdparm -S 120 /dev/sdc ** -S means standby and 120 means 10 minutes ** ** In this case you don't specify a partition number of the drive, ** ** because we want de whole drive to spin down. for example /dev/sdb or /dev/sdc etc. **
  7. Hi there, I am new to XPEnology and I wanted to test an installation on Proxmox VE with my physical harddisks assigned to the XPEnology Virtual Machine. My test is succesfull so far, so here is a how to: ================================================================================================= READ THIS HOW TO CAREFULLY BEFORE YOU START. OTHERWISE YOU CAN HAVE SOME EXTRA UNNEEDED WORK ================================================================================================= 1. Download and unpack the XPEnology package for VirtualBox.http://yadi.sk/d/T3MbhAIK22OPL 2. Install Virtualbox on your PC. ( I did this with Linux Mint ) 3. Create a virtual machine in proxmox for XPEnology with the following settings: Tab General: --> Give the vm any name you want. --> Remember the VM ID (we need it later on) Tab OS: --> Choose "Other OS Types" Tab CD/DVD: --> Choose: "Do not use any media" Tab Hard Disk: --> Storage: local --> Size: 1GB --> Format: Raw Disk Image (RAW) Tab: CPU --> assign the cores you want Tab: Memory --> assign as much memory you want (I recommend a minimum of 1GB for good performance) Tab: Network --> Choose: Birdged mode --> Model: Intel E1000 --> MAC Address: 00:11:32:08:D6:2A Confirm your VM and let Proxmox create it (you do not need to start it) 4. Locate the .vdi file of the XPEnology package and remember its location 5. Open a terminal window and go to the .vdi file location 6. Convert the .vdi to a RAW based .img file with the following command --> VBoxManage clonehd --format RAW [XPEnology filename].vdi SynoBoot_Proxmox.img 7. Copy the file to your proxmox machine with SSH --> scp SynoBoot_Proxmox.img root@[your proxmox ip]:/var/lib/vz/images/[your vm number] 8. Rename the original disk file --> login SSH ( ssh root@[your proxmox ip] ) --> cd /var/ib/vz/images/[your vm id] --> ls (this will get you a list of files) --> mv [the .raw disk file] backup-[the same filename] 9. Rename the SynoBoot file --> mv SynoBoot_Proxmox.img [the original .raw filename] ========================================================================================== THIS IS THE POINT FOR YOU TO DECIDE WHAT STORAGE YOU WANT TO ASSIGN TO YOUR XPENOLOGY VM ========================================================================================== I choose to assign my 2 physical 500 GB disks to the vm. It is also possible to assign an virtual harddrive in Proxmox 10. Prepare your physical disks for your XPEnology VM --> login SSH ( ssh root@[your proxmox ip] ) --> fdisk -l (will het you a list of all the storage devices) **Look carefully for your physical drives, you can look at capacity and partitioning to be sure **The harddrives must be totally empty without any partition on it in my case my physical harddisks are "/dev/sdb1" and "/dev/sdc1" --> fdisk /dev/sdb1 (you will be asked for a command, type an n and follow all the defaults given) --> do the same for all your physical harddisks 11. Assign the disks to your XPEnology VM --> qm set [your vm id] -ide[storage index number] /dev/sdb1 You can find the storage index number in your proxmox dashboard located at your XPEnology VM Hardware. Your local storage is most likelly IDE0 so you can start at IDE1 and so on. --> Repeat this step for all your physical harddrives ( note that the index number must be unique for each drive) 10. Start your VM in Proxmox --> it will say "booting kernel" (this is normal because there is no operating system yet) 11. Download Synology assitent http://www.synology.com/support/download.php?lang=enu&b=12%20bays&m=DS3612xs 12. Start Synology assistent and let it search your network for your XPEnology VM 13. right-click your XPEnology VM --> Choose: Install --> When prompted for the software choose your .pat file from the XPEnology download package --> Complete further steps ** In my case installation went wrong on the last step "writing configuration files" ** As far as I could trace the problem, it's caused by the Virtual Machine setup. Synology itself is not able to restart the system. ** When this happens with your installation, it will brick the virtual diskimage. The solution is to repeat the Steps 7 / 8 / 9. ** This will bring back your VM and it should run without anny problems after that because DSM and it's config are on your storage harddrives. ================================================================================================= SOME WORK IN PROGRESS: ================================================================================================= - Spinning down of the physical harddrives ( Synology has no control of the hardware because it's a vm. Promox must spindown the harddrives ) - Backup the XPEnology VM ( Backing up within proxmox console has bricked my VM, it's really easy to recover with steps 7 / 8 / 9 but it's not as it should be ) - Updating DSM ( I tried to update DSM to 4.2.xxxx but it reported an error. This is really valueble for me because I do not want to re-install for every DSM update ) Any help with the last points is much appreciated