Random virtual machines stop...

Similar Questions

• Virtual machines stop in Citrix

  * Original title: Windows 7 stop down

  Help!

  I have problems with the VMS in Citrix.

  Background

  I have 400 users and they use citrix to log on to the customers of the thing. But randomly, I get 5 or 6 users with questions that they can't connect, profile it gets damaged and needs to be recreated.

  This is where Microsoft can help - watching the event logs, I'm changing the time of the system that has no apparent reason.

  the general message said: "the operating system stops when the system *'»

  Thank you

  Michael

  Hi Michael,

  According to the description of the problem, you are connected to a network domain and using the virtual machine. We have, on this forum do not address this question. We have a dedicated forum dealing with this type of problem. So, the question you posted would be better suited in the TechNet Forums. I would recommend posting your query on the Forums TechNet.

  Keep us.

  Kind regards

• Windows 7 virtual machine - stop even if someone is connected via RemoteDesktop

  Hello

  I have a machine virtual windows 7. It runs on a host SLES 11 SP3 with KVM. When the host wants to stop the virtual machine, it signals the vm via ACPI. But if someone is connected via RemoteDesktop, virtual machine refuses to stop. KVM waits a while, then turns off the virtual machine. Is it possible to stop a windows 7 even if someone is connected via RemoteDesktop?

  Something like for example a registry key?

  Thank you.

  Bernd

  Hello

  Thanks for posting your query on the Microsoft Community.

  According to the description, I understand that you are facing problems with Windows.

  I suggest you post your query on The TechNet Forums , because we have experts working on this type of questions and for you help the better.

  Check out the link:

  https://social.technet.Microsoft.com/forums/Windows/en-us/home?category=w7itpro

  Hope this information helps. Please let us know if you need any other help with Windows in the future. We will be happy to help you.

• Random virtual machines after vMotion and Storage vMotion network loss

  Hi all -

  I have a couple of tickets open with VMware and our supplier of SAN, EqualLogic, on this issue.  Since the configuration of our production and DMZ clusters we noticed that the virtual machines will sometimes drop network connectivity after a successful vMotion and Storage vMotion.  Sometimes, although much less frequently, virtual machines also spontaneously lose network overnight.  What happened only a few times.  The strange thing is that the other guests on the VM host are fine - they lose any network.  Actually, I can do no more than 3 computers virtual host to another, and 2 of 3 can switch correctly, so that we lose the network.  The work around?  Simply 'disconnect' from the virtual NETWORK card 'reconnect' and the virtual machine will start the return packets.  I can also switch the VM troubled return to the host State and it will find the network.  I can it reboot and re - win network.  I can re - install the virtual card completely, and she re - win network.

  VMware has seen a lot of mistakes of SAN in our log files in order to update us our SAN firmware to the latest version.  That seems to have fixed that but we still have the issue.  Here are some of the specifications - all environments are virtually identical except for memory:

  Of PowerEdge R810

  NICs Broadcom 5709

  EqualLogic SAN running 5.0.5 F/W

  We use frames.  ESXi is fully patched.  I haven't seen a boss or not, it is only some guest operating system that loses the network, but we are a Windows environment.

  When a virtual machine loses the network, we can not:

  • Ping to it
    
  • Ping it
    
  • Ping him at the virtual machines on the same host or vSwitch
    
  • Ping outside our network
    
  • resolve DNS, etc..
    

  I followed some KBs VMware without success, including:

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1003839
  http://KB.VMware.com/selfservice/microsites/search.do?cmd=displayKC & externalId = 1002811 (port security is not enabled)

  -All the VMware tools have been updated to the latest version correct and corresponds to the ESXi host
  -Connected to the service ESXi console, I cannot ping the VM problem by name of host or IP address, but I can ping do not affected by the issue of the OTHER virtual machines.  I can also pings the service console.
  -Connected to the troubled virtual machine itself, I cannot ping other virtual machines, I can't resolve host names, I cannot ping by IP.  The machine virtual CAN ping itself by IP, but not hostname.  I cannot ping other virtual computers on the same virtual switch or network by either IP or host name.  I can't ping the vSwitch network management.
  -All vSwitches are configured in the same way and the same.
  -Notify the switches is set to yes
  -There are a lot of available virtual ports
  -We tried the E1000 and VMXNET virtual cards with no difference.
  -All cards are configured to negotiate, but we tried to force individuals speeds as well as with no difference

  I appreciate your help.  I have problems getting anywhere on this issue with the sellers.

  wkucardinal wrote:

  Still having the issue...

  Sometimes, it might be useful to really check that all uplinks VMNIC for all VLAN does work them. Try this is to create a new portgroup on the vSwitch used by your virtual machines on the host of the first, put a test VM on the portgroup, then go into the NIC teaming policy from the new portgroup and select "Override switch command failover."

  Then down vmnic all except one in unused, then only a single VMNIC is active. Then set the portgroup VLAN to a production of VLAN and try to see if we could ping some expected from the different addresses. If it works, then move VMNIC work until unused and move up to another asset. Try again, and this for all the vmnic. If it works, then you have verified that the configuration of VLANS and other settings are correct on the physical switch in the face of this host ports.

  If several VLANs, repeat the process for all other productions VLAN. Then repeat on the other hosts.

  While that may take some time, occurs if everything is properly configured on the physical switches. When occurs a vMotion virtual machine gets a new "Port code" and is assigned to a new outgoing VMNIC. If there is an error of configuration on one or more physical ports that might seem random, but may still happen on VLAN x on y VMNIC. Given that Port ID policy you use indeed spread randomly VMs on the vmnic these problems may be difficult to diagnose. (Make a disconnection of the VM vNIC gives the virtual machine a new port-ID, which it will move to a new outgoing VMNIC, which might seem to solve the problem.)

