Virtual machines restarted unexpectedly

Similar Questions

• Persistent routes no longer work after the virtual machine restarts

  Hello community.

  I was hoping that someone can shine a light on a problem I have experienced. I have a virtual machine that multiple network cards. Some are exposed to the Internet, some are just private and some are B2B connections. Now, I put the roads for a particular to Adapater it limits by using this command: route add 13.x.x.x mask 255.255.255.255 if0x10005-p 10.x.x.x. I could pinch the IP address once I put it but once I restart the virtual machine of the road is still there, but I can no longer to pinch the INVESTIGATION period. This happens in several environments I.

  I am running windows 2003 which has been recently patched with the latest

  I'm running the latest ESX3 and VC 2.5

  Any help would be great.

  FYI - Pinch is another form of Ping.

  Set the gateway on the roads. Both that the getway is only not shared by any other way on the same system your traffic should go out any interface is associated with the network which is located in the gateway. in this way, you don't have to worry about the interface.

• Help!  Virtual machine restarts gives only read error!

  Hello

  A virtual machine is having problems to start.

  The virtual machine is a Linux system and when it starts to load the modules of the boot, some fail and generate an error that is only read-only.

  The problem occurred after a failure of communication with storage. (already resolved).

  Can someone help me? Because only resover with restoring a backup of the virtual machine.

  Maybe this article will be useful?

  http://KB.VMware.com/kb/51306

• schedule a restart of the virtual machine

  Is it possible to set up a schedule a reboot for VM of CR or in any other way?

  For restarts of the annex, it is best to do so within the guest and do not force a reboot of the VCenter.

  For one the VCenter will signal just the tools to do it, but the tools do always not react if the VM cared, but if you set the prompt to reboot using the Manager tasks or something similar, you have more control over the process of restarting, like forcing users, waiting for a period of time to allow users to log out with elegance etc... If you just put the virtual machine restart, that's how he will be treated a reboot now, and no action is possible.

• Virtual machines view alerts

  Hi all

  My VMs shows alerts in Vcenter Server, although there is no visible alarm on the alarm tab. Not for the virtual machine, not for the host, and not for the data center.

  I can't connect to host virtual machines display no alert. I enclose a photo so you can see what I mean with a warning sign.

  It happened when we had an unexpected failure and virtual machines restarted.

  How can I solve this problem?

  Thank you

  Edy

  Edy Hello,

  Earlier, few people have experienced the same problem and have been able to fix by doing the vMotion of virtual machines. You see if it works for you? Maybe a service restart vCenter server to refresh the inventory followed by vMotion would be good too.

  -Obaid

• Virtual MACHINE starts in EFI environment after crash

  Hello world

  I'm breaking my head on something that looks like a bug to me.

  A few weeks ago, the ESXi host on that I was running VMs crushed (power fail) and after powering back and from virtual machines on this stand-alone host, one of the virtual machines did not start correctly.

  This machine virtual runs Windows Server 2012 and booted up this time in the EFI environment.

  After some research, the EFI configuration is gone. When opening the Boot Manager Maintenance upward and choose 'Start configuration Options', no options are listed. When you add a new boot option and using the backup function, the settings are lost instantly. When comparing the parameters with any other SMV 2012 I have running, Miss me a lot of configuration such as startup options and some driver options.

  These two options will not save after closing the menu for adding these options. When you choose 'Start from a file' I can start the virtual computer by using the 'VOLUME LABEL\EFI\Boot\bootx64.efi No.' file. After the virtual machine restarts, it will be to the EFI environment.

  It is very difficult to find information about the EFI BIOS so I hope anyone here have experience with it.

  I even tried to restore the VM about 2 weeks before the accident, but even with the files of the virtual machine will start in EFI environment with no settings at all. So maybe the problem caused earlier; very weird! Also not to be able to save the new settings in the environment EFI seems very strange to me.

  Thanks for the replies! =)

  Hi René,.

  Hmmm... There is something of very, very wrong with this file NVRAM.  Looks like that the power failure has corrupted the file NVRAM in a way that confuses the firmware irreparably.  I consider this new next week (next year!) when I'm back in the office and will introduce an internal bug report if I find something that we can make it more robust.

  Although I generally recommend it not for VMS EFI, in your situation, your best course of action is probably the virtual computer power off, remove the file .nvram to the directory of the virtual machine (or rename it to something else, if you want to be extra careful), and power then it powered.  A fresh .nvram file will automatically create the virtual machine starts.  For the most part, reasonably normal Windows installations, the virtual machine must then be started automatically in the operating system installed.

  (For the benefit of other readers of the forum who may come across this thread, I repeat: do not delete a virtual machine EFI NVRAM memory, unless you understand the consequences!)  "It seems that there is rather than remove the NVRAM in this particular situation and very few others.)

  Please let me know if that gets things going again!

  And I'm going to one of our regulars of the forum, WoodyZ, avoid having to make his regular situation comment: If you haven't already done so, you can consider investing in an uninterruptible power supply (UPS) to keep your system running through power cuts or to allow at least a normal instead of a hardware failure stop.

  See you soon,.

  --

  Darius

