本站用于记录日常工作内容,虚拟化云计算,系统运维,数据库DBA,网络与安全。
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...
Using NAT for container with private IPsUsually you supply public IP addresses to your containers. Sometimes you don't want to do it (lack of IPs, etc.). This article describes how to use private IP addresses for containers.目录1 Prerequisites1.1 IP conntracks1.2 IP forwarding1.3 Enable iptables in OpenVZ 7/Virtuozzo 72 How to create the container and attach network properties to it3 How to provide access for container to the Internet3.1 Save new iptables rules3.2 Firewall3.3 Test4 How to provide access from Internet to a container5 External LinksPrerequisitesMake sure that below prerequisites are met, otherwise it won't work for you!IP conntracksIP connection tracking should be enabled for CT0. For recent OpenVZ kernels (2.6.9 and later) connection tracking for CT0 is enabled by default, but it can be disabled by vzctl 4.7 and newer (because it has a negative impact on venet performance, see OpenVZ Bug #2755). So, make sure there is NO line likeoptions ip_conntrack ip_conntrack_disab...
ESXI5.5 本地磁盘分区丢失的解决方法,1、通过ssh进入ESXI shell,使用fdisk -l命令查看当前系统的各个分区情况2、使用esxcli storage vmfs extent list命令,查看卷名,设备名3、使用esxcli storage filesystem list命令,查看各分区的挂载情况,对于丢失的分区会提示相应错误4、使用partedUtil getptbl /vmfs/devices/disks/device_name 查看相应磁盘的分区表如:~#partedUtil getptbl /vmfs/devices/disks/naa.5000c5000d8b4e0d 得到以下信息gpt121601 255 63 19535251681 2048 1953523711 AA31E02A400F11DB9590000C2911D1B8 vmfs 05、再设置分区表,~#partedUtil setptbl "/vmfs/devices/disks/naa.5000c5000d8b4e0d" gpt "1 2048 1953523711 AA31E02A400F11DB9590000C2911D1B8 0"6、执行完以上命令后到主机存储配置界面即可看到丢失的存储器,此方法适用于磁盘意外脱机且无法自动挂载分区的情况,也适用于意外删除存储器,无损恢复。7、可根据实际问题灵活使用,可参考VMware KB http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1036609;http://kb.vmware.com/selfservice/micro...
    总共60页,当前第14页 | 页数:
  1. 4
  2. 5
  3. 6
  4. 7
  5. 8
  6. 9
  7. 10
  8. 11
  9. 12
  10. 13
  11. 14
  12. 15
  13. 16
  14. 17
  15. 18
  16. 19
  17. 20
  18. 21
  19. 22
  20. 23
  21. 24