• Virtual MACHINE starts automatically after a power outage of the entire site?

  Hello

  We use ESXi 5.5.

  If there is a power for the datacenter failure, ESXi hosts must be restarted when power is resumed.

  We wonder if VMs will be launched automatically to the top?   If not, this means that we must allow the "starting the Virtual Machine / stop option.

  If we put a number of virtual machines in "automatically start", such as VM1, VM2, VM3 on ESXi Server one, VM4 VM5 ESXi Server b.   Virtual machines are migrated between ESXi servers and how they can keep the boot sequence?

  Your opinion is requested.

  Dear Tony,

  I ask you to create a vApp and configure accordingly on your vCenter boot order.

  https://pubs.VMware.com/vSphere-55/index.jsp#com.VMware.vSphere.vm_admin.doc/GUID-0FAB05D4-22F7-4665-B42A-0FA4B360B398.html

  See you soon,.

  Billon Manogaran

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

• Failover storage and a new analysis while running virtual machines?

  The guys from storage must update the firmware on our HP EVA 8000 without. Currently, all my LUN is replicated to another EVA. The guys from storage you want to switch on the other EVA LUN so that they can make updates of the firmware without changing anything. I planned a complete failure of all my virtual machines and hosts so that they can make the switch. Basically stop all virtual machines, stop the hosts, making failover LUNs and then turn everything back.

  My question is there anything that can be done online? We tried it a couple of weeks, and we were hoping to have just the storage team launch the failover and a new analysis on the ESX hosts. All ESX hosts that had run VMs on those LUNS could would not fail on Mon after a new analysis. I have another cluster which can also display these LUNs. They were able to rescan and see the failure on Lun without problem. The only difference is that these other hosts have not the virtual machines running on these LUNs.

  If this working or is this the behavior that we should expect to see? This change in all with vSphere?

  Management has come back and asked why we must take a complete failure and whether it can be avoided in the future.

  > do failover LUNs and then turn everything back. My question is there anything that can be done online?

  Depends on your storage space.  If the LUNS are replicated really, they are up to date and your paths are correct on the ESX AND you use alternating (unfixed) it should work fine.

  This really isn't a function of VM Ware, because technically, storage is really transparent to ESX.  If you can find a valid path to the data, it will use it.  Just to make sure that is not the FIXED path.

