Passthrough hardware raid volume to VM

[Drag_and_Drop]

Hi,
I currently migrating my physical Windows 2008 R2 terminal Server and File server to Proxmox but I stuck on adding my 8 x 3 TB Fileserver RAID5 Volume managed by an Adaptec 24 Port SAS/SATA controller to my VM.
I managed to mount the volume to my Proxmox host, but how I add it to the vm?
The volume is currently NTFS formatted.

 

[Utking]

Hi,
I currently migrating my physical Windows 2008 R2 terminal Server and File server to Proxmox but I stuck on adding my 8 x 3 TB Fileserver RAID5 Volume managed by an Adaptec 24 Port SAS/SATA controller to my VM.
I managed to mount the volume to my Proxmox host, but how I add it to the vm?
The volume is currently NTFS formatted.

Something like this i have been out after as well!

Although i have two glusterfs volumes created, one for VM's and one for file storage, it's the last one i want to pass trough to my VM's

Any help guys?

 

[udo]

Hi,
look here: http://pve.proxmox.com/wiki/Physical_disk_to_kvm
But then the VM has access only - and live migration don't work anymore...

Udo

 

[Utking]

Hi,
look here: http://pve.proxmox.com/wiki/Physical_disk_to_kvm
But then the VM has access only - and live migration don't work anymore...

Udo

Hey! And thanks for a quick response! I tried this but got an error that my volume was a directory, and that is not supported :/ dunno what im doing wrong..

About not being able to migrate, it should work as long as it's a glusterfs volume? It's accessable from both nodes, so I don't quite understand why it shouldn't work:/

Thanks!

 

[udo]

About not being able to migrate, it should work as long as it's a glusterfs volume? It's accessable from both nodes, so I don't quite understand why it shouldn't work:/

Hi,
why it's don't work is quite easy: with path trough you provide an block-device to an VM (like an real hdd, or an lv) and not an Filesystem.
If you want to provide an filesystem, you could use something like nfs, which you can mount inside the VM.

Sorry, with gluster I haven't any experiences, but use the search-function. Such an scenario is disccussed more than one time.

Udo

 

[Utking]

Hi,
why it's don't work is quite easy: with path trough you provide an block-device to an VM (like an real hdd, or an lv) and not an Filesystem.
If you want to provide an filesystem, you could use something like nfs, which you can mount inside the VM.

Sorry, with gluster I haven't any experiences, but use the search-function. Such an scenario is disccussed more than one time.

Udo

Ok so NFS is the only way to go then? Hmm, maybe i'll have to try this then Yeah i've been searching both this forum, as well as servethehome, reddit and google for a month now! I'm learning a lot, but i still haven't found my completely solution as of yet!

I highly appreciate answers like this tough! So thanks for taking your time

Edit: At least i got it working with containers, if anyone has a solution for vm's i would be very happy! But the solution for containers is to add a line to ( /etc/pve/lxc/###.conf )

Add this line : ( lxc.mount.entry = /host/mount container/mount none bind,create=dir 0 0 )
just replace the mounts with your own.

Thanks to your_tv_is_too_high from reddit! ^^

 

[Drag_and_Drop]

Yeah I did it in the end also with NFS. Now I like it actually even more than the "fixed to a VM" version. And with Server 2016 the NFS client works pretty well, didn't saw any difference in performance or stability + you can access the share also with Linux VMs and do some awesome things with scrips :-D

Tutorial for NFS with Windows 2016: https://www.rootusers.com/how-to-mount-an-nfs-share-in-windows-server-2016/