The new vSAN feature coming up soon is
REALLY exciting me! That is such a cool feature 8-)! Of course, I was
interested in testing it in my lab right away when I could get access to
it and faced a problem: vSAN requires the availability of a locally
attached SSD drive. Well, I guess most of us build virtual (nested) labs
and right now vSphere cannot be configured to present a virtual SSD to a
VM – damn! Fortunately, there is a way to fake one
I remembered that is was possible to mark a disk as SSD in case ESXi
didn’t recognize it. So I thought maybe we can use this to fake an SSD
for virtual ESXi hosts and guest what – yes we can!
Recipe:
Tadaaa! Like this we can test vSAN and other cool stuff already around: Swap to SSD and Host Caching in VMware Horizon View VDI environments! Awesome!
For simulating the vSAN feature in a nested environment just use the detailed guide from David Hill at virtual-blog.
Once you followed the mentioned steps, you will se a shared vSAN datastore and the corresponding Storage Provider entries.
Now you are able to create a VM Storage Policy out of the vendor specific vSAN capabilities.
Just attach the newly created profiles to your Virtual Machine hard disk and voila…. That’s it Have fun of testing this really cool new feature in your nested environment.
Register for the public beta right here
Now no beta on VMware vSphere 5.5 update 1
http://www.vxpertise.net/?s=vsan
Recipe:
- Get a shell on your ESXi host (ESXi Shell or SSH)
- Find the canonical name of the locally attached regular disk
- Create a claim rule that tags the drive as SSD.
- Reclaim the device.
- Verify.
Find the canonical name of the locally attached regular disk:
~ # esxcli storage core device list | grep -E "(^\s+Display Name)|(^\s+Size)|SSD" Display Name: QUADSTOR iSCSI Disk (naa.6ed5603489a66917daa052a5de9197ad) Size: 204800 Is SSD: false Display Name: Local VMware Disk (mpx.vmhba1:C0:T1:L0) Size: 8192 Is SSD: false Display Name: Local VMware Disk (mpx.vmhba1:C0:T0:L0) Size: 16384 Is SSD: false Display Name: Local NECVMWar CD-ROM (mpx.vmhba0:C0:T0:L0) Size: 300 Is SSD: false Display Name: QUADSTOR iSCSI Disk (naa.6edd1360f61f663586050a01b6571f84) Size: 204800 Is SSD: false |
Create a claim rule that tags the drive as SSD:
~ # esxcli storage nmp satp rule add --satp VMW_SATP_LOCAL --device mpx.vmhba1:C0:T1:L0 --option=enable_ssd
|
Reclaim the device:
~ # esxcli storage core claiming reclaim -d mpx.vmhba1:C0:T1:L0
|
Verify:
~ # esxcli storage core device list | grep -E "(^\s+Display Name)|(^\s+Size)|SSD" Display Name: QUADSTOR iSCSI Disk (naa.6ed5603489a66917daa052a5de9197ad) Size: 204800 Is SSD: false Display Name: Local VMware Disk (mpx.vmhba1:C0:T1:L0) Size: 8192 Is SSD: true Display Name: Local VMware Disk (mpx.vmhba1:C0:T0:L0) Size: 16384 Is SSD: false Display Name: Local NECVMWar CD-ROM (mpx.vmhba0:C0:T0:L0) Size: 300 Is SSD: false Display Name: QUADSTOR iSCSI Disk (naa.6edd1360f61f663586050a01b6571f84) Size: 204800 Is SSD: false |
esxcli storage core claiming reclaim -d
mpx.vmhba1:C0:T2:L0 – See more at:
http://www.virtuallyghetto.com/2011/07/how-to-trick-esxi-5-in-seeing-ssd.html#sthash.O0jydZb0.dpuf
Tadaaa! Like this we can test vSAN and other cool stuff already around: Swap to SSD and Host Caching in VMware Horizon View VDI environments! Awesome!
For simulating the vSAN feature in a nested environment just use the detailed guide from David Hill at virtual-blog.
Once you followed the mentioned steps, you will se a shared vSAN datastore and the corresponding Storage Provider entries.
Now you are able to create a VM Storage Policy out of the vendor specific vSAN capabilities.
Just attach the newly created profiles to your Virtual Machine hard disk and voila…. That’s it Have fun of testing this really cool new feature in your nested environment.
Register for the public beta right here
Now no beta on VMware vSphere 5.5 update 1
http://www.vxpertise.net/?s=vsan
ไม่มีความคิดเห็น:
แสดงความคิดเห็น