- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- StoreVirtual Storage
- >
- Re: 2012 R2 guests on ESXi 6.5 fail to boot when u...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2017 07:39 AM
02-15-2017 07:39 AM
2012 R2 guests on ESXi 6.5 fail to boot when using EFI
I'm setting up a new vSphere 6.5 cluster and starting to provision my first machines. My backing storage is a StoreVirtual 3200 unit. I've set up a template for future guests, which uses EFI instead of BIOS. Upon rebooting the guests, they fail to start properly.
The issue is identical to this one I found on the KB: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2146167
I have followed the steps and set my configuration accordingly. Here is the output from esxcli storage core path list:
iqn.1998-01.com.vmware:esx-mk1-58d288d3-00023d000003,iqn.2015-11.com.hpe:storevirtual.rpl,t,3-naa.6000eb3b01323a960000000000001bf0
UID: iqn.1998-01.com.vmware:esx-mk1-58d288d3-00023d000003,iqn.2015-11.com.hpe:storevirtual.rpl,t,3-naa.6000eb3b01323a960000000000001bf0
Runtime Name: vmhba64:C0:T0:L10
Device: naa.6000eb3b01323a960000000000001bf0
Device Display Name: LEFTHAND iSCSI Disk (naa.6000eb3b01323a960000000000001bf0)
Adapter: vmhba64
Channel: 0
Target: 0
LUN: 10
Plugin: NMP
State: active
Transport: iscsi
Adapter Identifier: iqn.1998-01.com.vmware:esx-mk1-58d288d3
Target Identifier: 00023d000003,iqn.2015-11.com.hpe:storevirtual.rpl,t,3
Adapter Transport Details: iqn.1998-01.com.vmware:esx-mk1-58d288d3
Target Transport Details: IQN=iqn.2015-11.com.hpe:storevirtual.rpl Alias= Session=00023d000003 PortalTag=3
Maximum IO Size: 131072
iqn.1998-01.com.vmware:esx-mk1-58d288d3-00023d000004,iqn.2015-11.com.hpe:storevirtual.rpl,t,3-naa.6000eb3b01323a960000000000001bf0
UID: iqn.1998-01.com.vmware:esx-mk1-58d288d3-00023d000004,iqn.2015-11.com.hpe:storevirtual.rpl,t,3-naa.6000eb3b01323a960000000000001bf0
Runtime Name: vmhba64:C1:T0:L10
Device: naa.6000eb3b01323a960000000000001bf0
Device Display Name: LEFTHAND iSCSI Disk (naa.6000eb3b01323a960000000000001bf0)
Adapter: vmhba64
Channel: 1
Target: 0
LUN: 10
Plugin: NMP
State: active
Transport: iscsi
Adapter Identifier: iqn.1998-01.com.vmware:esx-mk1-58d288d3
Target Identifier: 00023d000004,iqn.2015-11.com.hpe:storevirtual.rpl,t,3
Adapter Transport Details: iqn.1998-01.com.vmware:esx-mk1-58d288d3
Target Transport Details: IQN=iqn.2015-11.com.hpe:storevirtual.rpl Alias= Session=00023d000004 PortalTag=3
Maximum IO Size: 131072
As per the article, I have taken the maximum IO size of 131072 (bytes) and set the 'Disk.DiskMaxIOSize' setting on each of my hosts to 128 (kilobytes). Output of esxcli system settings advanced list -o "/Disk/DiskMaxIOSize" | grep Int\ Value | grep -v Default'
Int Value: 128
Here's a snippet of vmware.log for a guest that fails to start:
2017-02-14T15:15:16.849Z| vcpu-0| I125: Guest: About to do EFI boot: Windows Boot Manager
2017-02-14T15:15:16.886Z| vcpu-0| I125: HBACommon: First write on scsi0:0.fileName='/vmfs/volumes/58986c57-beebfb62-20dc-941882e61b50/dc-mk1/dc-mk1.vmdk'
2017-02-14T15:15:16.886Z| vcpu-0| I125: DDB: "longContentID" = "9183ad927c82a0f735b6ad050dce9686" (was "b8e64cc6686f60edd799a37495b96386")
2017-02-14T15:15:16.939Z| vcpu-0| I125: DISKLIB-CHAIN : DiskChainUpdateContentID: old=0x95b96386, new=0xdce9686 (9183ad927c82a0f735b6ad050dce9686)
2017-02-14T15:15:20.002Z| vmx| I130: Vigor_ClientRequestCb: dispatching Vigor command 'Ethernet.queryFields'
2017-02-14T15:15:38.459Z| vcpu-0| I125: Tools: Tools heartbeat timeout.
There is a consistent 22 seconds between "about to do EFI boot" and "tools heartbeat timeout" when the guest fails to start.
I'm keen to resolve this ASAP so I can commission my new hardware in earnest - any ideas?
- Tags:
- 3200
- ESXi
- StoreVirtual
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2017 09:17 AM
02-21-2017 09:17 AM
Re: 2012 R2 guests on ESXi 6.5 fail to boot when using EFI
Hi referencepoint,
That's interesting. The SV3200 should support IO sizes much larger than 128KB. If you change the DiskMaxIOSize to 127, does it work? How about 64? Does it work if you boot in BIOS mode?
If you think this is a SV3200 issue rather than a VMware or Microsoft issue, go ahead and open a support case.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2017 04:16 AM
03-15-2017 04:16 AM
Re: 2012 R2 guests on ESXi 6.5 fail to boot when using EFI
Hi stor_mort
I didn't notice your reply - I'm now subscribed!
The guests work perfectly if they boot in BIOS mode - I haven't tried booting the hosts in BIOS mode as that would require re-imaging them.
I think the 128KB limit is possibly related to the fact it's running over iSCSI - lots of the iSCSI initiator config makes reference to 131072 byte (128KB) block sizes. I currently have a support case open with VMware, they suggested a few different Max IO Size options but none of those made a difference.
If you think HPE would be happy to assist with this issue then I'll make a ticket!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-01-2017 07:46 PM
08-01-2017 07:46 PM
Re: 2012 R2 guests on ESXi 6.5 fail to boot when using EFI
Hi!!
The SV3200 support the vSphere 6.5 ? In the Spock only the 6.0 U2 are listed like a supported operating system.
Please assign Kudos
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-02-2017 10:57 AM
08-02-2017 10:57 AM
Re: 2012 R2 guests on ESXi 6.5 fail to boot when using EFI
We plan to support ESX 6.5 hosts in the Nov/Dec timeframe later this year. SPOCK is correctly showing what we support on SV3200.
Amy Mitchell
StoreVirtual Product Manager