![]() ![]() As you say, RHEL5 is supported Converter goes a different path for unsupported distros. ![]() To the first question - you don't need to do that. When converting Windows, one of the post-conversion steps is to remove "hidden" devices, which includes hidden NICs, before you can assign a static IP to the VM.ĭoes this apply to Linux? (I don't think so) If not, I should be able to just boot up the resulting VM assign my static IP to eth0 (that's what it is now), and I should be good to go? Do I need to change the destination storage to "thin" and "Basic storage", or is this unnecessary with this version of Converter? That page is from Sep 2013, which is probably an earlier version of Converter. I don't know if this is still applicable to converter 5.5, since it supports RHEL 5.x. See Kernel Panic Using VMware vCenter Converter Standalone - Uptime Through Simplicity. ![]() I have found references that say I should edit the storage of the destination VM if I am using LVM (and I am). I will run the converter from a Win2008 R2 machine, pointing it at my Linux box. I need to convert a physical RH Enterprise Linux 5.11 physical server, using Standalone Converter 5.5.
0 Comments
Leave a Reply. |