Impression of virtual machine problem

Similar Questions

• VMotion and new Virtual Machine problems

  Hello

  Got a VI2 farm with 3 ESX servers.

  1 of the ESX servers play big time... when I try to VMotion VM him another 2 or create a new virtual machine, it gives the same error message ' reason: could not start the operation of long duration for the server VM.» Reason: Failed to get the directory config (basename = servername"

  Can I migrate from the problem for the other 2 ESX Server but not for her. Cold cant migrate either.

  I checked the logs, rebooted and rebooted vCenter Agent. Still no luck.

  Any help appriciated!

  This thread help me?

  Check this one, too.

  Basically, it seems that the system has trouble finding / access to one or more of the files associated with the virtual machine. Given that you can migrate to and not the host, I suspect it's the permissions problem reported in the first thread.

  Ken Cline

  VMware vExpert 2009

  VMware communities user moderator

  Blogs about: http://KensVirtualReality.wordpress.com/

• Problem migrating a virtual machine

  Hello!

  I have a problem when I try to migrate a virtual machine to the concrete only two hosts. I have no problem in other guests in my infrastructure. When I try to start this operation I get the following error message: "cannot migrate from esx1.domain.com to esx2.domain.com: the host CPU is incompatible with the function CPU requirementes of the virtual machine; problem detected the CPUID level 0 x 80000001 register edx.

  With other virtual machines, I have no problem and I can migrate from any host to any of them.

  Hi Eric,.

  Please check this link below:

  http://KB.VMware.com/selfservice/viewContent.do?externalId=1001131&sliceId=1

  Seems to be the answer to your problems.

  Please give feedback if this solves the problem

  Concerning

  If you find this or any other answer useful please consider giving points by checking the answer useful or appropriate.

• Problem with Migration hot virtual machines Hyper-V

  Dear support

  I am facing problem in Live Migration of Virtual Machine in Windows 2012 of Hyper-V R2 cluster. Here are the details for my current setup.

  Two windows 2012 R2 Datacenter even care Server (HV01 and HV02) both in cluster

  A Virtual Machine created the Volume share of Cluster (c:\Cluster storage\...)

  A network adapter dedicated to the management of server-> 10.0.1.11 (HV01) and 10.0.1.13 (HV02)

  A network card dedicated to Hyper v Virtual Machines-> 10.0.1.12 (HV01) and 10.0.1.14 (HV02) and allow networking option is disabled.

  A network card for the heart beats-> 10.0.20.1 (HV01) and 10.0.20.2 (HV02)

  A network card dedicated for Live Migration-> 10.10.10.50 (HV01) and 10.10.10.51 (HV02) and chosen to be used only for the live migration fails on cluster network settings

  I added the Virtual Machine Cluster Failover successfully without error or warning. When I do a quick migration his works fine but when I do live migration his error giving 21502.

  Please update what's wrong with my setup

  Hello

  Post your question in the TechNet Server Forums, as your question kindly is beyond the scope of these Forums.

  http://social.technet.Microsoft.com/forums/WindowsServer/en-us/home?category=WindowsServer

  See you soon.

• I need a new Image of XP because my expired original but when I downloaded it again, the new XP said its has expired, too! I thougt of caching problem of virtual machine manager, but I'm not sure.

  VHD expired

  http://t.co/exzliimb - where I downloaded the XP VHD of

  http://t.co/8vhbKuzu - error screenshot

  I need a new Image of XP because my expired original but when I downloaded it again, the new XP said its has expired, too! I thougt of caching problem of virtual machine manager, but I'm not sure. I deleted all the VHDs before you download again. Any ideas?

  Hello

  Your Windows XP question is more complex than what is generally answered in the Microsoft Answers forums. It is better suited for the IT Pro TechNet public. Please post your question in the Technet Forum. You can follow the link to your question:

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

  Hope this information helps.

