Dark Developments Where Knowledge Meets Power

26Oct/120

ASTERISK – Move VM issues.

Posted by Dark#Basics

ASTERISK - Move VM issues.

When moving a VM with Asterisk, or another platform dependant package, from for example a VMware Player to VMWare ESXi you might have some issues running the package. In my case after preforming a move from VMware Player to VMWare ESXi using VConverter the ASTERISK package wouldn't start. I received the error message 'Illegal Instruction'. After some Google-ing, trying to convert again using a different VM-version I had an idea of reinstalling the Asterisk package and it worked! Probably when running apt again it installed some additional packages for the new/current chipset. Make sure that you don't overwrite your Asterisk configuration!

15Aug/121

VMware- ESX Image Builder CLI

Posted by Dark#Basics

VMware- ESX Image Builder CLI

When installing ESX(i) on different vendor platforms you'll get confronted with warnings related to drivers. In my case it was a Dell R720 and during the installation of ESX I got the message "no network adapters found".
The only option is to build your own custum ESX image and inserting the correct NIC drivers.

1. Download the latest ESXi build from the patch page from VMware. my.vmware.com/web/vmware/info/slug/datacenter_cloud_infrastructure/vmware_vsphere/5_0#product_downloads

2. Next download the approriate driver software from the driver depot. my.vmware.com/web/vmware/info/slug/datacenter_cloud_infrastructure/vmware_vsphere/5_0#drivers_tools
Note: In my case I needed the net-tg3 drivers.

3. Extract all the files so that you can access them with vCLI. You can download vSphere CLI from my.vmware.com/web/vmware/details/vcli41/ZHcqYmRoaCpiZHRAag== .

4. Next, start your PowerCLI session and import the software depots using the “Add-EsxSoftwareDepot” cmdlet.  Import all the software depots you have downloaded.

Select All Code:
1
2
Add-EsxSoftwareDepot C:\vmware\ESXi-5.0.0-20120604001-standard.zip
Add-EsxSoftwareDepot -DepotURL "C:\vmware\net-tg3.zip"

5. After the software depots have been imported the next step is to create an image profile using the “New-EsxImageProfile” cmdlet. There are two ways to create a new image profile, you can create an empty image profile and manually specify the VIBs you want to add, or you can clone an existing image profile and use that as your starting point.

Select All Code:
1
New-EsxImageProfile -CloneProfile "ESXi-5.0.0-20120604001-standard" -Name "CustomISO" -AcceptanceLevel CommunitySupported

6. Next, you use the “Add-EsxSoftwarePackage” to add VIBs to your image profile.

Select All Code:
1
Add-ESXSoftwarePackage -ImageProfile CustomISO -SoftwarePackage net-tg3

7. After adding the VIBs you need the next step is to export the image profile. You can export the Image Profile as a software depot (.zip) or as an ISO file (.iso).

Select All Code:
1
2
3
Export-EsxImageProfile -ImageProfile CustomISO -ExportToIso -FilePath C:\vmware\CustomProfile.iso
 
Export-EsxImageProfile -ImageProfile CustomISO –ExportToBundle -FilePath C:\vmware\CustomProfile.zip

blogs.vmware.com/vsphere/2012/04/using-the-vsphere-esxi-image-builder-cli.html

communities.vmware.com/message/2069580

9Jan/120

VMware – Move VM to different datastore on ESXi

Posted by Dark#Basics

VMware - Move VM to different datastore on ESXi
It's pretty striaght forward how to move a VM to a different datastore within a standalone ESXi host.

Login by using the vSphere client on the ESXi host and shutdown the VM that you want to move to a different datastore. After the VM is powered off remove it from the inventory by right clicking on the VM and selecting ‘Remove from inventory’.

After that the VM is removed from the Inventory browse the current datastore (source) and the new datastore (destination) and just copy/past or cut/paste the VM's from source to destination.

After that the copying is complete go to the new datastore, right click the VM and select 'Add to Inventory'. Follow the steps in the wizard and the VM will be visible in the inventory. If needed change the VM settings.

When you power on the VM it will notice that he is on a different datastore. Answer the question by selecting ‘I _copied it’ and click ‘OK’.

11Oct/110

VMware – ESX(i) Jumbo Frames on Storage Adapters

Posted by Dark#Basics

VMware - ESX(i) Jumbo Frames on Storage Adapters
Jumbo frames are units that contain 9,000 bytes of data instead of the usual 1500, or an MTU of 9000 instead of 1500.  When using the ESX software iSCSI initiator, a network adapter becomes the transport device for your iSCSI traffic.  When creating a virtual switch using the vSphere client, you cannot change the default MTU value of 1500, nor can you even view the values

If the software Storage Adapters are already created the MTU can still be modified using the CLI of your host.
First check the current vSwitches so that you can confirm the changes and settings.

Select All Code:
1
esxcfg-vswitch -l

Run vmknic to change the MTU of all the vSwitches.

Select All Code:
1
esxcfg-vmknic -m 9000 "VMkernel iSCSI 2"
19Sep/110

VMware – vCenter Converter

Posted by Dark#Basics

VMware - vCenter Converter
Taking physical machines and making them virtual can be a long and complex process.  With vCenter Converter it is possible to automate and simplify physical to virtual (P2V) as well as converting virtual machine formats for example VMDX-files from exported VM's in VMWare Workstation. It is possible to convert Microsoft Windows and Linux-based physical machines and third-party formats to VMWare virtual machines.

When running vCenter Converter the first option you will need to chose is a source type. There are five available options in the current version:

  • Powered-on machine - Convert any powered-on physical or virtual machine (local or remote).
  • VMware Infrastructure virtual machine - Convert a virtual machine from VMware VirtualCenter or VMware ESX Server.
  • VMware Workstation or other VMware virtual machine - Convert a virtual machine from VMware Workstation, VMware Player, VMware Fusion or other VMware product.
  • Backup image or third-party virtual machine - Convert a backup image or a third-party virtual machine. For example Microsoft Virtual PC, Parallels,  VMware Consolidated Backup, Symantec LiveState Recovery Image, StorageCraft ShadowStor Image, Acronix True Image Backup.
  • Hyper-V Server - Convert a virtual machine from Microsoft Hyper-V Server.

After selecting the desired option and selecting/adding the necessary information you will be able to configure the VM's settings. For example CPU, memory, hard disk,... Based on previous selection you will be able to create (a) virtual machine(s) to a vSphere host, VMware Workstation, VMware GSX Server, VMware Player, VMware Server or VMware Fusion.

You can get a free copy of vCenter Converter here at www.vmware.com/products/converter/