Tag Archives: BIOS

VMware – Setting up ESX NTP Time Sync

Posted on by

ESX NTP KB ID 0000798

Problem

Having your ESX Server running the correct time is quite important, and before you visit this subject, I would suggest you MAKE SURE the time is set in the ESX Servers BIOS, ie the internal clock is set correctly first. I’ve lost count of the amount of times I’ve seen Windows domains fall over because the ESX host has reverted to its BIOS time and replicated that time to its guests, suddenly your domain clocks are two years apart and carnage ensues!

Throughout this procedure I will be setting my VMware environment to sync time with a LOCAL windows domain controller, some may argue if the domain controller is a virtual machine in a virtual environment that this is a BAD IDEA. I understand that argument (but this is my test network). In production I would rather have my devices getting time synchronised from a public reliable public time source.

Solution : ESX NTP

Step 1: vCenter NTP

Assuming you have already set time correctly on you domain controller as per this article. Then the next step is to configure you vCenter server(s) NTP time source. note: If you are using stand-alone ESX Servers please skip this section.

Note: For this to work the hosts need to be able to communicate with the time servers over NTP (UDP Port 123), ensure your firewall has this port open to the NTP source or time sync will fail.

Connect you your vCenter(s) direct admin console https://{ip-or-domain-name}:5400 log in as root. Navigate to Time > Select the correct Time Zone (Note: there is GMT but no BST So if you’re in the UK select Europe/London). Under Time Synchronization > Edit > Mode = NTP > Time Servers = the IP(s) of you time sources > Save.

Have a coffee, eventually it should look like this.

Step 2: ESX NTP (Directly)

Note: If you are managing ESX hosts via vCenter skip to the next section, this procedure is used to set NTP on an ESX host directly. Connect to the management console of your ESX Server. Navigate to Manage > System > Time & Date > Edit NTP Settings.

Select “Start and Stop with Host” > Enter the IP addresses or names of the NTP Source(s) > Save.

 

Step 2: ESX NTP (via vCenter)

Connect to vCenter and select your first ESX host  > Configure > Time configuration > Add Service > Network Time Protocol > Enter the IP addresses(s) or name(s) of you NTP Server(s) > OK.

At this point go and have a coffee > Hit Refresh > ONCE there’s an entry under Last Time Sync > Test Services.

The output should look something like this

 

ESX NTP For OLDER versions of vSphere

Connect to the host (or vCenter and drill down to the host(s)). Select the host in question > Configuration > Time Configuration > Properties > Tick NTP Client Enabled > Options > Add > Add in your public time server IPs > Tick ‘Restart NTP Service to apply changes’ > OK > OK.

Note: I’m in the UK so I’m using two time servers in this country, you may want to use one closer to home.

130.88.212.143 = turnip.mc.man.ac.uk (Manchester University)
130.88.200.4 = dir.mcc.ac.uk (Manchester University)

2. When you see the following all is well.

Note: If all these details are IN RED, then it has failed to sync, either be patient, try putting the host into and out of maintenance mode, or reboot it, if it continues to fail check it can see the public time servers on UDP port 123.

Related Articles, References, Credits, or External Links

NA

VMware Error – HARDWARE _VITRTUALIZATION WARNING

Posted on by

KB ID 0000570 

Problem

Seen while installing vSphere ESX 5 (In this case, on a Dell Power Edge).

Warning(s)
<HARDWARE_VIRTUALIZATION WARNING: Hardware Virtualization is not a feature of the CPU, or it is not enabled in the BIOS>

Solution

Unless you have a “quite old” server, you simply need to enable “virtualization Technology” in the machines BIOS.

1. On this machine (Dell PowerEdge T410) enter the BIOS > Navigate to Processor Settings > Virtualization Technology > Set to Enabled.

Note: You can check Intel Processors for Virtualization Technology Support here, and for AMD Processors go here.

 

Related Articles, References, Credits, or External Links

NA

VMware Workstation – Error – ” Virtualized Intel VT-x/EPT is disabled”

Posted on by

KB ID 0000540 

Problem

Seen on VMware Workstation, when attempting to virtualise a product that IS a virtualisation hypervisor (ESX for example).

Error: Virtualized Intel VT-x/EPT is disabled for this ESX VM. You will only be able to run 32-bit nested VMs.