• Unexpected shutdown of the virtual machine when compacting

  I have VMWare Server 1.08 on CentOS 5.3 with guests from Windows server 2003. the virtual machine uses 2 GB non-preallocated split files. I'm trying to shrink the virtual machine using VMWare tools. After him "are preparing to shrink" the process is over and I click "Shrink now" after a few minutes (this time varies a little) the virtual machine stops. I have a 2nd vm on this host as well and it stops as well. The host is a Dell 2900 with 2 processors quad core and 32 GB of ram and appx 1 TB of storage in raid 5. I checked memory usage and cpu during the process and memory, the cpu more than 100% for a short periods, but goes back down. Any idea what can be the cause?

  I'm not a person "linux", but am learning.

  I appreciate all help.

  Thank you

  RL

  
  May 15 00:56:16: vmx| SCSI0:0: Command READ(10) took 3.059 seconds (ok)
  May 15 00:56:23: vmx| SCSI0:0: Command READ(10) took 2.254 seconds (ok)
  May 15 00:56:24: vmx| SCSI0:0: Command READ(10) took 3.059 seconds (ok)
  May 15 00:56:24: vmx| SCSI0:0: Command READ(10) took 3.059 seconds (ok)
  

  If you get a lot of lines like that it usually means that either-

  -your physical disks are dead slow

  -the virtual disk has not shrunk Age

  - or is it close to corruption

  Some of these lines are not alarming per se - but if you see thousands of them like in your case that should sound the alarm.

  I'll try to use vmware-vdiskmanager with function r - and just clone the drive for growth in a preallouee.

  ___________________________________

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

• I get an error "the disk hard virtual parent is in a saved state. Discard the saved state or stop the virtual machine and try again. "during the installation of XP mode.

  I have Win7 Pro SP1 x 64.  I downloaded WindowsXPMode_en - us.exe (from Microsoft downloads) and run it.  The installation seems to work OK (I've specified a different location for the parent virtual hard disk file).  Then, installation happening and I provide the information requested (name of user and password for the XP Mode), updates Windows and OK to the issue of sharing.  The installation program then reports the following error:

  The disk hard virtual parent is in a saved state.  Discard the saved state or stop the virtual machine and try again.

  I get the error even if I try manually configure XP Mode (use the Setup Wizard).  I downloaded the installer XPMode (3 times) and reinstalled several times, always with the same result.  If it helps, I can't locate anywhere .vsv file.

  Any idea what's going on?

  Original title: XP Mode Setup error

  Hi smithnr10,

   

   

  You must post your question in the TechNet forums because it caters to an audience of it professionals.

  To do this, you must consult the link-

  http://social.technet.Microsoft.com/forums/en-us/w7itprovirt/threads

   

  Hope this helps!

• Stop the virtual machine

  I'm looking for a script to stop vm...

  Script works fine, but I have a few Questions or details

  $csv = import-csv C:\xxx.csv

  Foreach ($line in $csv)

  {

  Write-Host “====================================================================”

  Write-Host "$line treatment".

  $vminfo = get-view-Id ($line.vm) USER.USER

  Write-Host "checking the VMware Tools on $line... »

  # If we have the VMware tools installed

  If ($vminfo.config.Tools.ToolsVersion - eq 0)

  {

  Write-Host "($line.vm) don't have vmware tools installed, strong power this one.

  # Hard power off.

  Stop-VM ($line.vm)-confirm: $false

  }

  on the other

  {

  write-host "I'll try to stop $vm.

  # Turn off with elegance

  Get - VM ($line.vm) | Stop-VMGuest-confirm: $false | Out-Null

  }

  }

  1. my code below what I'm missing / or hurt?

  $vminfo = get-view-Id ($line.vm) USER.USER

  Write-Host "checking the VMware Tools on $line... »

  2. Tools a lot of combination

  Tools installed - but not running

  tools not install

  Are that both will have to stop-vm?

  3.

  I got a simple code, it will cover the tools stuff?

  $vm = Get-VM
  $vm | where {$_. Comments . State -eq "Running"} | Shutdown-VMGuest -confirm:$false
  $vm | where {$_. Comments . State -eq "NotRunning"} | Stop-VM -Confirm:$false

  
  

  4. I want to stop 50 virtual machines simultaneously, how the

  
  

  Your script seems to be ok.

  When the VMware tools are installed you can do a gracefull shutdown (Stop-VMGuest) within the guest where OS the obligation for the VMware tools.

  The next option is to stop the virtual machine (VM-Stop), with what would be the power button on a physical computer.

  No phasing out of the BONES and a potential risk on the corruption of the OS.

  With switch RunAsync that the cmdlet returns immediately, it will not wait until the underlying vSphere method is complete.

  The method will continue, but in the background.

  You should check these tasks to background (Get-task), to monitor the successful completion.

  To manage VMS in batches of 25 and wait 60 seconds between batches, you could do something like that

  $vms = get - VM

  $step = 25

  $start = 0

  for ($loop = 0; $loop - the ([math]: ceiling ($vms.)) Step Count / $)-1); $loop ++) {}

  $vms [$start... ($Start+$Step-1)] | where {$_.} Guest.State - eq "Running"} | Stop-VMGuest-confirm: $false - RunAsync

  $vms [$start... ($Start+$Step-1)] | where {$_.} Guest.State - eq "Keep"} | Stop-VM-confirm: $false - RunAsync

  sleep 60

  $start += $step

  }