• Have problems connecting to the Internet after the virtual machine has crashed.

  Original title: problems sudden ethernet

  Hello

  I'm having a problem with connecting my computer custom-made. I was with my virtual machine to run an android phone. It connected via a second wireless connection (I don't know much I just let it work). It crashed my computer and when I rebooted I had no internet.

  It would also be useful to mention that I recently had a BSOD because of the virtual Manager and a driver, but I solved it.

  He said that no connection is available, and there is a red cross.

  So far I have tried:

  A second ethernet cable - nothing. (The two wires green on the end of the PC and the end of the router).

  Updated windows, but he can't because of the lack of connection.

  System Restore, but it says "Windows has detected corruption of system files on Local disk (C .)» You should check the drive for errors before you can restore it.

  sfc/scannow, but which translates "could not Windows Resource Protection start the repair service".

  I have also reinstalled the drivers for my cable ethernet twice and nothing.

  If more information is needed please ask. Thanks in advance.

  Hello

  In Device Manager, expand network adapters, right click on the Ethernet device and update the driver.  Otherwise, identify the manufacturer, go to their website and download the latest driver.

• I have a problem with the password on the virtual machine.

  Original title: passwords & Windows 7 virtual machines

  Hello

  I am running windows 7 pro 32 bit, with a windows XP virtual to develop existing software.

  The hosts & VM connect to a file on the network server. The file server is running windows XP, the network is a simple working group. I've manually created a limited user on the file server with the same name and password as my logon to windows 7.

  Today, I changed my password to connect to windows 7, which I am not as often as the security people recommend that I do. I changed the password on the file server to synchronize and also the password on the virtual computer.

  The virtual machine is maintaining however, somewhere the old password, which crashes, and I get the logon screen. If I enter the new password it connects then. I went into the settings of the VPC and delete the credentials saved, without effect. I removed "enable on startup" of integration features, also without effect.

  So I get the password in the VPC, but then I have to enter the password to access the network share. Or I can enter the password each time I start the virtual machine. The second is less painful, but still annoying.

  Any thoughts?

  Hello

  Thanks for posting in the Microsoft Community.

  According to the description, it looks like you are facing a problem with windows Virtual PC.

  The question you posted would be better suited in the TechNet Forums; We recommend that you post your question in the TechNet Forums to get help:

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

  If you need Windows guru, do not hesitate to post your questions and we will be happy to help you.

• Problems of migration of a virtual machine

  Hello

  I have a problem when you try to migrate a virtual machine to an ESXi to and another ESXi. I migrate from power off State. That's what I get:

  

  I have 2 ESXi host with vCenter device.

  When I go to the preview of the hosts, in the first (it is the destination of the migration), I have no CPU usage and memory. There is something wrong because I have the vCenter and other Linux machine powered:

  

  The other host (this is the source of the migration) looks good:

  

  How could I solve this problem?

  I'd really appreciate your help.

  Best regards.

  Thanks for the reply.

  I reboot the host and now I can migrate and CPU and memory info is correct.

  Kind regards.

• ORA-12560: TNS:protocol adapter error. Virtual MACHINE works on old MBP and Win7 but not on new MBP [mid 2015 retina], speed or network problem?

  We strive to use our VM on the new retina MBP (mid-2015) with MacOS X 10.11 (El Capitan) but we had a problem starting from Oracle. If we first converted our ESX VM but once on the Mac laptop Oracle (v12.1.0.1.0 on WIN2012R2) does not open the database, error;

  ORA-12560: TNS:protocol adapter error

  Does not change us any setting on the virtual machine itself so services work fine. Network has set the IP with host only. Tried with Fusion 7.1 & Fusion 8.0.2 new Mac with nothing doesn't. Also with the different versions of the VM tools. Tried to remove the NIC in Fusion and recreate, don't sucses.

  Funny enough the same virtual machine starts fine on PC (workstation 10.3.0 & Win7), MBP beginning 2011 (Fusion 7 & Mac 10.10) or ESX itself for Oracle opens the database!

  That's why we think in the direction of the new MBP specific? speed or network issue? Ring the bells?

  
  

  Help appreciated!

  Bottom line, this is a problem of Oracle who dislikes the MBP on a virtual machine.

  for reference;

  Virtual MACHINE works very well on all platforms, but not on the latest MacBook Pro (retina, 15 inch, mid-2015). So, when you try to use sqlplus you might get the error that there is no such thing as SID. Earphone works very well, but the DB process does not record with earphone or work correctly also. But the process is running and a SID tnsping returns an OK. This isn't a problem of configuration Oracle as the VM and DB works well from the moment where you run the virtual machine on a PC or an old MBP. Either way, Virtualbox has the same problem so not a problem of Fusion.

  I will record a deal with Oracle but I doubt that it is corrected.

