Random virtual machines after vMotion and Storage vMotion network loss

Similar Questions

• vROPs - you can create a report to show when a virtual machine has changed and what has changed?

  I can't currently developing a report/view that can show me what I'm looking for.  I thought since it's related capabilities vROPs can keep track.  Is there a way to see the when a virtual machine has changed and what has changed?  Looking mainly vdisk, vCPU or vRAM.

  Thanks for help or suggestions.

  Hi newbski1,

  There are few things you can try to help him with this.

  1. the events view shows you changes in resources, it is not terribly detailed, but it will help

  2. depending on your version, you can also view in Configuration Manager that is part of the vRO suite that will show you the changes to configurations.

  See you soon

  @iiToby

• Pre-built virtual machine with OBIEE and APEX

  Hi all
  
  I searched for a virtual machine with OBIEE and APEX pre-installed, but I can't find it... or information messages on this subject. Does anyone know if y at - it a selection of pre-designed developer programs VM with these two tools?
  I currently have the "database App Development VM' with APEX in there, but I can't understand how to install OBIEE inside.
  
  Any help will be appreciated.
  
  Please, if this is not the right category where I should ask the question, let me know and I'll move it.
  
  Thank you.
  Elena.

  PL see deployment guide in the link above - the model of computer virtual includes version of database 11.2.0.3, which should be the APEX installed by default in it. If this isn't the case, it will be much easier to install the APEX in the VM OBIEE.

  For sharing files between the host and the guest, pl see the Virtualbox documentation - http://www.virtualbox.org/manual/ch04.html#sharedfolders

  HTH
  Srini

• Network down frequently on a virtual machine after the upgrade of computers host and vmware to win 10

  Dear all,

  A week ago, I upgraded both my two machines VMWare Win 7 to win 10, as well as the host operating system. also from 7 to 10.

  Now once every 1 or 2 days, one or both the two vmwares aura an esclamation mark on the network status icon in the lower right corner and West no connection.

  The host operating system is NOT having any problems with the network.

  The solution is to disable and reactive the adapter to virtual machines, or repair of running Network Diagnostics where she'll tell me that it s has reinstated the connection to the bridge. But obviously I´d prefer the VM´s to be on the internet 24/7 without my intervention.

  I have another computer on the same router on which I did the same thing, but with this I m not having these problems. A different and not connected equipment via the VPN running on the host OS, which is the case with the machine that s had questions.

  But even once, the host operating system is not having issues, the two VM´s aren´t always the two to have this problem, and this never happened when he was all Win 7.

  I ve disabled some nights windows defender analysis and TCP/IP V6, but neither helped.

  Want to see some of the information from the last network diagnostics / repair or some log file, or you already know what would be the solution to my problem?

  Thanks in advance!

  Best regards

  Jazzl

  Well, I thought that a vm was having this problem a lot more often than the other, so I looked for error messages in windows journal, showing that the network problem - have to with DHCP btw - always spent 2 minutes after an event regarding slui.exe, not found on the other machine.

  What I also noticed was that the problematic vm had lost its activation of windows with the upgrade to win 10 (win 10 has limits to how much the same license can be run as virtual machines), is is not the case for the more successful one.

  Then I copied the good machine, which contains the same as the other, changed mac and uuid and now it s showing that enabled, no problem so far.

• What is the best way to restore virtual machines after a refresh of the server

  Hi all

  First time poster here. A group of people at my work have their own VMWare environment which they install later. It has 3 virtual machines running on it, and they want to set up a fourth. Unfortunately the new machine, they want to put in place is going to be almost 1 TB in size, and they initially setup the VMFS datastore to 1 MB, which means that a machine can be as large as 256GB.

  Research, it seems that there is absolutely no way to work around this problem, except to redo the data store. Is this correct? If this is the case, I was looking at a way to save the three current machines and to reload them after it is updated. A way that I thought was to go browse the data store and copy all the files on my local machine to the virtual machine (.nvram, hard, .vmx etx... all the files), wipeout and redo the ESXi host with the correct setting of data store, build the machines VMS in vSphere, and then replace the files with those copied. This works perfectly? I don't see a lot of information out there about it and I want to make sure that I have not to spoil the VMs. This environment consists of 1 ESXi host with all the local storage (2 TB).

  Also, if anyone knows a better way to do this, please feel free to give your comments. I would really appreciate it.

  Thank you

  Hello

  Welcome to the community!

  Research, it seems that there is absolutely no way to work around this problem, except to redo the data store. Is this correct?

  Yes, unfortunately there no way to change the block size of the datastore to vmfs without reformatting.

  If this is the case, I was looking at a way to save the three current machines and to reload them after it is updated. A way that I thought was to go browse the data store and copy all the files on my local machine to the virtual machine (.nvram, hard, .vmx etx... all the files), wipeout and redo the ESXi host with the correct setting of data store, build the machines VMS in vSphere, and then replace the files with those copied. This works perfectly? I have

  Yes, it will work. You have just to copy all files in this VMFS datastore to a place safe and download once the block size has increased. Once the download is complete, navigate to the virtual machine, the virtual machine folder right click and save the VMX.

  You can find the steps to change the size of the block VMFS in this KB. VMware KB: block the size of a VMFS data store limitations