• Accidentally, I put my virtual machine - Windows 7 - 4 MB RAM, and now I can't load and stop it!

  Accidentally, I put my virtual machine - Windows 7 - 4 MB RAM, and now I can't load and stop it!
  My Windows 7 virtual is stuck in start mode of Windows, but not I can't start it, nor can I stop to change the RAM to return to normal. Help! What can I do now?

  I use Macbook Air if it is useful and WM ware Fusion 6.0.3

  Hi Requiem88,

  Just to be clear, you press the Option key on the keyboard key then went in the Virtual Machine menu at the top of the screen and choose Force Shut Down who?  Looks like you force quit in the menu Apple have rather choose.  Force quit will put end to VMware Fusion, while the option Force stop menu stop permanently from Windows itself.

  See you soon,.

  --

  Darius

• Stop/start multiple virtual machines with names created automatically

  Hi all

  in my test environment, I want to stop or start multiple virtual machines via the script.

  Their name is always like this:

  'vm-100-qa', 'vm-101-qa","vm-100-qa","vm-102-qa '...

  Now I would like to just stop every VM 'vm-140-QA' to 'vm-160-qa.

  I created a table "$a = 140.160", but I don't know how to implement this in a script 'Shutdown-VMGuest-comments '.... »

  Sorry for this stupid question. I am a beginner absolute powershell.

  Thank you very much in advance,

  Petrie

  You can do something like this

  140..160 | %{   Shutdown-VMGuest -VM "vm-$_-qa"}
  

• vCenter converter 5.1 - just P2V to esxi 5.1 but stop virtual machine by iteself

  I P2V a machine using vCenter converter 5.1 and migrated to 5.1 ESXi host. If conversion/migration is finished without error. Now when I turn on the computer, virtual it stops up to the login screen and it goes on and on. Not able to understand what is happening. I veried resources assigned these looks good.

  Some successful how to enter safe mode. UPS service was guilty. Disabled it and also default actions has changed for this service of "Non-action" for all three incidents.

  No problems now and new virtual machine works very well without any problem

• The virtual machine that wouldn't die - or - how the % ^ $^ % $ do I stop a suspended virtual machine?

  Fusion: v4.1.4

  VM: Windows XP SP3

  OK, so I copied on my old XP VM, initially created on Workstation 5, on my Mac. It starts very well and I've added merge tools without problem. Everything works fine. BUT if I power down using start-> computer-> Turn Off Guest, it will just into suspend mode. I have a--suspend try virtual machine-> Force Shut Down and it just goes back to the standby mode. I try to start-> turn off the computer-> restart followed by start-> computer-> Turn Off and same thing. Virtual machine-> Force restart following start-> computer-> Turn Off the same results. So nothing I've tried will turn off what I can change the settings.

  I think what happened is, I had initially set the preferences of the merger to 'Suspend the virtual machine', powered on virtual machine and then he changed it to "Turn off the virtual machine" and then tried to stop.

  An OS X Lion VM, I have no problem turns off.

  What can I do, short removing the cursed thing and start over? And if I do that I'll have the same problem I think.

  Administer a test... While the virtual machine is stopped, manually edit the .vmx placing a # configuration file to: snapshot.action = "autoRevert"

  It is a parameter that is available from the VMware Workstation user interface but not the INTERFACE of VMware Fusion and I believe that it is perhaps the origin of the problem.

• Start and stop Virtual Machines with the system

  Hello

  In a server cluster @vcenter HA/DRS 5.1, I enabled start and stop virtual machines with the system option but after I checked two days later, he is off again somehow. What makes this option off? I had a power failure in the datacenter. vCenter server has not been upward. I started all of the ESXi servers manually then went all VMs account is declining. I want that they start automatically when server ESXi upward.

  Thanks in advance,

  Thank you. This option is more valid than if the hosts are part of an HA Cluster license. I suspect that you configured through the traditional vSphere Client and that it is a bug with this client. If you try with the new vSphere Web Client, you will find a notice that it is disabled and there is no button "Edit".

  Concerning