Network card configuration missing after P2V using VMware Converter

Last night I converted a physical Windows 2003 R2 server to a VMware virtual machine using VMware Converter Standalone version 4.0.1.  The entire process was extremely simple, only four steps.  After the P2V conversion completed, the physical machine powered off, and the newly created VM booted up.  Everything appeared to be normal, until I realized I couldn’t RDP into the new VM.

I jumped on the server console via the Virtual Infrastructure client, and found that my VM was receiving an IP address from DHCP, rather than the static address the physical server was configured with.  I attempted to assign the static IP to the NIC, and received a message that an existing NIC already was using that IP address.   No other NICs were visible in the Network Connections applet.

I immediately thought back to my post from earlier this summer titled Fix: The IP address you have entered for this network adapter is already assigned to another adapter that is hidden from the Network Connections folder because it is not physically in the computer”  This post details how to start Device Manager in a mode that shows hidden devices.  I was able to follow the steps to remove the phantom NIC, then was able to assign the static IP address to the VM’s NIC, which allowed me to RDP into the server once again. 

The steps are:

  1. Click Start, click Run, type cmd.exe, and then press ENTER.
  2. Type set devmgr_show_nonpresent_devices=1, and then press ENTER.
  3. Type Start DEVMGMT.MSC, and then press ENTER.
  4. Click View, and then click Show Hidden Devices.
  5. Expand the Network adapters tree.
  6. Right-click the dimmed network adapter, and then click Uninstall.
Finally I configured the static IP on the NIC, and all was well.

Howto: Reset a lost VMware guest password

So you’ve forgotten your VMware Linux or Windows guest password?  Here’s how to reset it.  These instructions focus on resetting the password through the Virtual Infrastructure Client, but there’s no reason you couldn’t do it using VMware Workstation or VMware Server.  

1. Grab a Kon-Boot .iso image.
 
2. In the Virtual Infrastructure client, configure the problematic guest’s Virtual CDROM for the Kon-boot ISO image.
 
3. Boot the problem guest server.  At the VMware BIOS screen, press the ESC key to bring up the boot menu.  Select to boot from CD-ROM.
 
4. When the Kon-Boot splash screen appears, press Enter to boot Windows.
 
5. At the Windows login screen, enter administrator as the user name, with any password you’d like.  Note:  This password is not persistent!  You must set the administrator password manually! Once the password is set, reboot the server and you will be able to login with the newly set credentials.
 
If you are trying to reset the password in Linux, the steps are the same, but instead of logging into Windows and resetting the adminstrator password, login to Linux and reset the root password.

Fix for VMWare error: Could not open virtual machine, this virtual machine appears to be in use

This morning I received the following error when trying to power on a VMware Workstation virtual machine:

Could not open virtual machine: C:\VMs\Windows Server 2003 Standard Edition.vmx. This virtual machine appears to be in use.

To resolve the issue, I deleted all of the .lck files and directories in the guest’s directory listed above. This allowed me to start my VM. I encounter this error from time to time, yet always forget how to resolve it.

Ubuntu 8.10 Alpha 4 now available as VMware Virtual Appliance

Ubuntu 8.10 Alpha 4 is now available as a VMware Virtual Appliance free download.

The fourth alpha release of Ubuntu 8.10 “Intrepid Ibex” is ready for testing.

New features:

  • X.Org server 1.5 brings much better support for hot-plugable input devices such as tablets, keyboards, or mice
  • Linux kernel 2.6.26
  • encrypted private directory
  • guest session – the GNOME user switching applet now provides an extra entry for starting a guest session, this creates a temporary password-less user account with restricted privileges
  • Network Manager 0.7 which comes with long-expected features, such as managing system-wide settings, 3G connections (GSM/CDMA.), multiple active devices, PPP and PPPoE connections, devices with static IP configurations, routes for devices.

Last updated: 08/25/2008

VMware Express Patch for ESX and ESXi 3.5 now available

Yesterday I wrote that VMware was promising a patch by noon PDT today to address their licensing issue that caused version 3.5 Update 2 ESX and ESXi machines not to power on, suspended machines not to leave suspended mode, and machines not be able to be migrated via Vmotion. 

Well, VMware has released patches for both systems ahead of schedule.  You can read about the patches here, or go directly to download the ESX or ESXi version of the patch.

You can read a huge thread on the VMware Communities forum about the experiences network administrators have had with this bug.  It’s currently 42 pages long, and lets just say many administrators who have tauted VMware’s software as the answer to high availability challenges have egg on their face today.  The thread is so lengthy the moderator has created new separate threads for technical and non-technical feedback.

You can also read a post from VMware CEO Paul Maritz  about this issue.

A VERY bad day for VMware

[update 2008-08-13]