• Drops after vMotion network

  Hi all

  I have a problem with vMotion in vSphere and I was wondering if someone could help.

  I currently have 2 hosts which were entirely patches. I have 2 vSwitches. One for management (SC and VMK) and the other for the Virtual Machine. Each vSwtich has 2 adapters physical 1000FDX assigned. The cluster has active HA but DRS not activated and I don't use of FT.

  When I vMotion machines among hosts I loose the customary ping of the virtual machine, but also intermittently the VM gets disconnected for about 2-3 minutes. Probably to about 30% of my vMotions not this way. During this period, you cannot ping the server or anything from the ping server.

  I tried setting the port speed on the network cards on the vSwitch to 1000FDX, tried different vNIC on virtual machines (VMXNET2 and VMXNET3) but still the same problem, but not all the time and it doesn't seem to follow all of the grounds.

  At any come across this before, and how can I solve this problem.

  John

  Could be a problem with your physical switches?

  Can you try to enable RSTP or FastPort?

  You have a single switch or more?

  André

• The list of virtual machines, data warehouses and the folder name by cluster

  
  Hello!!  I hope someone can help me with a PowerCLI script that can pull the info from the object into a file, txt or csv.  In order to get our environment cleaned before our next year Dr. with MRS, I want a list showing each VM and the data store (s) in that it is the name of the folder in the virtual computers view and models.  We keep our VMs organized by creating folder names that correspond to the application running on the virtual machine.  I mention a SRM than last year because our protected groups matched groups of our table of 3PAR Rcopy.  However, we have added over 200 new virtual machines from this era and the members of my team essentially placed these new virtual machines on the first available data store that had enough free space.  Unfortunately, we are not using storage profiles... it's scheduled for next year.

  Information extracted would look like the following:

  ServerName Datastore folder name

  Server1 LUN0 ActiveDirectory

  Server2 LUN0 ActiveDirectory

  Serveur3 LUN1 ActiveDirectory

  Server4 LUN3 Argo

  Server5 LUN7 Argo

  LUN6 Lockbox Server6

  LUN5 Lockbox Server7

  Serveur8 LUN9 Citrix

  etc...

  Any help with the extraction of this info from vCenter would be greatly appreciated.

  Thank you

  Charles

  You can redirect the results to a CSV file, for example

  Get-VM |Select Name,@{N="Datastore";E={[string]::Join(',',(Get-Datastore -Id $_.DatastoreIdList | Select -ExpandProperty Name))}},@{N="Folder";E={$_.Folder.Name}} |Export-Csv C:\report.csv -NoTypeInformation -UseCulture
  

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

• can not power on virtual machine after activating the VR

  This is the error I get after activation of the replication of Vsphere and turn on/off the machine. I say feeding because allowing the VR blocks virtual machine. If I disable the replication, the machine starts correctly. The Bayt thing is that I can reproduce a 80 GB drive on this machine, but the minute I have activate the duplication of a 2 TB drive, I have this problem.

  Any idea?

  "An error was received from the ESX host turning on VM Novastor.
  Unable to start the virtual machine.
  Power DevicePowerOn module has failed.
  Unable to create the virtual SCSI device for scsi0:1, ' / vmfs/volumes/4ffda1f1-22a39f8e-bd7d-e61f13f6d8ff/Novastor/Novastor.vmdk'
  Impossible to attach the 'hbr_filter' filter to scsi0:1: limit exceeded (195887110). "

  I guess that's under the limit of 2032GB of Vsphere replication then why make this mistake when I enable replication for this disc?

  2 TB is equal to 2 048 GB that exceeds the maximum size supported 2 032 GB (= to 1,984375).

  André

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

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

• Black screen on all virtual machines after software update

  I'm running 3.1.2 Fusion on a Mac Pro, which is running 10.6.7 and after a recent update all my virtual machines reach black screens when they run. If I suspend, I can see the screen, and it seems that everything works normally, but when I take the screen becomes black. I don't think that it is really a display problem: I can not ping the VM when it runs.

  The same thing happens when I create a new virtual machine, Windows or Ubuntu. Looking at the VM Ubuntu after that I created a new and he suspended definitely seemed to be running: frozen screen was part of the Ubuntu installation, so he had certainly run pending. The update of software in question was not an update of the OS from memory, I think I kept the machine more up-to-date than that, but I can't be sure.

  Any help is very appreciated, that completely prevent me from using VMware.

  Thank you very much!

  Heath

  Have you tried to uninstall/reinstall VMware Fusion to try to see which solves the problem?

• Random virtual machines stop...

  Hello

  We had a problem today with ESXi4 where, all the virtual machines have been shut down randomly.

  I checked the event log in vSphere Client, but it seems to have been cleared out.

  Restarted the server and my virtual machines came back well.

  I wonder if the machine might have been hacked? I've attached a screenshot of the events tab in vSphere.

  TIA,

  Mitch

  Welcome to the Forums - my reading of your attachment looks like a network problem - did nothing happen on your network? Is this already happened? It's a stand-alone ESXi host?

  If you find this or any other answer useful please consider awarding points marking the answer correct or useful

• Update hardware VM virtual machine running vCenter and VUM

  Curious to know how to upgrade hardware VM (from 4 to 7) of a computer virtual running vCenter 4 and the Update Manager.

  you will have to do it manually.  Connect to the host ESX (i) in which the virtual machine is hosted on, arrested, upgraded and on material (after the VMware Tools) power.