Cannot depend on the virtual machine after reboot

Similar Questions

• Unable to connect to the virtual machine after adding new eSATA drive

  Hello.

  I'm trying to connect my new 2 TB drive in VMWare Workstation. It is connected via eSATA to the host computer, and it works. I added the drive to the desktop as a new "physical disk." But now I can not power the workstation the most.

  (1) when I start the VMWare Workstation it right ask admin (it didn't need before).

  (2) when I turn on the prompt does not charge even the bios. It shows a rear screen with the logo of VMWare for a while and then stop saying: "VMware Workstation cannot connect to the virtual machine. Make sure that you have the rights to run the program and access all directories that it uses and access rights to all directories for temporary files. »

  The host is running Windows 7 x 64. The workstation runs under the standard user account.

  Thank you.

  Hmmm - it's unexpected - works for me here - only difference: I tried with only 1 TB disks.

  You start Workstatiion as an administrator?

  _________________________

  VMX-settings- WS FAQ -[MOAcd | http://sanbarrow.com/moa241.html]- VMDK-manual

• Cannot start the virtual machine after you create snapshop

  I found a strange behaviour. I have a Windows 2008 guest that I just copied in my new box ESXi. I am trying to create a snapshot before upgrading the guest to 2012 Windows operating system. The virtual machine has currently no snapshots. Whenever I have create a snapshot, he succeeds, but then I can't start the virtual machine saying that it does not find the vmdk file delta even though I see there in the data store. In order to start the virtual machine, I have to delete the inventory and it readd, but then I lose the snapshot. I also have another computer virtual running Windows 8.1 that does exactly the same thing. How can I create snapshots safely without damaging the virtual machine? I also tried to create the snapshot while the virtual machine has been activated but that makes crashing and then it does not start again, so I have to repeat the process to remove the inventory and it time. Frustrating. See the screenshots, I have attached.

  Once these virtual machines have been in Hyper-V in the past and I just convert to VMware format using the StarWind V2V converter.

  Yes, for an ESXi host and target you must either select the ESX f.vmdk as format target (growable option is for VMware Workstation), or you must convert the virtual machine once more instead of simply upload the files to an ESXi host.

  André

• Students cannot "connect/disconnect the virtual machine's CD/DVD devices.

  I will start with this context (and apologies for the wall o ' text): I'm a newbie.  I took the course VMware local community college offers [VMware ESXI Server Enterprise (CIS197)], but I've not yet certified. And I don't have a real experience, except what I have taught myself so far.

  I recently accepted a position of learning associated with the College (think: glorified lab tech). I was tasked to work with stuff from VMware in the laboratory (among other things such as Cisco and Juniper equipment). There is no pass-down information like the previous left the position four months ago.

  We have a single host running ESXi 348481 4.1.0. "We have vCenter Server (5.5.0, 1312298), running on Windows Server (2008 R2, Enterprise Edition).  Access host and vCenter through two different IP, addresses using the vSphere client (either 5.5 or 4.1, using a single application - depends to know if I connect to the host or vCenter).

  At that time, the host is using local storage only (we have plans to change this, but it will take time).  The host is not a production on its own server, because it does not have a school systems.  He does, however, run a number of virtual machines in the lab, students use (Linux, Microsoft, Web design, etc.).  So, right now, I can't take it down.

  I was tasked to create a number of virtual machines that students can use to make the basic labs of Microsoft Windows 7.  So far, I have:
  -Created users, one per student, on the host.
  -Creating VMs, deploy one per student, I have a gold model vcenter.
  -Creation of roles to limit the access of students to just their VM attributed, which they access via client vSphere.
  -Created a Windows Server 2008 R2 domain controller that is also a DHCP server.
  -Created a virtual network, which is accessible only by the Windows 7 virtual machines and is not visible outside the vSphere environment (if I said this right - he does not see the Internet or school network).

  So far, it's all good.

  However, I need to be able to allow students the ability to edit the ISO file on which their VM points in order to complete some laboratories. I guess they would use the button "connect/disconnect the virtual machine's CD/DVD devices" on the taskbar (or console window). It does not work.
  I searched a lot and found that others have had the same problem.  However, all of the solutions I've tried so far have failed.  When they click 'Connect to ISO image on the data... store. "they get an error message means nothing to me,"an internal error has occurred in the vSphere Client. Details: Object Reference not set to an instance of an object. Contact VMware support if necessary.
  The role that I use for students has these settings:
  -Data store > Browse the data store
  -Virtual Machine > Configuration > change the settings of the device
  -Virtual Machine > Configuration > settings
  -A bouquet under the virtual machine > Configuration >
  -Configure CD media
  -Console interaction
  -Connection of the device
  -On
  -Power off
  -(and more, which I don't believe are important to the question)
  -State > create the snapshot
  -State > go back to the snapshot

  I tried "Virtual Machine > Configuration > add existing disk", "Virtual Machine > Configuration > add new disk" and "Virtual Machine > Configuration > add or remove an instrument" with no luck.

  Either by the way, the root account can do all these things, but no other account can - not even a game as an administrator account.

  I've seen mention I have apply the role in the data store.  It is perhaps part of the problem. I can't see the data store when I am connected to the host (wellll, I can, if I click on the host name, then on the Summary tab - but roles do not apply at this stage).  I see is 'Inventory' (which has virtual machines and Pools of resources), 'Rôles' and 'log files '.

  I can see the data store when logged in vCenter. Roles of students, however, are defined on the host computer. If I clone the role of users in vCenter and change this role cloned to have "permissions" that those who are on the host computer and then apply it to the data store, it still does not work.

  So, after all this (which I hope I've included all the necessary information), what can I do to allow the students to change ISO to which they are connected?

  Of course, if I left something, or if someone has a question, please ask.  I want to get this resolved as soon as I can.

  It turns out that I finally found the solution to the problem.

  What 'fixed', it is sufficient to vSphere Web Client to vCenter, which then allowed us to use Single Sign-On (SSO).  This, in turn, allowed us to define users and roles in vCenter (rather than having set them up directly on the host computer) which have then been applied to the VMS of students and also to the data store.

  Now, they can (de-) connect their ISOs at will.

  I find it interesting that vSphere Client (application) shows the users (and the things that they have access to), but it won't let you set of users.

• Unable to start the virtual machine after failing to remove the snapshot

  Recently, I tried to delete a snapshot on a Windows XP virtual machine in VMware server 2.0. After a few minutes, the operation has failed, then the GUI crashed. I was not able to manage one of my virtual machines until I rebooted the server. My other virtual machines still work fine. I can't just run the virtual machine on which I tried to remove the snapshot. This virtual machine is very important to me and I would try to get it back. Does anyone have advice? Also, I upgraded this version of VMware server 1.x to 2.x, so please let me know if this may have something to do with this problem. Thanks in advance.

  An additional note. If the virtual machine starts, I suggest that you run chkdsk, just to make sure that there are no problems with the file system of the client.

  André

• Unable to start the virtual machine after restoration

  Guests including Test host: ESXi 5.1.0.1065491

  Vm problem: 32-bit, Server 2003

  I use Veeam Backup & Restore 6.5 to back up my vm.  I always do a test restore to ensure that my backups are good.  I'm having a problem with a restore.  The 32-bit Server 2003 vm starts just fine on the main host it runs on.  All the vm are 64-bit except for one who is a 32-bit Server 2003 vm.  Restoring the machine virtual and implemented on a host except the 32-Bit vm Server 2003 test.  After restoration and trying power to the top, I get the following error:

  Unable to start the virtual machine.

  Turn on VPCM module has failed.

  Viewed performance counters require version 3 or greater of architectural performance monitoring.

  Anyone know if there is a fix for this problem?

  TIA,

  Mux

  I assume you are using different hardware (CPUs, the BIOS settings) for VMS restored!

  The virtual machine has VPCM enabled, which causes the problem. You can either disable it in vSphere Web Client (you can do this in the vSphere Client Windows), or directly modify the .vmx VM by setting vpmc.enable to "FALSE".

  For how toggle this setting in the Web Client see allow virtual in the Web Client vSphere CPU Performance counters. If you want to edit the .vmx file manually, you need to delete/re-add the VM from the inventory or recharge (see http://kb.vmware.com/kb/1026043)

  André

• Could not start the virtual machine after you use vmkfstools to resize - HELP!

  I thought I knew what I was doing, but apparently not...

  I tried to increase the size of a VM over 36 GB drive and now I can not start the server. Here's the change front of directory list:

  -rw - 1 root root 16781312 Sep 20 19:46 PJAEast-DL01-000001 - delta.vmdk

  -rw - 1 root root 325 28 August to 01:52 PJAEast-DL01 - 000001.vmdk

  -rw - 1 root root 4096 9 February 14:55 PJAEast-DL01-000002 - delta.vmdk

  -rw - 1 root root 277 9 February 14:55 PJAEast-DL01 - 000002.vmdk

  -rw - 1 root root 28201 28 August to 01:52 PJAEast-DL01 - Snapshot1.vmsn

  -rw - 1 root root 28267 9 February 14:55 PJAEast-DL01 - Snapshot2.vmsn

  -rw - 1 root root 131604480 26 August at 08:04 PJAEast-DL01 - flat hard

  -rw - 1 root root 8684 25 August at 21:03 PJAEast - DL01.nvram

  -rw - 1 root root 589 25 August at 15:18 PJAEast - DL01.vmdk

  -rw - r - r - 1 root root 1042 28 August to 01:52 PJAEast - DL01.vmsd

  -rwxr-xr-x 1 root root 2779 Feb 9 15:10 PJAEast - DL01.vmx

  -rw - r - r - 1 root root 267 Feb 9 15:10 PJAEast - DL01.vmxf

  -rw - 1 root root 9898631168 9 February 14:54 PJAEast-DL01_1-000001 - delta.vmdk

  -rw - 1 root root 331 28 August to 01:52 PJAEast-DL01_1 - 000001.vmdk

  -rw - 1 root root 73728 9 February 14:55 PJAEast-DL01_1-000002 - delta.vmdk

  -rw - 1 root root 283 9 February 14:55 PJAEast-DL01_1 - 000002.vmdk

  -rw - 1 root root 36322836480 28 August at 01:41 PJAEast-DL01_1 - flat hard

  -rw - 1 root root 597 25 August at 15:18 PJAEast - DL01_1.vmdk

  -rw - r - r - 1 root root 78710 25 August at 16:06 vmware - 1.log

  -rw - r - r - 1 root root 68108 25 August at 20:43 2.log - vmware

  -rw - r - r - 1 root root 122302 28 August at 01:41 vmware - 3.log

  -rw - r - r - 1 root root 90557 Sep 20 19:54 4.log - vmware

  -rw - r - r - 1 root root 69453 9 February 14:54 vmware.log

  Then, I run the command:

  vmkfstools x 256g PJAEast - DL01_1.vmdk

  And now the virtual machine does not start, return an error: "the virtual disk parent has been changed since the child was created."

  The directory listing is now ("BOLD" indicates the change of information post-vmkfstools):

  -rw - 1 root root 16781312 Sep 20 19:46 PJAEast-DL01-000001 - delta.vmdk

  -rw - 1 root root 325 28 August to 01:52 PJAEast-DL01 - 000001.vmdk

  -rw - 1 root root 4096 Feb 9 16:12 PJAEast-DL01-000003 - delta.vmdk

  -rw - 1 root root 277 Feb 9 16:12 PJAEast-DL01 - 000003.vmdk

  -rw - 1 root root 28201 28 August to 01:52 PJAEast-DL01 - Snapshot1.vmsn

  -rw - 1 root root 28267 9 February 14:55 PJAEast-DL01 - Snapshot2.vmsn

  -rw - 1 root root 131604480 26 August at 08:04 PJAEast-DL01 - flat hard

  -rw - 1 root root 8684 Feb 9 16:12 PJAEast - DL01.nvram

  -rw - 1 root root 589 25 August at 15:18 PJAEast - DL01.vmdk

  -rw - r - r - 1 root root 1015 28 August 01:52 PJAEast - DL01.vmsd

  -rwx - 1 root root 2779 Feb 9 16:12 PJAEast - DL01.vmx

  -rw - 1 root root 267 Feb 9 16:12 PJAEast - DL01.vmxf

  -rw - 1 root root 9898631168 9 February 14:54 PJAEast-DL01_1-000001 - delta.vmdk

  -rw - 1 root root 331 28 August to 01:52 PJAEast-DL01_1 - 000001.vmdk

  -rw - 1 root root 73728 Feb 9 16:12 PJAEast-DL01_1-000003 - delta.vmdk

  -rw - 1 root root 283 Feb 9 16:12 PJAEast-DL01_1 - 000003.vmdk

  -rw - 1 root root 274877906944 28 August 01:41 PJAEast-DL01_1 - flat hard

  -rw - 1 root root 599 9 Feb 16:11 PJAEast - DL01_1.vmdk

  -rw - r - r - 1 root root 68108 25 August at 20:43 2.log - vmware

  -rw - r - r - 1 root root 122302 28 August at 01:41 vmware - 3.log

  -rw - r - r - 1 root root 90557 Sep 20 19:54 4.log - vmware

  -rw - r - r - 1 root root 69453 9 February 14:54 5.log - vmware

  -rw - r - r - 1 root root 39510 Feb 9 16:12 6.log - vmware

  -rw - r - r - 1 root root 39411 Feb 9 16:12 vmware - 7.log

  -rw - r - r - 1 root root 39410 Feb 9 16:14 vmware.log

  I can't do anything else until I get comments. Can anyone recommend a way to solve this problem?

  I thought I knew what I was doing, but apparently not...

  I agree

  Two a problem with the new drive.

  1. You get the error message comes from the basic disk with a different size than the disks of the snapshot.
  2. With a size of 256 GB, you will not be able to create snapshots of the disk (on ESXi prior to 5.0 with a block size of 1 MB)

  What you can try to do is to edit the file PJAEast - DL01_1.vmdk :

  • 536870912 VMFS 'PJAEast-DL01_1 - flat hard' RW--> RW 70943040 VMFS 'PJAEast-DL01_1 - flat hard. "
  • DDB. Geometry.Cylinders = "33418'-> ddb.geometry.cylinders = '4416.

  After that, I would recommend to clone the virtual disk to a new one, replace the virtual disk in the virtual machine settings and resize it to a maximum of 254GB (see "calculates the time system required by the snapshot files" at http://kb.vmware.com/kb/1012384)

  • vmkfstools-i PJAEast-DL01_1 - 000003.vmdk PJAEast - DL01_1a.vmdk

  André

• Unable to start the virtual machine after Migration - ESXi hosts

  Last night I wanted to move a virtual machine to a host of test to a production cluster.  All hosts (test and production) have shared access to the same LUN, so I usually am able to simply remove the virtual machines of the inventory in the test environment and add them to the production environment by accessing the .vmx on the data store file.  Two of the 3 hosts migrate perfectly and are running in the production environment.  However, the third server, while the migration starts.

  First he gave me errors that it was missing some files.  The only thing I did was different to rename the folder for the virtual machine on the data store.  It was called 'New Virtual Machine' for a reason, so I renamed it to "Antivirus."  However, something strange happened.  Instead of renaming the folder, it seems was created a new folder named "Antivirus" and the old folder 'New Virtual Machine' was still there.  In addition, the renamed folder 'Antivirus' had only SOME of the files needed.  So I just copied from the old folder in the folder "Antivirus" and he hung up the virtual disk of 20 GB file.  So I closed the VI client and checked the vdmk 20 GB folder and back this morning is in the folder with other files.  However, when I try to start the virtual machine, I get the "cannot access a file because it is locked" error message.

  I've done some detective and I noticed that in my second datastore where was the other folder vdmk, the file was now .40kB in size.  Looks like I've lost my other vdmk folder.  What happens here?

  It looks that the virtual machine was still running when you tried to change the name, so the old folder could not be renamed because of the lock. That's why a new folder has been created instead, and why your vm hung on the vmdk file until the lock has been released. Don't know what happened to the 2nd vmdk file, but the file vmware.log in virtual machine directory must have some info as to why does not start the virtual machine. If the 2nd vmdk is gone, this might be a reason.

  -KjB

  VMware vExpert

  Post edited by: kjb007: changed vm in vmdk

• Unable to connect to the virtual machine after they are created

  I installed VMware view and connected to my server Vcenter. Composer, I installed the server vcenter and View manager recognizes it.

  I created a virtual Windows Vista machine, is joined to the domain and instant, it.

  I then created a persistent office pool and allowed users to access.  I can see the virtual machine created the VCenter

  However, the view Client cannot access the virtual machine (he can see the office pool) bit tells me that the customer is not available.

  Any ideas on what I missed?

  Go to the desktop the pool in view Administrator resources and check the status, it should say "Ready".  If this is not the one usually means that there is something blocking the port 4001 of the agent on the view connection server.  I got this when deploying a pool on a different subnet and there is a network between the areas of the network firewall.  The Vista firewall can sometimes be reset on the deployed virtual check computer so who has not been reactivated and adjust the GPO if necessary.

• Error occurred by restarting the virtual machine after instant collection

  Configuration:

  2 X ESX 3.5 U3 in cluster (Enterprise license) + Virtual Center 2.5 update 3

  18 customers running Win2k3 servers and Oracle on RHEL 3 servers

  2 X SAN DELL MD3000i with two controllers (active / active).

  Question: Last night, when the backup of VCB, we lost the SAN n ° 1 completely (two controllers at the same time).

  We have a few customers with Microsoft Raid 1 (1 on San 1 and 1 drive on San 2).  guests in mirror mode survived 40 minutes after the San n ° 1 crashed.

  After checking saves files I found that: ESX shutdowned guests due to a problem with the snapshot.

  I feel really bad this morning... because I told my boss we're safe if we lose 1 SAN because we are mirrored on 2 SAN.

  Why stop ESX invited after problems with snapshots. Also, we received a lot of Virtual Center with false alert alarms (virtual machine does not).

  ESX filled 800 megs of log files in a few minutes with the same message (path fails, try another a blabla).

  What the purpose of putting my guests in mirror mode stop ESX if my guests after losing the path during backup?

  Hello

  Conclusion?

  If SAN #1 accident during the VCB backup, you're dead?

  If you use software raid within the virtual machine is then SAN1 dies, the VM will crash because the Bank of support file (this case a delta) is no longer available and there is no way to read or write data even.

  Software RAID does not apply to things outside of the virtual machine. A solution would be to have a device that can do Raid through mirroring without.

  Best regards

  Edward L. Haletky

  VMware communities user moderator

  ====

  Author of the book "VMWare ESX Server in the enterprise: planning and securing virtualization servers, Copyright 2008 Pearson Education.»

  SearchVMware Blog: http://itknowledgeexchange.techtarget.com/virtualization-pro/

  Articles of blue Gears - http://www.itworld.com/ and http://www.networkworld.com/community/haletky

  As well as virtualization at http://www.astroarch.com/wiki/index.php/Virtualization Wiki

• Could not power on VM: no space is available on the device: cannot power on the virtual machine.

  VMware esx ei, 3.5.0 123629

  Physical memory: 64 GB

  Hard drive: 1.63 TB

  7 virtual machines. 5 of them are configured with 4 GB memory and 2 of them with 2 GB of memory. I am able to power on 3 virtual machines with 4 GB of memory.

  When I try to turn on 4th VM with 2 GB of memory, I get this error message "could not power on VM: no space is available on the device: cannot power on VM.»

  I would like to know if this is the limitation of the ESX Server? How should I size the memory for VMS if I want to run every 7 virtual machines to the

  Moreover, given that I have 64 GB of physical memory. Is there documentation that provides a report of the maximum allowed memory configurable

  compared to the virtual memory?

  Thank you

  Ganesh.

  Ganesh,

  Memory reservations are defined based on VM by VM.

  You can allocate more memory to the virtual machines you have in your host (it's not really a good idea to go crazy with the overcommitment of memory, but some level of excessive pressure is used in general).  Memory applied to your VM resources are shares, bookings and VMkernel Swap limits.

  Just to illustrate:

  You allocate 8 GB memory to a virtual computer.  If you take all the parameters by default, ESX will allot a 8 GB VMkernel Swap file in the base directory of your VM (it will have the extension ".vswp") this VMkernel Swap file is a safety net.  Your virtual machine, at this stage, can consume up to 8 GB of memory If physics is available from the host.  If the memory of your host is overcommitted, some of the available memory 8 GB could be allocated on 8 GB VMkernel Swap file.

  If you set a reserve of memory - 2 GB - this means that the vmkernel will still award the first 2 GB of memory used by the virtual machine to the physical memory.  This is not means that the 2 GB of memory reserved is carved off the coast and completely dedicated to the virtual machine.  This means that the vmkernel offers up to 2 GB of RAM to the VM when and if she needs to use it.  It is a guarantee that the memory will be available upon request.  Because of this guarantee of the VMkernel, VMkernel swap file only has to make sure that the 6 GB memory is satisfied (4 GB total less the 2 GB reserved), so the VMkernel Swap file is only 6 GB in size.

  Actions are a mechanism for prioritization and limits are a cap on physical memory ever allocated to the VM.

  You can set up any number of memory for the virtual machines that you want - frankly, overcommitment of memory for ESX is a very good thing, but you must be vigilant about watching your systems if approve you.  If you have 64 GB of RAM, and you only configure your virtual machines to use total 32G, then you lose 32 GB of RAM.  If you allocate, say, 96 GB of RAM (total) to your virtual machines, then you look at a 50% overcommitment.  What to watch in overcommitting memory is application performance (and more importantly - perception of the user of this performance) and also the memory ballooning and VMkernel Swapping activity.  Those who can both will be in graphics performance in VirtualCenter.  I would recommend reading the Guide to management resources for more details.

  Hope that provides an overview.

  Thank you

  -jk

• Internal error starting the Virtual Machine after Crash

  I'm in Yosemite and when running a virtual Windows 7 machine it suddenly stopped working. The beach ball slider off for half an hour and I was force quit Fusion 7. While trying to launch the virtual machine again, I get a message "Internal error" generic.

  Already tried: restart my Mac, repair permissions, uninstall/reinstall Fusion 7, even try to fix the main VMDK file (it is divided and returned without error).

  Any suggestions?

  Looks like you run your virtual machines from a disk formatted in NTFS by using the Paragon NTFS driver.  Have you tried to use disk utility to check the integrity of the NTFS partition?  Error messages suggest strongly that the NTFS file system may be corrupted or there may be a problem with the NTFS driver.  (I think that the NTFS driver is not available when you used the recovery environment to check disks).

  If this volume extracted also OK through the disk utility first aid option, you pourriez either requires an upgrade of your driver of Paragon NTFS since version 11 to version 12 (which their Web site claims is the first version with support of Yosemite), or you may need to set the drive on a Windows machine and have windows to control its own native on the volume file system in Paragon file system audit case missing something.

  See you soon,.

  --

  Darius

• State of the virtual machine after the host failure

  Hello

  If a virtual machine is running on a host and that host suddenly powers off dirty, like a power failure or a remote access card power the server due to a fault, overtemp etc., what happens to the virtual machine?

  My guess is the virtual machine is actually difficult, dirty off too and if HA is configured, etc it is going to do a full power on sequence. Or is it restart on a new server and be automatically in the same power state with the same States of memory and cpu until the host has dropped dead? So if I got a connection of the DRC in a vm of windows server and the host dies suddenly and it restarts, reconnect to the session even State immediately before the breaking of the host?

  Thank you

  When ESX\ESXi fails due to power failure:

  No configured HA:

  1. all virtual machines is also faces off against the sudden stop. SMV will lose data runtime and all communications (including the RDP connection) will be interrupted.

  Configured HA:

  1 VMs will be powered - on on a different host. However, its the same as a reset of the virtual machine, we will lose any unsaved data.

  VMware FT:

  We ensure 100% uptime for a virtual machine using VMware Fault Tolerance. In case of failure of the host, next time school resumes VM in FT. More details on IP are available at the following link.

  http://www.VMware.com/products/fault-tolerance/overview.html

• Cannot turn on the virtual machine in VMware workstation

  Hello

  I have windows 2008 stocked VM of windows 4.1.Inside ESX VM 2008 I installed VMware workstation and created the virtual machine in vmware workstation. When I have tride to power on the VM iam getting error below. Please help me.

  "Running vmware workstation in a virutal machine requires external thr virtual machine is configured to run the vmware esx host operation system.you may not power on a vierutal machine until the external virtual machine is reconfigured.

  Thank you

  Victor

  This is the VM vmx nested - you must add this line to the external virtual machine - one who runs in ESXi

• No network on the virtual machine after the use of converter

  I was running a basic vm (WinXP) on an esxi4.1 host running short of disk space.

  So I ran the vCenter Converter Standalone client to copy the original VM on a new - the only thing that I changed the size of the disc thin provisioned avaiable.   The copy/convert seemed to work your.

  I started in the new virtual machine, and it came exactly as the old one (with the largest disk).

  ... but the network on the works of more than vm.

  I can still use vSphere to connect to the esxi server and bring up the VM console (which tells me that the network the server works very well).  When I look at the configuration of the virtual machine, it looks exactly like the old (complete with a network powered).   But on the virtual machine, I can't even ping the router, much less get to the dhcp server.

  I even went so far as to stop the virtual machine, remove the network card, restart the virtual machine (if the network has been removed from the virtual machine), stop the virtual machine again, add a NEW network adapter.

  Still the problem remains.  The virtual machine has a network card - but has no network.

  A few thoughts:

  You use a managed physical switch? If so, check if the MAC address of the VM is seen on one of the uplink ports.

  The network management and the virtual machine using the same IP subnet? You could probably try (if possible) is to create an another vSwitch and attach the XP VM to it to see if there is a problem with the virtual machine and the management on the same vSwitch network.

  André