The patch is out, read all about it here.

****************************************

Vmware Knowledge Base ID 1006716 sums up the situation quite succinctly:

Unable to Power On virtual machine with “A General System error occurred: Internal error”

A virtual machine fails to power on, fails to leave suspend mode, or fails to migrate with VMotion and the following message is displayed in the vmware.log file for the virtual machine:

This product has expired. Be sure that your host machine’s date and time are set correctly.

Currently running virtual machines will continue to run but will not be able to perform migration with VMotion, suspend or power on virtual machines.

The cause of the problem? An issue with ESX/ESXi 3.5 Update 2 causes the product license to expire on August 12, 2008!

DOH!

The good news is VMware promises patches will be available for download by noon PST on August 13.

Free VMware ESXi licenses

VMware is now offering free licenses of it’s popular ESXi hypervisor.  Your license includes VMware ESXi, VMware Virtual SMP, and VMware VMFS.

VMware ESXi is a full fledged bare-metal hypervisor that fits into a 32MB footprint.  VMware ESXi is essentially VMware ESX without the server console.

You can run virtual machines created by Microsoft Virtual Server, Microsoft Virtual PC 7 or greater, VMware Server on VMware ESXi by using the free VMware Converterto import virtual machines.  VMware Converter also supports conversions from sources such as physical machines and certain 3rd party disk image formats.

Virtualizing servers is not a trend, but the future of the datacenter.  If you’re still maintaining all physical servers, now is the time to give virtualization solutions consideration.

NETinVM: Like it sounds, an entire virtualized network in a single VM

I was trolling around the Internet today and came across NETinVM, from the guys at the RaDaJo security blog.  According to the NETinVM web site:

“NETinVM is a single VMware virtual machine image that contains, ready to run, a series of User-mode Linux (UML) virtual machines which, when started, conform a whole computer network inside the VMware virtual machine. Hence the name NETinVM, an acronym for NETwork in Virtual Machine. NETinVM has been conceived mainly as an educational tool for teaching and learning about operating systems, computer networks and system and network security, but other uses are certainly possible.”

You can see a drawing of the preconfigured network here.

After reading the documentation, it sounds like setup and using the software is simple.  Check it out the next time you need to work on your penetration testing skills.  NETinVM is available here.

Free ConfigCheck Utility for VMware ESX host security assesment

Tripwire has a free, Windows based security assessment tool called ConfigCheck for VMware ESX hosts.  It rapidly assesses the security of VMware ESX hypervisor configurations compared to the VMware Infrastructure 3 Security Hardening guidelines. According to the VMware website:

Tripwire ConfigCheckTMis a free utility you can use to rapidly assess the security of your VMware ESX host configurations, according to the VMware security hardening guidelines. Co-developed by VMware and Tripwire, ConfigCheck provides an immediate assessment of the server configuration to ensure VMware Infrastructure environments are properly configured.

Tripwire ConfigCheck is simple & easy to use. To properly install & start-up the utility, follow these steps or read the blog posting:

To install and run ConfigCheck:

  1. Download the file configcheck.zip to a Windows machine that has Java Runtime Environment (JRE) version 1.5, or higher.
  2. Unzip the configcheck.zip file
  3. Double click on the file configcheck.cmd
  4. Accept the license agreement
  5. Enter the ESX host and user credentials
  6. Click the “Check Configuration” button

Once the check is complete you can click the test results to view remediation steps and view the Tripwire ConfigCheck Remediation Guide.  You can also listen to the Tripwire Podcast Operationalizing VMware ESX Best Practices – Introducing Tripwire ConfigCheck.

VMware VI Toolkit for Windows Beta is now available

The VMware VI Toolkit for Windows Beta is now available for download. The toolkit provides cmdlets for managing, monitoring, automating, and handling life-cycle operations for VMware Infrastructure components – virtual machines, datacenters, storage, networks, etc.

Less experienced administrators can use PowerShell commands included in the VI Toolkit to manage their VMware virtual infrastructure from the command line. Advanced administrators can develop PowerShell scripts that may be reused by other administrators or integrated into other applications.

The VI Toolkit for Windows 1.0 ships with 101 cmdlets: 97 PowerShell-based cmdlets and 4 Microsoft .NET cmdlets for use through PowerShell – The so called Web Service Access Cmdlets.

You can launch the VI Toolkit (for Windows) Console in one of two ways:

  1. From the Start menu, click Programs > VMware > VMware Infrastructure Toolkit > VMware VI Toolkit.
  2. Double-click the desktop icon (if you have chosen the option at installation). The VI Toolkit console window opens in a PowerShell window.

For more information see the VI toolkit for Windows Admin guide or the VMware community discussions. Don’t forget to download and install Windows Powershell before using this toolkit.