• This virtual machine to become protected vsphere HA and HA can not try to restart after a power failure

  I got a 5.1 cluster with some problems HA.

  a few virtual machines are showing this

  This virtual machine to become protected vsphere HA and HA can not try to restart after a power failure.

  When I try to reconfigure HA on the host. It times out and fails.

  any idea?

  Instead of reconfiguring HA on the concerned host, have you tried to disable HA on the cluster and enable again? See: VMware KB: State of the virtual machine changes from protected to Unprotected

• ESXi host goes to the State and the virtual machine does not restart on other host does not

  Hi all

  I'm looking for a solution, in which case the host goes to the State and the virtual machine on it does not restart on a different host (they'll just gray) does not not what could be the problem here and how to fix it

  later when the failed host returns upward machines either go to motor off the coast of the State, or they show that under tension

  While the host is down or not responding do not I am able to ping the host ESXi (5.5) and able to ping the default gateway and the DNS servers of the host itself

  Yes AF, the answer to all these questions is Yes, it is a HA and DRS cluster active, I tried restarting mgmt service, we use a shared storage (storage iSCSI HP 3PAR and left hand)

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

• Get-VIEvent "vSphere HA restarted virtual machine.

  Hi score

  Can someone help me complete this script

  Get-Cluster 'test ' | Get - VM | Get-VIEvent | Where-Object {$_.} FullFormattedMessage-LIKE "{vSphere virtual machine rebooted HA *'} |" Select ObjectName,@{N="IP addr; E={($_. Guest.IpAddress)}}, Createduserid, FullFormattedMessage

  Out put:

  ObjectName IP addr Createduserid FullFormattedMessage

  ----------                          -------                             -----------                        --------------------

  VM1 05 - Sep - 14 16:14:29 vSphere restarted my virtual HA...

  VM2 05 - Sep - 14 16:14:25 vSphere restarted my virtual HA...

  VM3 05 - Sep - 14 16:14:25 vSphere restarted my virtual HA...

  Failed to get the IP address on this script.

  Thank you for giving if any good script to get vSphere HA restarted event when the host failure.

  Try like this

  Get-Cluster 'test ' | Get - VM |

  Get-VIEvent |

  where {$_.} FullFormattedMessage-match 'vSphere virtual machine rebooted HA'} |

  Select ObjectName,@{N="IP addr; E = {(Get-vue-Id $_.)} {{Vm.Vm). Guest.IpAddress}}, Createduserid, FullFormattedMessage

  Not sure property you are trying to achieve with ObjectName.

• Set the priority of restarting a virtual machine

  Hello

  I'm trying to set the priority of restarting a virtual machine in a cluster. I worked along THIS DISCUSSION to create this script:

  var myVcClusterDasConfigInfo = new VcClusterDasConfigInfo() ; 
  var myVcClusterDasVmConfigSpec = new VcClusterDasVmConfigSpec() ; 
  myVcClusterDasVmConfigSpec.operation = VcArrayUpdateOperation.add; 
  var myVcClusterDasVmConfigInfo = new VcClusterDasVmConfigInfo() ;
  myVcClusterDasVmConfigInfo.key = VM;
  myVcClusterDasVmConfigInfo.restartPriority =  VcDasVmPriority.high;
  myVcClusterDasVmConfigSpec.info = myVcClusterDasVmConfigInfo;
  var myVcClusterDasVmConfigSpecArray = new Array() ; 
  myVcClusterDasVmConfigSpecArray.push( myVcClusterDasVmConfigSpec ); 
  var myVcClusterConfigSpecEx = new VcClusterConfigSpecEx() ; 
  myVcClusterConfigSpecEx.dasConfig = myVcClusterDasConfigInfo; 
  myVcClusterConfigSpecEx.dasVmConfigSpec = myVcClusterDasVmConfigSpecArray; 
  Cluster.reconfigureComputeResource_Task( myVcClusterConfigSpecEx, true );
  

  Where Cluster and VM are objects of the WF input.

  Executions of thoughts scripts, however, in the CR, I get the error «the parameter of {entry.@enum.» InvalidDasConfigArgument.EntryForInvalidArgument} is not valid for the cluster.

  It's simple... but I just can't cope.

  Thank you guys

  Also I just realized... that the method I used is deprecated... grrr

  Here's the correct one:

  var myVcClusterDasVmSettings = new VcClusterDasVmSettings();
  myVcClusterDasVmSettings.restartPriority=VcClusterDasVmSettingsRestartPriority.fromString(priority);
  
  var myVcClusterDasVmConfigInfo = new VcClusterDasVmConfigInfo();
  myVcClusterDasVmConfigInfo.key=VM;
  myVcClusterDasVmConfigInfo.dasSettings=myVcClusterDasVmSettings;
  
  var myVcClusterDasVmConfigSpec = new VcClusterDasVmConfigSpec() ;
  myVcClusterDasVmConfigSpec.operation = VcArrayUpdateOperation.add;
  myVcClusterDasVmConfigSpec.info = myVcClusterDasVmConfigInfo;
  
  var myVcClusterDasVmConfigSpecArray = new Array() ;
  myVcClusterDasVmConfigSpecArray.push( myVcClusterDasVmConfigSpec );
  var myVcClusterConfigSpecEx = new VcClusterConfigSpecEx() ;
  var myVcClusterDasConfigInfo = new VcClusterDasConfigInfo() ;
  myVcClusterConfigSpecEx.dasConfig = myVcClusterDasConfigInfo;
  myVcClusterConfigSpecEx.dasVmConfigSpec = myVcClusterDasVmConfigSpecArray;
  task=ClusterName.reconfigureComputeResource_Task( myVcClusterConfigSpecEx, true );
  

• 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

• VMware Workstation 9.0 restarts my PC trying to turn on a virtual machine

  Hello everyboddy! On Sunday, I installed VMware Workstation, Version: version 9.0.0 build-812388 and configured a new virtual machine. I installed Windows 8 Enterprise on it and everything was fine. The same day that I had no problem at all - I have turned on and off the power of the virtual machine without any reboot. But today, when I try to power the virtual machine, I created loads for a while and then suddenly my PC restarts. I tried 3 times and the result was the same. Can you tell me where is the problem and help solve it, please?

  My PC:

  ASUS M3N-H/HDMI

  AMD Phenom 9350e Quad-core 2.00 GHz

  NVIDIA GT240 GDDR3 512 MB

  2 x 2 GB DDR II 800 MHz RAM (only 3 GB usable due to the OS)

  SE host: Windows 7 Ultimate x 86 SP1

  Settings of the virtual machine:

  

  PS Minutes ago I reduced the computer virtual memory to about 1.2 GB and made a new attempt to launch the virtual machine, but that this time he gave me the following error message: fatal error (vcpu-0)

  vCPU - 0:SVM is disabled and locked on this CPU (or something like that)

  And here's the last log file:

  One of your four hearts a SVM disabled and locked.  The other three are not.  You should be able to run virtual machines using the binary translation (set the execution mode privileged binary translation under VM-> settings-> processors).  However, you will get into trouble if you try to use (SVM) hardware-assisted virtualization.

  Have you checked for an update of the BIOS?

• Service mgmt-vmware restart causes the virtual machine downtime

  I'm looking in the configuration of SNMP on our ESX for Solarwinds alert guests, and is the last step I have to restart the service mgmt-vmware.

  I looked around online and have been unable to find confirmation that it will not have all the time with the virtual machines running on those hosts, as production machines.

  
  We run ESX v4.1.0

  Thanks in advance.

  Hello and welcome to the Forums!

  Restart management agents will have no negative impact on your guests.

• After restart ESXI Virtual Machine back to start

  I have an a bit Esxi 4 Virtual Machine but he is the one who each time to restart VmWare machine system begins to start, if I put a file or install software after restart all software and data are cleaned of VmWare and I have to reinstall all, why?

  This Virtual Machine is a migration of a real machine.

  Welcome to the forums

  There is an explanation why this can happen.

  1 VM start after reboot of the host:

  Look under the tab of host - start/stop the Virtual Machine configuration

  See if this virtual machine is enabled to start when the start host

  Disable this if you do not want that it

  2. all changes on VM ignored after reboot

  Right-click the virtual machine and choose change setting

  Take a look at the hard drive options, it can be set to independent - not persistent

  Uncheck independent or select persistent

  Please attribute points by clicking on correct/good