• Some virtual machines have intermittent network connectivity problems and rest work correctly.

  Some virtual machines have intermittent network connectivity problems and rest work correctly. The VMs are in the same group of port and on a 4-node cluster. Physical network interface cards are appearing in vsphere client

  Please confirm if the issue has been resolved after you complete the steps.

• Connectivity problem of virtual machines the host is rebooted.

  We restarted our esxi host and after reboot, we receive questions, with the connectivity of virtual machines hosted on that particular esxi only.

  The problem is that some virtual machines communicate on the network and some are not.

  There are two hosts in the cluster, if move us the virtual machines on another host, virtual machines are running well.

  The host has the same configuration with respect to the physical networking and configuration of virtual networking is concerned.

  ESXi version: 4.1

  You mentioned that host network configuration and good host network configuration problem is the same.

  Issues appeared after reboot the host, and until the battery has been replaced.

  I guess that something is wrong at the physical end itself.

  Is that possible, that you can stop the host again and obtain reinstalled network and power it turn it on again and test it.

  Because when the battery change is done server is put out of the rack, so I'm assuming that n/w card were not seated correctly. I have faced this kind of problem once and I did the same thing and things worked well for me.

• Problema ao melting uma VM (problem building a virtual machine)

  Good afternoon a todos.

  (Hey),

  Estou com um problema no VMWare em had I can not melting uma VM. Ocorre a mensagem "Unable to access file < unspecified file name > because it is locked ':

  I have a problem in VMWare où I can not build a virtual machine. Occurs le message " Cannot access the file <not specified filename > because it is " locked":

  

  POIS bem, I tried melting a Máquina an outra forma, that faith: fazer um snapshot da VM, remover instant esse e depois mover para outro DataStore. Led a mensagem erro abaixo:

  Well, I tried to consolidate the machine otherwise, which was: take a snapshot of the VM, remove this snapshot and then move to another data store. Le the error message below has occurred:

  

  Inclusive isso occurred depois o Avamar estava um doing backup, mas houve uma is na rede, e o processo faith backup interrompido. O Quebec EU posso fazer nesse caso?

  Same as has occurred after the Avamar was a backup, but there was a failure of network and the backup process has been interrupted. What I can in this case?

  Obrigado desde ja,

  Thank you

  Otimo... vai ser color some proxy that esta lockando o seu servidor vmdk... para saber qual, nao is for many, acesse as configuracoes da Máquina virtual proxy, locate o referring disco seleciando disco, a virtual com problema e o LFR machine an option 'remove from Virtual Machine", according an imagem abaixo:

  

• VCo workflow to clone a virtual machine of centos. Network interface problem

  Hello

  I use vco workflows to clone a virtual machine of vcenter. The virtual machine is running centos 6.0. When cloning is complete. I see the network eth0 and eth1 interfaces set correctly the static gateway ip and address information I provided. I deleted the 70 - persistent - net .rules on the basic vm form which I clone. So, I get the correct interface names. But when vm powers on and I run "ifconfig eth0" I don't see the IP address of this interface has all the details.  same for the other interface also.

  But if I do a system restart network without changes to networking and then do an ifconfig I see the IP with the previous information.   I don't know why the service network restart is necessary so that he can recognize the ip address.

  Any ideas what I could do wrong. or to avoid this manual step of the execution of the service network restart command on the creation of the vm.

  Thank you

  Kiran

  Yes I'm restarting after after the application of customization.

  Has been able to solve the problem... In CentOS, the network service does not work by default. This is why it does not have network interfaces at startup. So now the machine instant, I started the network services and stop the Network Manager service

  using chkconfig network on

  chkconfig NetworkManager off

  and then cloned from this virtual machine... and apply the customization settings. during the start now it shows the interfaces properly without needing a service restart

