Support > User Customizations
UnRAID on VMWare ESXi with Raw Device Mapping
Veilus:
I been using 5.0 beta 8 on my esxi and has been working well. So i decided to try RC5 which told me to copy the two files over: bzimage and bzroot. Made a new .vmdk file and added it to esxi. It only gives me basic key and wont read my pro key. Not sure if its an esxi thing or rc5 thing. USB flash drive is mounted as well and added.
Johnm:
My guess would be you accidently named your VMDK "unraid"...
BetaQuasi:
Johnm is likely right... to be 100% sure in the future, if you still have your old, working VMDK.. simply shut down unRaid, mount that vmdk in another VM, copy the bzroot/bzimage files over, then remount it in unRaid. That way you shouldn't run into any issues.
johnodon:
--- Quote from: gfjardim on June 20, 2011, 04:07:46 PM ---With "Remote Tech Support" enabled, use WinSCP to connect to ESXi, and add there two lines to the /etc/vmware/passthru.map file:
--- Code: ---# Marvell Technologies, Inc. MV64460/64461/64462 System Controller, Revision B
11ab 6485 d3d0 false
--- End code ---
--- End quote ---
Sorry guys...I know that this is an old thread but it is also the most relevant to this question...
I am running ESXi 5.1 and it is seeing both of my MV8 as well as my onboard Marvell controller (same exact chipset as the MV8) just fine. Do I still need to make the edit shown above or is that only to get ESXi to be able to passthrough the controllers. I know that I still need to edit the VMX but wasn't sure if the prior step is required for me.
John
Ice_Black:
Someone said alternative to Raw Device Mapping is to present normal VMDK with a thick eager - no performance benefit of a hack RDM versus a thick eager VMD
Is that true?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version