I've spent my last saturday virtualizing physical Linux servers by a customer site. As VmWare Converter is in experimental status for now for virtualizing Linux I think that's a good idea to put the procedure I've used and that I've described in my two previous posts (1, 2) but without screenshots ;) .
So, let's begin with conversion: first of all shut down your physical linux box and put the VmWare Converter CD - I've used the last one, 3.0.1 - in your CD reader and boot. Follow the on screen procedure and send the images to your target Virtual Infrastructure host. At the end of the cloning task you'll find the definition of your brand new VM browsing your Virtual Infrastructure Client.
Take a Linux rescue CD, my favourite is Fedora Core 2 rescue linux ('cause works with all the linux boxes I've virtualized), set it as boot device and fire up your VM.
Be sure to boot from the rescue CD. Otherwise you'll surely get a Kernel Panic messages
If you use FC2 rescue CD just press enter (with other rescue CD you'll have to type linux rescue at the boot prompt)
Select the language...
... and do NOT connect the network (sometimes it bring to an hanged system)
Linux rescue will try to mount the virtual machine file system in /mnt/sysimage: let's mount it in read-write mode.
As for the messages from your linux console, you can set /mnt/sysimage as your root environment; press the OK button and you'll be in a shell as root user.
Issue the chroot /mnt/sysimage command,
and edit /etc/modules.conf with your favourite editor, changing every scsi alias with BusLogic and each eth nic with pcnet32. Save and exit.
Change directory to /boot and make a backup copy of your initrd-2.x.y-zz.img .
Then issue the mkinitrd command (mkinitrd -v -f /boot/initrd-2.x.y-zz.img 2.x.y-zz, all on one line as you can see in the below figure). Wait for the command to end,
... and reboot
Disconnect the linux rescue boot CD and see your virtualized linux box that come up.
During the first boot the virtualized box will reboot (sometimes) and kudzu will check for new hardware prompting for removing physical scsi modules configuration and for adding BusLogic and PcNet32 modules (always).
This procedure has worked for Fedora Core 6, Red Hat Enterprise Linux 3 with 2.4.XX-ELsmp kernels and for Red Hat 6.2 and 6.1 with 2.2.x-YYsmp kernels. The RH6.1 box has LILO instead of grub: I must issue the lilo command after the mkinitrd session in order to rewrite the MBR (don't know why...), and to get this vm working.
All the procedure is based on www.vmwiz.com but, I hope, more in depth explained and used after VmWare Converter cloning (not after P2V / Ghost cloning)