Apps Media

Some VMs are missing after Xenserver failure Without enabled HA feature there is no mechanism enabled which checks if the host which went down had any VMs running at the time of the failure. There is no mechanism which updates the database with the informatio?n that the VMs which were running on the failing host should be marked as halted after the crash. So, when you do not have the possibilit?y to enable HA you can do the following to make the VMs available in XenCenter again: 1. Locate the VMs which were running on the failed host with the following command: xe vm-list resident-o?n=<UUID of the XenServer host> --multiple You can determine the UUID of the host which failed by running the `xe host-list`? command. 2. reset the power status of the VMs to halted using the following command: xe vm-reset-p?owerstate vm=<Nam?e of VM received from the command in step 1> force=true? (repeat this step for all VMs which were running on the failed host) Once you reset the powerstate?...

SOLUTION Vagrant Plugin Installation failure in Windows 8 1 OS                                              The problem exist in ruby for windows ... it has some issues related to space in folder names and by default vagrant home is the C:/users/your user name/.vagrant.d all you need to do is to set the environment variable VAGRANT_HOME to something like C:/Vagrant/Home .... so to do it first make the folder Vagrant in C drive and then make another folder in Vagrant directory i.e. Home ... So you have something like this C:/Vagrant/Home                                                                                    After making the folder run the following comma...