VMDK Recovery Tool (ESX 3.5 Update 3) (1007243) Solution For this tool to work, you must keep a current block list of your virtual machines. You cannot recover VMDK files for which you do not have a block list. To create a block list using the VMDK Recovery Tool:Launch the VMDK Recovery Tool, log in to the service console as root and run the command: # vmfs-undelete.Select option [b] to list all virtual machines registered to the host.To create the block list, perform one of these options:Select [99] to back up a vmdk block list of all virtual machines.OrSelect a virtual machine ID from the list to back up a specific virtual machine.During block list creation, the tool prompts you to specify the filename to backup the data. You can either give an absolute path (a new file is created by the tool) or it will be saved in the current working directory. Sample session:[root@esx11]# vmfs-undelete ######################################################### VMFS Data Re...

MirantisOpenStack-4.0.iso的下载地址：http://pan.baidu.com/s/1dDsuzXf。下载之后使用虚拟机或者物理机安装都可以，我使用的是vmware。需要把NAT的自动分配ip功能关闭点击下载安装文档

RDO quickstart: Proof of concept for single nodeIf you want to spin up a proof of concept cloud on one node, this is theplace to be. You will be able to add more nodes to your OpenStack cloud later, if you choose.If you are looking for instructions to deploy a production cloud,possibly with HA, see the TripleO Quickstart.If you just want to try it out without installing anything, check out TryStack.These instructions are to install the current Liberty release.Summary for the impatientMake sure your /etc/environment is populated:LANG=en_US.utf-8 LC_ALL=en_US.utf-8 If your system meets all the prerequisites mentioned below, proceed with running the following commands:$ sudo yum install -y https://www.rdoproject.org/repos/rdo-release.rpm $ sudo yum update -y $ sudo yum install -y openstack-packstack $ packstack --allinone Step 0: PrerequisitesSoftwareRed Hat Enterprise Linux (RHEL) 7 is the minimum recommended version, or the equivalent version of one of the RHEL-based Linux distri...

RedHat Linux 4 Kernel Panic not syncing kill init no volume groups foundI just imaged my RHEL 4 system that was running on a Dell Poweredge 2950 server using Acronis software and I restored the image to a VmWare virtual machine.   Dell Poweredge 2950 - RAID 5I got it fixed: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1002402 http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004797 Virtual machine does not boot after being converted from a physical Red Hat machine Details •      A converted physic...

The P2V conversion of Debian OS is not as straight forward as CentOS where you just need to click Next, Next,...Finished!!!...The conversion process is same for both, but the Debian conversion may fail during the final stages of conversion.IssueWhile doing P2V on aDebian/Ubuntu OS, the process fails at 99%.Under log highlights, you could see the error"Error: Unable to reconfigure the destination virtual machine". Under the conversion status, you will find the error:FAILED: Anerror occurred during the conversion: 'GrubInstaller::InstallGrub:/usr/lib/vmware-converter/installGrub.sh failed with return code: 127, andmessage: Installing GRUB1 on (hd0)... /vmware-updateGrub.sh: 59: grub:not foundError installing GRUB Error running vmware-updateGrub.sh through chroot into/mnt/p2v-src-root '        If VMware conversionhas failed at 99%, that doesn't mean theconversion has failed completely. The copy of the physical machine will already be in thedestination when t...

How to P2V a Linux host in vSphere 4.0 Occasionally, you will need to P2V a physical Linux machine that doesn’t quite match up with the accepted configuration defaults for vSphere — particularly, a distribution (or even a fork of a distribution) that’s not 100% supported. For example, I recently had to P2V a CentOS 2.1 VM, which you would assume would appear to vSphere as a Red Hat Enterprise Linux 2.1 VM, seeing as the two distributions are binary-compatible. However, I assumed that, and it turned out I was wrong. :-)Given that CentOS is binary-compatible with RHEL, it’s very possible that you could simply edit /etc/redhat-release on the CentOS box to mirror what’s on a RHEL box and be done with it. (I haven’t tried, but if anyone wants me to, just holler.) Out of the box, because VMware Converter can’t figure out what distribution you’re using, it can’t/won’t/doesn’t install the correct drivers when you P2V your old, busted Linux host. So, when you boot up the VM, yo...

