Answere:
Using static address:
1) Ping any IP address in your network. If it succeeds, then it is confirmed that you don't have any problems with your local network using static address.
2) Ping any IP address outside your network. If this succeeds, then it is confirmed that traffic is getting out of your network using static address.
3) Ping any domain name outside your network. If this succeeds, then it is confirmed that your DNS is resolving names.
This assumes you have given your box a correct IP address, network mask, gateway and DNS.
Operating System
This blog is created for learning how to manage OS.
Tuesday, March 3, 2015
Sunday, December 28, 2014
Fix for VMware Workstation “Not enough physical memory is available” Error
VMware Workstation is, in my eyes, the best personal virtualization
product around. Although other products exist, such as the free client Hyper-V on Windows 8/8.1 and Oracle Virtual Box,
VMware Workstation has so many features that makes it much more usable
compared to other offerings. I’ve used it for many years, and now VMware
Workstation is on version 10. On my laptop I have several virtual
machines (VMs) that I constantly use for various purposes, mostly
running Windows Server 2012 R2 and Windows 7/8.1, but I also have some
CentOS and RedHat VMs.
Not enough physical memory is available to power on this virtual machine with its configured settings.
To fix this problem, power off other virtual machines, decrease the memory size of this virtual machine to 220 MB, increase the amount of physical memory for all virtual machines to 2256 MB, or adjust the additional memory settings to allow more virtual machine memory to be swapped.
It is possible that native applications and/or services have locked down memory which could be preventing the virtual machine from launching. Shutting down unnecessary applications or services may free enough memory to launch this virtual machine.
If you were able to power on this virtual machine on this host computer in the past, try rebooting the host computer. Rebooting may allow you to use slightly more host memory to run virtual machines.
And here’s a screenshot of the error I received:
The actual number of megabytes that the prompt tells you to configure may change, and sometimes it even changes between reboots of the host machine.
What? That cannot be right. My laptop has 16 GB of RAM and there were no apps that took more than 4 GB overall, which left more than 12 GB free. The VM I tried to boot was a Windows Server 2012 R2 machine with 4 GB of RAM.
I tried again, same error. I tried a different VM, same error. All my VMs couldn’t boot.
Since the same VMs worked just fine since my last reboot of the host laptop, I rebooted it, hoping it will make the error go away. It didn’t.
I looked around on the Internet. Reading some forum posts that I found, this error appears for a random reason and has been around in older versions of VMware Workstation, where it’s been found to go back to VMware Workstation 6.
2. If you have an icon for VMware Workstation on your desktop, right-click it and read on. If you don’t have an icon on the desktop, find it in Start and right-click it.
3. Select “Open file location.”
4. Right-click the VMware Workstation icon and select Properties. Go to the Compatibility tab and select “Run this program as administrator.”
5. Click OK.
6. Try to run VMware Workstation and boot your VM. If it works, fine. If not, read on.
2. October 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2.
2. Add the following line to the end of the file:
3. Save the file. You may need to edit it as an administrator in case you get an error during the save.
4. Reboot your host computer.
5. Try to run VMware Workstation and boot your VM.
2. Add the following lines to the end of the file:
3. Use “100” to run a few VMs with best performance, or use lower
values such as “25” if you want to run many VMs at the same time.
Note: These settings can also be done through the VMware Workstation UI under > Edit > Preferences.
Some more tuning options:
Sponsored
A couple of days ago I rebooted my laptop due to a Microsoft Windows
Update, and when it started I launched VMware Workstation. I powered on
one of my VMs, as I usually do. But this time I was presented with the
following error:Not enough physical memory is available to power on this virtual machine with its configured settings.
To fix this problem, power off other virtual machines, decrease the memory size of this virtual machine to 220 MB, increase the amount of physical memory for all virtual machines to 2256 MB, or adjust the additional memory settings to allow more virtual machine memory to be swapped.
It is possible that native applications and/or services have locked down memory which could be preventing the virtual machine from launching. Shutting down unnecessary applications or services may free enough memory to launch this virtual machine.
If you were able to power on this virtual machine on this host computer in the past, try rebooting the host computer. Rebooting may allow you to use slightly more host memory to run virtual machines.
And here’s a screenshot of the error I received:
The actual number of megabytes that the prompt tells you to configure may change, and sometimes it even changes between reboots of the host machine.
What? That cannot be right. My laptop has 16 GB of RAM and there were no apps that took more than 4 GB overall, which left more than 12 GB free. The VM I tried to boot was a Windows Server 2012 R2 machine with 4 GB of RAM.
I tried again, same error. I tried a different VM, same error. All my VMs couldn’t boot.
Since the same VMs worked just fine since my last reboot of the host laptop, I rebooted it, hoping it will make the error go away. It didn’t.
I looked around on the Internet. Reading some forum posts that I found, this error appears for a random reason and has been around in older versions of VMware Workstation, where it’s been found to go back to VMware Workstation 6.
Sponsored
4 Fixes for “Not enough physical memory” Errors
There were four approaches that I found to solve this error. For me, the third one worked, but I’ll list all of them just in case.Fix #1 – Run as Administrator
1. Make sure VMware Workstation is not running.2. If you have an icon for VMware Workstation on your desktop, right-click it and read on. If you don’t have an icon on the desktop, find it in Start and right-click it.
3. Select “Open file location.”
4. Right-click the VMware Workstation icon and select Properties. Go to the Compatibility tab and select “Run this program as administrator.”
5. Click OK.
6. Try to run VMware Workstation and boot your VM. If it works, fine. If not, read on.
Fix #2 – Uninstall Windows Update Fix KB2995388
1. If you have the Windows Update fix KB2995388 installed on your machine, then you may want to remove it. It should solve the VMware error, but it will prevent you from getting the other fixes in this rollup update, so I wouldn’t rush to go down this path.2. October 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2.
Fix #3 – Modify the config.ini file (Host Parameters)
1. Open the config.ini file located by default at C:\ProgramData\VMware\VMware Workstation.2. Add the following line to the end of the file:
1
|
vmmon.disableHostParameters = “TRUE”
|
4. Reboot your host computer.
5. Try to run VMware Workstation and boot your VM.
Sponsored
Fix # 4 – Modify the config.ini file (VmMemPct)
1. Open the config.ini file located by default at C:\ProgramData\VMware\VMware Workstation.2. Add the following lines to the end of the file:
1
|
prefvmx.minVmMemPct = "25"
|
Note: These settings can also be done through the VMware Workstation UI under > Edit > Preferences.
1
2
3
|
Fit all = 100
Allow some = 50
Allow most = 25
|
Some more tuning options:
- The VMware Continuum tuning guide provides instructions to set up the host for expected usage.
- Save the file. Note that you may need to edit it as administrator in case you get an error while saving.
- Reboot your host computer.
- Try to run VMware Workstation and boot your VM.
Thursday, June 12, 2014
How to Reset Your Forgotten Windows Password the Easy Way
Forgetting your password is never any fun, but luckily there’s a really easy way to reset the password. All you need is a copy of the Windows installation disk and one simple command line trick.
Resetting Your Forgotten Windows Password
Boot off the Windows disk and select the “Repair your computer” option from the lower left-hand corner.Follow through until you get to the option to open the Command Prompt, which you’ll want to select.
First you’ll want to type in the following command to backup the original sticky keys file:
copy c:\windows\system32\sethc.exe c:\Then you’ll copy the command prompt executable (cmd.exe) over top of the sticky keys executable:
copy c:\windows\system32\cmd.exe c:\windows\system32\sethc.exe
Now you can reboot the PC.
Resetting the Password
Once you get to the login screen, hit the Shift key 5 times, and you’ll see an administrator mode command prompt.Now to reset the password—just type the following command, replacing the username and password with the combination you want:
net user geek MyNewPassword
That’s all there is to it. Now you can login.
Of course, you’ll probably want to put the original sethc.exe file back, which you can do by rebooting into the installation CD, opening the command prompt, and copying the c:\sethc.exe file back to c:\windows\system32\sethc.exe.
Subscribe to:
Posts (Atom)