In this section we are going to deploy the downloaded NetScaler firmware onto our hypervisor (VMWare).
If you want to learn more about Citrix NetScaler check out our online NetScaler course at www.mastersof.cloud
We found a network bridging issue for a client running VMWare workstation 10. The VM would ‘sometimes’ connect to the production / corporate network and obtain a DHCP address. Othertimes it would not and it would get an APIPA address instead. (169.254.x.x)
Various internet posts suggested
- Disconnecting the Virtual nic – NO SUCCESS
- Upgrade the VM tools – NO SUCCESS
couldn’t even mount the ISO for some reason, so the .iso’s are located here(“C:\Program Files (x86)\VMware\VMware View\Client\Local Mode”) for future reference so you can extract and then manually run the installation.
- Remove and re add the NIC – NO SUCCESS
Turns out that when bridging mode is set to ‘automatic’ VMWare workstation will bind to any and all available network cards. (Bluetooth, wifi, other VMNics, Virtual box etc) So its a bit of pot luck when it connect to the production network and not the others.
- Open the Virtual Network editor
- Edit the appropriate ‘bridged’ network and select the appropriate NIC to bridge
- Be sure the configuration of the VM’s NIC is set to BRIDGED or is bound to the VMNetX that is configured for bridging.
Note: Besure to run the Virtual Network Editor as an administrator else you will not be able to change settings.
The OS was built and running fine on my SHuTTLE SH67 32GB, i7 CPU Vmware 5.1.0 box.
The moment i tried to copy a ISO (smaller files seemed to be ok) to or from the Windows 8.1 machine the entire ESXi box would PSOD.
Connecting from the *.1 to a XenServer machien to install the client tools also rendered the ESX PSOD.
Change the Windows 8.1 from using the E1000 network NIC driver to the VMXNet3. All problems gone! (for now!)
Error: There is no more space for the virtual disk XXX.vmdk. You might be able to continue this session by freeing disk space on the relevant volume.
Notes: I had no idea that was a snapshot on this home file server so was a surprise when i simply tried to move the vmdk file – to find all its associated -delta and snapshot files were missing! The changes I did here trashed all the changes to the vmdk since the snapshot – but as it was mostly for downloads i wasnt that upset… 🙂 I dont suggest folloing this unless you are sure 1) the snapshots are useless and 2) you are desperate to simply restore the flat VMDK without snapshots.
Steps i took that worked:
Noted the VM wasnt stated nor would it start.
Noted above error message
tried removing the secondary disk – couldn’t even edit settings
backedup just the -flat.vmdk and its disk descriptor to a separate / another lun that had lots of free space.
finally realised there was a snapshot file for the VM
ran the snapshot delete
server still wouldnt start
server required snapshot consolidation
tried to start and got ‘The Virtual Disk is either corrupted or not a supported format’
vm still wouldn’t start
remove all reference to the secondary ‘data’ disk (edit settings)
start the VM (os was on separate original vmdk)
try once more to add original ‘data’ vmdk- this failed
add back the newly moved vmdk and disk descriptor
drive attached ok.
https://(ipaddress of esx host)/mob/?moid=ha-host&doPath=capability
Assuming here that your ESXi environment is already nested and configured appropriately.
Power Off the guest ooerating system you want to enable FT for
Disconnect the CD / DVD (or select client devic eoption)
GO to options tab and sele the Advanced / General Button
ON right hand side click configuration parameters button
Add 3 ROWs
Name: replay.allowFT Value: true
Name: replay.supported Value: true
Name: replay.allowBTOnly Value: true
You ned VT-X as a feature of you rphysical CPU adn this needs to be passed through to your Nested ESXI host.
http://www.virtuallyghetto.com/2012/08/how-to-enable-nested-esxi-other.html < See this blog for more details.
It matters greatly if you are using ESXi 5.0 or 5.1
I recently purchased the following gear to setup a home lab for ESXi 5 study and to of course get my VCP5.
Its a Shuttle XPC with 32GB of DDR3 Ram, Intel i7 3.5ghz and a 3TB SATA3 HDD
I already had a HP microserver N40L with 8GB ram – but with more than 2-3 VM’s it would struggle and subsequently frustrate me greatly …. to say the least 🙂
I intended to run ESXi 5.1 virtualised so I could really test out the features and not be limited by hardware (like the shuttle only having 1 physical NIC)
The only things I needed to change on the physical shuttle host was
- add ‘vhv.allow = “true” > /etc/vmware/config
- Enable promiscuous mode on physical hosts ESXi vswitch
- Select Other x64 bit client for the VM Client
Check out this great blog http://tsmith.co/2011/creating-a-nested-esxi-5-environment/– for further info on nested ESXi setups
I also wanted a NFS and iSCSI device and after downloading OpenFiler from here https://www.openfiler.com/community/download
Configure it with as an RHEL x64 – 2GB Ram and 2 IDE Disks and 1vCPU
Then I found the following blogs to setup the OpenFiler shares
Problem: When pointing Xen Desktop 5.6 to a VMWARE management center you may receive the following error.
Error Message: Unable to contact the hypervisor. Check that the address, user name, and password are correct; the Controller and hypervisor are connected; and the SSL certificates have been set up correctly if you are using HTTPS. For more information see: CTX131512
Solution: Easy one really
- Ensure you are connecting to the Virtual Center server NOT the ESX or ESXi host itself.
- Install the certificate of the Virtual Center server into Trusted People Local Computer store (I just browsed to the site in IE and installed from there)
- Ensure you are using HTTPS in the Xen Desktop Wizard
- Ensure you place a /sdk after the Virtual Center servers https address ie.. https://vc.home.local/sdk
Problem: Upgrading 32 to 64 bit server on VMWARE ESX 4.x would result in a stop when booting the Windows 2008 x64 CD
Error Message: STOP: 0x0000005D (0x000000000FEBBBFF,0x0000000000000000, 0x0000000000000000,0x0000000000000000)
Resolution: Obvious one really, change the Architecture to be (64 BIT) for the VMWARE properties of the VM