Hey everyone.
I am starting a thread on making Xpenology work on Hyper-V. Why? You can run Windows 8.1 Pro as a host, or even Hyper-V Server 2012 R2. One machine. Awesome NAS. Flexibility of a VM host or a Windows RDP machine, especially when aggregating networking.
The guide I used was posted in another thread but based on the ESXi version here.
Going to keep a little log of the steps:
1. Download the nanoboot.img file
2. Convert nanoboot.img to hyper-v vhd
3. Make a VM and attach nanoboot.vhd to the VM IDE O - This will not work on the SCSI controller.
4. Take drives and attach to the SCSI controller. You can use hyper-v disk pass-through guide or test with dynamically expanding virtual disks. I would recommend testing with the vhdx files for now.
5. Boot the VM
6. Select upgrade DSM
8. Select a version. I am working with DSM 5.0-4482
That worked and let everything install. When it game time to reboot, I've now got a black screen and blinking cursor.
Anyone get further than this?
I am starting a thread on making Xpenology work on Hyper-V. Why? You can run Windows 8.1 Pro as a host, or even Hyper-V Server 2012 R2. One machine. Awesome NAS. Flexibility of a VM host or a Windows RDP machine, especially when aggregating networking.
The guide I used was posted in another thread but based on the ESXi version here.
Going to keep a little log of the steps:
1. Download the nanoboot.img file
2. Convert nanoboot.img to hyper-v vhd
3. Make a VM and attach nanoboot.vhd to the VM IDE O - This will not work on the SCSI controller.
4. Take drives and attach to the SCSI controller. You can use hyper-v disk pass-through guide or test with dynamically expanding virtual disks. I would recommend testing with the vhdx files for now.
5. Boot the VM
6. Select upgrade DSM
8. Select a version. I am working with DSM 5.0-4482
That worked and let everything install. When it game time to reboot, I've now got a black screen and blinking cursor.
Anyone get further than this?