• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Is this doable?

U

/usr/home

Supreme [H]ardness
Joined
Mar 18, 2008
Messages
6,160
When I first built my server (see sig for specs), I tried playing around with ESXi 4 and 3.5. What I was trying to do was have one VM for a file server, and then other VMs for DC and mail server, etc. I installed ESXi to a 37 GB U320 SCSI drive and then proceeded to create my VMs. Everything went fine until I wanted to add all 4 of the SATA drives to the storage "pool" or whatever you want to call it on the VM. They are all attached via the onboard SATA ports. I couldn't figure out how to get the VM to see the drives as a native hard drive. I remember reading something about it and if I remember correctly it wasn't doable or something like that. Is this possible with ESXi or Hyper-V? These drives are currently formatted as NTFS and have data on them that I don't want to lose or have to backup to other drives. (The data is backed up, but for simplicity I want to leave the formatting of them alone.)

Cliffs:
Want to let a VM see the 4 SATA drives as if they were hard drives in the VM. Ex: they'd show up in the disk management as Drive1, Drive2, Drive3, etc and you can assign them drive letters and access them. I only need the one VM to be able to access them, not all VMs. Is it doable?
 
What you are wanting to do is know as a RAW LUN mapping under VMWare or a direct drive mapping under Hyper-V.

VMWARE ESX/ESXi doesn't always play well with onboard SATA controllers. Depends on the board. If your controller isn't officially supported, pretty much all the really cheap add-in SATA controllers are. If ESX/ESXi doesn't see the drives at all, you can't make them avaiable for RAW mapping. If ESX sees the drives, adding them with RAW mapping is trivial.

To make drives avaiable under direct mapping is trivial under HYyper-V as well. Off-line the drive on the host in disk managment. Attach it to the VM via the matching disk number in the drop down in the Hyper-V managment tool.
 
Forgot to mention, the board is a Tyan S2882-D. Sil3114 is the SATA controller. If I remember correctly I think it did see the drives. I'm not sure to be honest, I'd have to try it again.
 
nessus said:
What you are wanting to do is know as a RAW LUN mapping under VMWare or a direct drive mapping under Hyper-V.

VMWARE ESX/ESXi doesn't always play well with onboard SATA controllers. Depends on the board. If your controller isn't officially supported, pretty much all the really cheap add-in SATA controllers are. If ESX/ESXi doesn't see the drives at all, you can't make them avaiable for RAW mapping. If ESX sees the drives, adding them with RAW mapping is trivial.

To make drives avaiable under direct mapping is trivial under HYyper-V as well. Off-line the drive on the host in disk managment. Attach it to the VM via the matching disk number in the drop down in the Hyper-V managment tool.
Click to expand...

you cannot add local disks as an RDM in ESX.
 
You must log in or register to reply here.
Back
Top