If you recently upgraded to VMware 5.5 you will notice this warning if you try to edit your virtual machines.
“You cannot use the vSphere Client to edit the settings of virtual machines of version 10 or higher. Use the vSphere Web Client to edit the settings of this virtual machine.”
Unfortunately the vSphere Web Client is not free. So while you could download this you would be running in trial mode. The simplest fix for this issues is to follow the following steps.
Recently I installed Vmware Server. When I opened the web browser it popped up with an error service unavailable 503. To fix follow the steps below.
Now you need to right click on tomcat6.exe and go to properties. Click on the compatibility tab
Click on the button that says change settings for all users.
You will now see a new window with a single tab labeled compatibility for all users
Check the box that says “Run this program in compatibility mode for:”
That is it now you can start your Vmware service and open your browser.
There is a problem that exists where if you assign too much of the physical memory to a VM it will seem like every process you start bogs down the processor. Anything from word to SQL server. If you experience this problem try decreasing the ram to half of what you have and see if that makes a difference.
First thing you need to do obviously is make sure ESX can see both of your datastores.
Power off the virtual machine that you wish to copy.
SSH into the server using putty or like product.
go to /vmfs/volumes and go into the volume in which you want to move your data:
mkdir <Name of VM directory>
Now switch back to source datastore
cp *.* /vmfs/volumes/Datastore2/<Name of newly created VM directory>
Depending on the size of your datastore this obviously can take a very long time.
Now you have to register the new virtual machine
Go into virtual infrastructure, Click on the left the name of your ESX server, Go to the configuration tab.
From here go down to storage on the right hand column, double click the datastore in which you moved the VM.
Browse until you get to the folder that you moved. Find the vmx file right click on it and select add to inventory.
Congratulations you are finished.
Gain console access, I use putty.exe for this instance.
Login and then simply type the command passwd at the console. It will prompt you for the new password.
1. Download the Trixbox ISO. This will probably take ~1 hour.
2. Create a new virtual machine in ESXi with the following options
3. Follow this blog to mount the ISO as a virtual Cd-rom. http://www.n2networksolutions.com/blog/?p=366
4. Power on the virtual machine
The Trixbox CD was not found in any of your CDROM drives. Please insert the Trixbox CD and press OK to retry.
This did not work
Well I could not get this problem resolved so I’m just going to download the Trixbox Vmware appliance. It is 2.6.1 as opposed to 2.6.2 but you can always upgrade after the install. Here is the link.
1. Ok the first step here I’m going to use vCenter converter to import this virtual appliance into my ESXi server.
2. Converting is very simple once the program is installed click on the “Convert Machine” button which will bring up this window.
3. What you want to do is browse to the file we downloaded in the previous step after it is unzipped. trixbox 2.6.1-vmware.vmx
4. Once you click next it will ask you to supply your login to your ESXi server.
5. The next step allows you to rename your VM to whatever you want and select your data store.
6. The next step allows you to change your hardware settings for the virtual machine. I’m going to change two settings here:
Change to a 10gb disk
7. Once you click next you are ready to start your conversion. Now keep one thing in mind. This converter has to upload the large file we downloaded to the server. So if you are on a time crunch and are on wireless make sure you hardwire and disable your wireless. This will ensure you save the most time.
1. Ok now that we have the virtual machine install make sure it is powered on. It uses DHCP so you need to figure out what IP address it got. This can be accomplished by logging in to the Trixbox console with username root and password trixbox. Once you get the # type in ifconfig. This will display the IP.
2. This is going to be a server so we will want to configure a static IP or else it will be getting using DHCP which could cause all types of problems down the road.
now press esc and :wq to save changes and quit
now press and :wq to save changes and quit
The next step I recommend is opening your Trixbox server from a web browser:
Click on the packages link at the top so we can update our software to the latest version. When I clicked on mine i received the following error:
Error: The xml response that was returned from the server is invalid. Received:
To fix it I was able to type the following from the command line:
From here find the section below and change
max_execution_time = 300
memory_limit = 256
This may not work for you but it did resolve my problem.
Once you changed this type the following to restart the http daemon:
service httpd restart
Now I am able to successfully open:
From here I’m going to go down and check every box in the “upgrade” column this way all of my software installed on the server is up to date.
While trying to install a couple of the updates I’m receiving the following error:
Error: Missing Dependency: libtds.so.5 is needed by package asterisk
To fix it:
yum install libtds.so.5
Ok now that everything is downloaded and installed I’m going to configure some SIP trunks. I personally use Broadvoice for terminating my voice lines. However, there are tons of service providers out there. Here are my steps.
Open internet browser to http:///admin
First thing I’m going to do is edit the trunks
For trunk name you can put whatever you want
For peer details I’m using the following:
For user context I’m using the following sip.broadvoice.com
For user details I’m using:
Click submit changes.
If you are trying to mount ISO CD-rom images to ESXi so that you don’t have to physically burn the disc. Here is how.
1. Download a program called WinSCP. This allows you to use SSH to transfer files.
2. Open WinSCP to /vmfs/volumes/[name of your data store] then create a directory called ISOS.
3. Copy the downloaded ISO files from your PC to the ISOS folder.
4. Open Vmware infrastructure client right click on your server and go to edit settings.
5. You can either create another virtual CD rom drive or you can mount your ISO to your existing one.
6. Click on the CD/DVD Drive 1 in your options. On the right hand side select Datastore ISO file. Now simply browse to your ISO and you can mount it as if it were an inserted CD/DVD.
So I was finally able to get ESXi up and running. You can see from my previous posts I’ve tried hacking my system I have finally given up after investing probably 30 hours of trying.
What I finally did was purchase this SAS controller from Amazon:
SuperMicro Uio Card Lsi 1068E Sas Controller Card
I also purchased an Intel pro/100 network adapter from Fry’s electronics which appears to be compatible using the e100 driver
I do have an Intel Pro/1000 pci x1 adapter in the mail. Once it arrives I can hopefully increase my bandwidth to 1GB opposed to the 100MB I’m running currently.
I’m still debating whether or not I want to convert my home machine into a permanent ESXi server. It would mean I would have to pull one of my old PC’s out of the closet as a workstation….ugh.
While trying to convert an existing virtual machine with Vcenter Vmware Converter. I received an error that it had failed. So I browsed over to the log file to see what the cause was.
C:Documents and Settings%username%Local SettingsTempvmware-tempvmware-client-0.log
After editing the file at the end I see the following:
[2009-02-20 17:38:49.843 ‘P2V’ 1752 error] [task,295] Task failed: P2VError UNKNOWN_METHOD_FAULT(sysimage.fault.InvalidTargetProductVersion)
I realized it’s been awhile since I’ve tried to use this utility so I’m going to download the latest version to circumvent this issue.
Go to the ESXi console and press alt+F1
Enter the root password
At the prompt type “vi /etc/inetd.conf”
Look for the line that starts with “#ssh” (you can search with pressing “/”)
Remove the “#” (press the “x” if the cursor is on the character)
Save “/etc/inetd.conf” by typing “:wq!”
Restart the management service “/sbin/services.sh restart”