At first I (wrongly) assumed that I needed to enable something in the BIOS on my laptop, and searched though every page to enable some virtualization setting that was turned off. But that’s NOT what it’s telling you. what it is telling you is you are trying to virtualize a virtualization product, so all the clever VT settings from your physical machines CPU will be shown to VMware workstation. But that presents a Virtual CPU to the OS you are installing as a guest (In the case above ESX) and THAT virtual CPU does NOT have Intel- VT-x/EPT enabled.

So a “Nested VM” – is a Guest VM, running Inside a Guest Hypervisor, that’s been virtualized.

Solution

Note: I’m using VMware workstation 8.

1. Right click the VM in question and select “Settings”.

2. Hardware Tab > Processors > Tick the option to enable VT-x/EPT or V/RVI > OK.

3. Restart the guest machine.

Note: You can also do this be editing the machines .vmx file with a text editor and adding the following lines;

[box]

monitor.virtual_mmu = "hardware"

monitor.virtual_exec = "hardware"

vhv.enable = "TRUE"

monitor_control.restrict_backdoor = "true"

[/box]

Related Articles, References, Credits, or External Links

NA

vSphere – Floppy Drive ‘Won’t Appear’

Posted on by

KB ID 0001020

Problem

“It’s 2015 why are you messing around with floppy drives?” I hear you ask! Well for importing certificate requests, and issued certificates from an offline root CA server, it’s still considered best practice to use a virtual floppy drive rather than connect the offline root server to the production network.

So today while deploying a PKI infrastructure, I needed to present a floppy drive to a Windows Server 2012 R2 Issuing (subordinate CA). Despite me adding the hardware, presenting a floppy image and ticking ‘connected’ the floppy drive refused to ‘appear’ in Windows.

Solution

The problem was the client had a ‘Pre-hardened’ Server 2012 R2 template, that I had used to deploy the server, and in the BIOS of the template the floppy drive was disabled.

1. Set the VM to boot into BIOS next time it starts (you can reboot and keep pressing F2).

2. Main > Legacy Diskette A: > Set to [1.44/1.25 MB 3 1/2].

3. At this point I hit F10 (Save and Exit), booted up the VM, and it was still missing!

4. Turns out (after some more BIOS digging) that the controller was also disabled! Advanced > I/O Device Configuration.

5. Set Floppy disk controller to ‘Enabled’ > F10 > Boot the VM. Problem solved!

Related Articles, References, Credits, or External Links

NA

Windows Server 2012 – Install Error

Posted on by

KB ID 0000618 

Problem

I thought I’d spin up Server 2012 today, and as usual with all new OS’s I run them up in VMware Workstation to take a look (I’m running Workstation 8.0.3 build-703057).

As soon as it started up I was greeted by this.

Your PC needs to restart.
Please hold down the power button.
Error Code: 0x0000005D
Parameters:
0x000000000FEBFBFF
0×0000000020000800
0×0000000000000000
0×0000000000000000

Below is information for VMware Workstation and ESXi 5

Solution

For VMware Workstation

1. In my case it was simply a BIOS setting that needed to be enabled. Enter your system BIOS and locate a feature called Data Execution Prevention, (or No Execute Memory Protection).

2. Enable that setting, then ensure you shut the machine down then manually power it back on again.

Additional Points to Note when installing Server 2012

Make sure on the properties of the VM > Hardware > Processors > Tick Virtualize Intel VT-x/EPT or V/RVI (Note: Virtual support should also be enabled in the host machines BIOS).

VMware Workstation – Error – “Virtualized Intel VT-x/EPT is disabled”

VMware Workstation likes to automatically install VMware Tools, Sometimes Server 2012 does not like this and sits with a black screen that will flash blue when you click on it. So to Stop it Installing VMware Tools, Options Tab > VMware Tools > Select Manual. Note: you can always snapshot it and then manually install it later it you want to test. This has been a problem since the early releases of Windows 8.

Solution For ESXi5

1. Here’s the same problem on an ESXi 5 host.

2. Before you do anything you need to be at ESXi 5.0 U1 for Server 2012 to be supported (That’s build number 623860 or better).

3. However in this case the problem is the same as above, The server in question was an HP Proliant ML 350 G5. Boot the server and press F9 to enter the RBSU > Advanced Options.

4. Processor Options

5. Enable ‘No-Execute Memory Protection” > Exit and save settings.

6. And now we are good to go.

Follow up

04/07/12 Email from Simon Reindl:

I had to update my Bios as InsydeH2O does not offer any tweaking options, It is using Compal Bios (previous 9, now 10 – downloaded from Compal.com. It is using InsydeH20 BIOS on a Compal motherboard. It is a custom build.

 

Related Articles, References, Credits, or External Links

NA