虚拟机在从物理 Red Hat 计算机转换后不引导 (2093497) Symptoms 免责声明：本文为 Virtual machine does not boot after being converted from a physical Red Hat machine (1002402) 的翻译版本。尽管我们会不断努力为本文提供最佳翻译版本，但本地化的内容可能会过时。有关最新内容，请参见英文版本。 Resolution 出现此问题的原因是，操作系统的 ramdisk 映像不包含适用于为虚拟机配置的虚拟 SCSI 适配器的驱动程序或模块。这些模块之所以不在 ramdisk 映像中，是因为该映像最初是在不使用此硬件的系统中创建的。必须将现有 ramdisk 映像替换为包含正确驱动程序的 ramdisk 映像。Converter 3.0.x 不支持 Linux 操作系统热克隆，也不支持对新虚拟硬件生成的虚拟机进行配置。仅支持不进行任何配置的冷克隆。而 vCenter Converter 4.0 支持某些 Linux 操作系统的热克隆和配置，包括 Red Hat。有关支持版本的列表，请参阅相关手册。验证下面每个故障排除步骤是否适合您的环境。每个步骤提供相关说明或文档链接，用于消除可能的原因和采取必要的补救措施。这些步骤按照最合适的顺序排序，以隔离问题并确定正确的解决方法。请勿跳过任何一个步骤。 注意： 如果您在以下任...

Vmware P2V conversion failed with showing grub prompt  We tried to convert one of our physical machine running fedora15, using vmware tools. It started and failed exactly at 99% showing the following error“An error occured during the conversion GrubInstaller:InstallGrub: /usr/lib/vmware-converter/installGrub.sh failed with return code:1, and message: FATAL: kernel too old Error running vmware-updateGrub.sh through chroot into /mnt/p2v-src-root”Solution1. Boot the virtual machine with the fedora15 DVD and select the ‘rescue’ option.2. Once it boots chroot the /mnt/sysimage.3. While giving fdsik -l, im getting the following error“cannot open /proc/partitions”Also, mount too get some errors like unable to read etc., So exited the /mnt/sysimage by “exit” command4. Now, I gave the followingmount -o bind /proc /mnt/sysimagemount -o bind /dev /mnt/sysimageIf we didn’t mount the second one /dev, we will get blank when we give fdisk -l. Only “/dev/null” is present, nothin...

Linux P2VIntroductionP2V Linux migrations are a combination of science, art and luck.P2V stands for Physical to Virtual. In other words, it is the process or procedure of moving a running system (operating system and everything installed) from a physical machine to a virtual machine.This page describes some of the (un)usual steps necessary to convert a Linux system into a virtual machine running under VMware ESXi Server. The same steps should mostly apply to other virtual platorms/hypervisors like VirtualBox, KVM and QEMU.The focus of this P2V explanation is on Red Hat and CentOS guests as they are not only supported, but benefit from kudzu and rescue disk capability built-in. Other distributions can of course be converted but the exact steps will vary.So, let's get started.What to use (or not)The following software products claim to do P2V, but in fact do not seem to support Linux, so YMMV Virtual Server Migration Toolkit EZP2VThese products do support Linux in some way... VMware Con...

Resolving Linux boot issues after P2V with VMware ConverterRecently I had to deal with migrating SuSE Enterprise Linux servers from the old environment to the Vblock. Customer had a number of physical servers and XEN instances that needed to be moved to the new vSphere environment.While VMware Converter 5 does a good job live-cloning the existing Linux servers, sometimes you have to use the Cold Clone boot CD if the physical server uses software RAID (and then boot VM from the broken mirror side), or sometimes the resulting VM does not boot because of issues with bootloader.For the most migrations I’ve used VMware Converter 5.0. One thing you need to do right away is to modify the config for VMware Converter to enable the root login and keep the failed helper VM. Enable useSourcePasswordInHelperVm flag and disable powerOffHelperVm. See http://kb.vmware.com/kb/1008209 for details.Now you should have the result of your failed conversion preserved, and should be able boot the VM to...