Spontaneous restarting the virtual machine after migration

Similar Questions

• 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

• 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

• Monitoring VM - how to restart the virtual machine

  Hi all

  Hit a problem in our environment that can not be solved, but wanted to tender hand to people and see if they have found a way to replace.

  Currently have followed vm enabled in our cluster. Thing is watching us to restart the virtual machine VMware tools demonstrated to a status of "not running" - now, the key is to most of the definitions, the system is available in this case, can be crazy, RDP'ed etc, but we here again them restarted as he finally solves the issue we see (for example unable to connect via citrix for the machines in question)

  Duncan in the post below highlights in order to avoid false positives any i/o to storage/network activity will be verified after that heatbeats failed to "double check" there is a problem with the virtual machine

  Favorite VM monitoring (aka VM HA) - yellow bricks

  What I asked is it possible to replace verification of network storage/IO activity and then restart the virtual machine VMware tools on them stops as soon as?

  Many tx for all thoughts

  «.. . is there a way to replace check network activity of storage/IO and then restart the virtual machine of VMware tools on them stops as soon as...? »

  You can always use a supervision-process inside the virtual machine for this tool (perhaps more followed VM). It acts independently and allows much finer control, i.e. it can try first (re) start vm-tools before restarting. Same BSOD /-kernel panic can be dealt with by VM itself. It can actually be even more robust, not dependent on VMware infrastructure.

• 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é

• HA restarts the virtual machine if the storage connectivity is lost? If how is HA needs to be configured?

  We plan to go forward with a single dual-port HBA in each of our ESX servers. My concern is that the HBA becomes a single point of failure. HA supports restarting the virtual machine which lose connectivity to back-end storage. We did some testing and it does not appear that HA does not handle this. Even when 'enable us VM monitoring' the machine virtual do not restart on other ESX servers in the cluster that they hang just basically. I've read a few articles which seem to indicate that it should work, but I'm not able to get there. Any thoughts there?

  HA checks the availability of default ESX host. There is an option to monitor the heartbeats reviews, as well. Maybe this will do, but sometimes a guest still works for awhile even if the disk is lost. And as for a long time VMware tools send heartbeats...

  AWo

  VCP 3 & 4

  Author @ vmwire.net

  \[:o]===\[o:]

  = You want to have this ad as a ringtone on your mobile phone? =

  = Send 'Assignment' to 911 for only $999999,99! =

• Cannot depend on the virtual machine after reboot

  Hello world

  Thanks for reading this post.

  My version VM ESXI4.1.0, 348481.

  Here's my problem:

  One day my VM was hanged, and I tried to restart.

  After the reboot, it can be turn on. And I tried to remove the inventory and to recreate the virtual machine.

  However, I can't find the. VMX file in the data store.

  So I tried to create a new virtual machine and put the files in this folder, but it can also work.

  Please see the capture screen, (http://clip2net.com/s/2aNUG)

  Could someone give me guidance and advice how to solve?

  Thank you very much.

  According to the latest vmware.log file, you have tried to access one of the files base/flat with a wrong header file (40 GB)! This hopefully not bad data on the virtual disk. In any case, I've recreated the missing files (see attachment), so you should be able to redo the work of the virtual machine. Because the vmware.log file did not help, I've recreated the instant chain according to the timestamps of the delta file.

  Please follow it below mentioned steps exactly to avoid problems in case something does not work as expacted:

  • Make sure the flat files as well as files 2 6 delta are still in place (not renamed,...)
  • remove the virtual machine from the inventory of the host (right-click-> "Remove from inventory") ESXi
  • delete the temporary/second .vmx unless there is a special need for it
  • Download the files from the .zip file in the folder of the virtual machine on the data store
  • Click right newly downloaded virtual machine's .vmx file and choose "add to the inventory.
  • create a new snapshot (this is important!)
  • Turn on the virtual machine

  If something is not or you have questions, please send back before moving on to the other steps.

  If everything works as expected you should consider the 'Delete All' snapshots in snapshot Manager. This will release not only almost 200 GB of disk space, but can also improve the performance of the virtual machine. Because the size of the snapshot, remove snapshots may take some time, probably in hours!)

  André

• No network connection to the virtual computer after migration manually to the new host

  We have added six new hosts to our environment, and I was tasked to test connections of VIRTUAL LAN on each of them before we move VM production of their.  This is probably a simple problem, but I am new to VMWare and need help.  I already talked to our network guys, and he assures me that the physical switches are setup and working properly.  We work a vDS.

  I'm testing 14 VLANs on six new hosts.  All but one are constantly working.  (They all work on the hosts of origin which were in force before.)  I have a static IP configuration on my test VM and MAC is set to automatic.  I checked the MAC does not change when you migrate to other hosts and the VLAN correct is listed in the settings the VM network (it is not empty).  Him VLAN will work on three of the six hosts, but not all at the same time.  The strange thing is that guests at work are constantly changing.  For example, this morning hosts11, 12 and 14 may work, but this afternoon, that could change at hosts12, 14 and 16.  I don't understand why they would change on their own.

  My test consists of VM testing, migration manually, powering back, then he ping from my computer off.  Of course everything works when I get ping responses.  When I get no answers, the test of the virtual machine has a yellow exclamation mark on the network icon in the system tray.

  What should I do to fix this?

  How is the network configured?  You have a different NIC port/cable for each VLAN or Trunking used on the side of the switch?

  If you use circuits on the side of the switch, then your GRPE ports virtual switch a VLAN ID needs to match the vlan is underway to shared resources.  No matter if it's a standard switch or switch distributed... you still need this ID of vlan.

  I've seen the random question that you encounter if missing one or more of of the uplinks on the side of the switch the VLAN.

• 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

• Block of VMWare workstation to restart the virtual machine

  Hi all...

  I use vmware workstation 9.0.2 on a machine running windows 7 Professional (64 bit) on any domain.

  the problem is that: when I reboot whole VM (windows/linux), vmware stop working a present the home screen (with options F2, F12, ESC)... at this time, all orders (average, suspend, reset) does not work... I need to manually complete the vm procecess - ware.exe, remove *.lck items and restart the physical machine...

  If I stop the virtual machine, all work without problems...

  any ideas?

  Hi riccimaticand welcome to the VMware communities!

  Try disconnecting the virtual CD/DVD drive.  It seems that there are situations in which problems arise to restart a guest, operating system while its virtual optical drive is connected.  The most common cause is using MagicDisc/MagicISO on the host, which is known to cause exactly the problem you describe.

  See you soon,.

  --

  Darius

• 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é

• 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

• 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é

• Is reset or restart the virtual machine should all expanding vmdk size?

  Hi all

  While extending the size of 20 to 28 GB GB vmdk I can extend when the VM is in poweron State, but he didn't think inside the virtual machine. The disc is resized when the virtual machine won reset or reboot.  I would like to know if the reset or restart that virtual computer is must have for resizing vmdk. If it is then what is the use of expansion of disk while the VM is in poweron State?

  Thank you

  Vijaya

  Yes with windows 2008, you can extend the OS disk to create a new drive letter instead.

  Here is a tutorial: http://www.petri.co.il/extend-disk-partition-vista-windows-server-2008.htm