• Problem with New-OSCustomizationSpec during the deployment of a new virtual machine

  Hi all, I'm having a problem trying to deploy a VM from a script.  I started with this thread LucD code: https://communities.vmware.com/message/2220479#2220479. I'll start with the Basic code that I use:

  $myCluster = Get-Cluster -Name "Cluster1" | Get-ResourcePool "Test"
  $myTemplate = Get-Template -Name "Win 2008 R2 SP1 Std - Powershell"
  $myDatastoreCluster = Get-DatastoreCluster -Name "DataStoreCluster1"
  $myVM = "Adam12"
  $IP = "10.0.0.1"
  $SubnetMask = "255.255.255.0"
  $Gateway = "10.0.0.254"
  $DNS = "10.0.0.10","10.0.0.11"
  
  Get-OSCustomizationSpec -Name "Server 2008 R2 Standard - Powershell" | New-OSCustomizationSpec -Name temp -Type NonPersistent
  Get-OSCustomizationSpec -Name temp | Get-OSCustomizationNicMapping | Set-OSCustomizationNicMapping -IpMode UseStaticIP -IpAddress $IP -SubnetMask $SubnetMask -DefaultGateway $Gateway -Dns $DNS
  
  New-VM -Name $myVM -Location "Folder1" -Template $myTemplate -Datastore $myDatastoreCluster -ResourcePool $myCluster -OSCustomizationSpec temp
  
  

  Very simple.  Now I can use the New - VM above command directly against the template and the OSCustomizationSpec, and that works just fine (and of course manually provisioning works as well).  However, as soon as I try to make a new one and use the 'temp' specification, the virtual machine never gets to the name change process and I ended up get an error oobe indicating "impossible Windows analyze or process the unattend answer file."  I noticed in the Summary tab in vSphere that the IP address is correct on this basis, but the name of the server never changes the name of the original model.

  I stripped down and got out of line 10 above (static IP address setting) and just left it to DHCP and it doesn't have the same way.  Any ideas on what could be the cause?  Everything else works, it puts the virtual machine in the correct folder, the data store right pole and the pole of the right.

  As a bonus question: after all what I have read, VM storage profiles are not accessible via PowerCLI.  This changed at all?  It would be good to set the profile in a script instead of having to do it manually after the fact.  Thank you!

  Adam

  Answering my own post here...

  Seems that it works if I create the New OsCustomizationSpec with - Type persistent instead of NonPersistent.  I'm on vSphere 5.0 and 5.0 with PowerCLI 5.1 ESXi, if my guess is that those of you who have found this works are on vSphere 5.1.

  I'm just starting my big 5.5 update, so I'll re - visit it at that time.  For now, I'll just to create a random variable of 8 characters for the temporary custspec and remove it when the virtual machine is deployed.  Seems to work fine and I can have several builders of VMs at various locations without stepping on each other.

• Problem with initialization virtual machine OlioDB

  Hello

  I have been using VMmark 2.1 six months spent for our performance appraisals. I recently started seeing the following error message when the harness trying to boot the virtual machine OlioDB0:

  Stafcmd: Tile0: FS copy the file: ConfigServer_OLIOjspDB.sh failed with RC = 22, STARFResult = STAFConnectionWriteUInt: error writing to the socket: send() RC = 10054:22

  I can ping the virtual computer, I can also ping using STAF (oliodb0 STAF-> pong ping ping).

  If I change the WORKLOADLIST in the vmmark2.config file so that it includes OlioDB, initialization is going through and I can see the virtual machine making initialization. But when WORKLOADLIST revert to the original, I get the above error message. I would appreciate your help to try to solve the problem.

  Thank you

  Amin

  Sorry, my apologies, I understood the question. I had another copy of the same virtual machine running on a separate server, which caused a conflict of IP address with the main VM that the test sought to initialize. I got rid of the copy and everything started to work very well.