RHEL 3 P2V Conversion

Similar Questions

• RHEL 4 P2V conversion fails at Boot/cloning

  I'm trying to convert a box of RHEL 4.9 of the physical to virtual, and I'm running into the following error message:

  Error: Impossible to clone the volume mounted on ' / boot ' to 'ip.address.of.source '.

  / boot is the first player tries to clone through.

  I joined the server agent and the worker log files.  I am using vCenter Converter Standalone 4.3 (Win7 x 86) and ESXi 4.1.0 and conversion from a distance.

  The only thing I've changed is the NIC, and I assigned an IP address using the virtual machine and set the DNS suffixes.  Drives, memory and processors are that they are on the physical machine.  The server that hosts ESXi has the hardware to support.

  I have the physical ability to su to root.  In the converter - converter - Worker.xml and agent.xml files, I put useSudo and useSourcePasswordInHelperVm to true.  I tried enabling root SSH and conversion of the machine, but I still end up with the above error.

  I checked for if make sure that time is located on the linux machine as the machine virtual host machine (I found a thread indicating that it was someone else).  I also checked the xml files above for keepSparseFile that is set to true by default.

  I tried Googling how to install agent converter on the Linux box itself and execution of the conversion from there, but I guess that an agent has not been yet developed.  I found where someone has started a petition. If there is another way around him, please let me know.  I'm willing to try anything.

  What could help to convert this machine?  I've searched and searched, and every possible solution I tried did not work.  Help, please!

  Good to know it worked

• P2V Conversion error (ignored Socket)-

  Nice day!

  I would like to ask for help with the issue, I met with my first try of P2V Conversion with a Server Live (RHEL4) with SAP, I used version 5.5 of ESXi.

  Please see attachment for summarized error encountered.

  Nice day

  It is usually advisable to attach the beam of any newspaper. Usually the server log contains no interesting information. In this case however the original error has been adopted if something can be seen.

  I would recommend you stop all the essential services (especially Oracle) before the conversion, and then try again. Converter uses cloning with 'tar' to the file level. Even if the conversion itself was successful, you'd have incompatible application files if the services were running in this.

  --> tar:. / oracle/PRG/origlogA/cntrl/cntrlPRG.dbf: file changed as we read it

  --> tar:. / oracle/PRG/sapdata1/system_1/system.data1: file changed as we read it

  --> tar:. / oracle/PRG/sapdata1/undo_1/undo.data1: file changed as we read it

  --> tar:. / oracle/PRG/sapdata1/cntrl/cntrlPRG.dbf: file changed as we read it

  HTH

  Plamen

• Blue screen after the work of completely P2V conversion completed

  Hi all

  I have try the P2V of Powered - on Windows XP conversion.

  The conversion work was finished with the status "completely."

  However, after that, when I try to power on the target of the Win XP on ESXi machine, the machine displays the blue screen and does not start.

  If there is a way to solve this problem, would you please let me know?

  [more info]

  1.

  I chose the installation of vmware tools option in the conversion with VMware Converer autonomous steps.

  However, it was not installed in the target machine Win XP on ESXi.

  2.

  In this Windows XP P2V conversion, I can always find a certain caveat on the sysprep file in Converter Wizard.

  The warning is "Impossible to locate the necessary Sysprep files."

  Due to the expiration of the period of support for Microsoft's Windows XP, I can't do anything about this warning.

  The default disk for XP controller is BusLogic, specially for 32-bit Windows. It might work with LSI Logic, too but with SAS - hardly.

  The warning of sysprep is on the customization steps. If you do not it - ignore it.

  In regards to the VMware tools - you can install later vsphere client, after fixing the boot

  HTH,

  Plamen

• P2V conversion and snapshot

  Hello

  I found the below on one site. Can someone please clarify?

  Q. What are the parameters that are taken into consideration when we initiate a snapshot?
  SNA. Configuration of the virtual machine (what hardware is attached to it)
  Status of the virtual hard disk file (back if necessary)
  The memory state of the Virtual Machine (if it is under tension)

  Could you please develop meanings?
  

  Q. What are the requirements to convert a physical machine into a virtual machine?
  SNA.  An agent must be installed on the physical machine
  VI client must be installed with plug converter
  A server to import/export virtual machines
  

  (What agent)

  (Where the VI client must be installed and what is converter plugin)

  (Please specify)

  Answer to Q1:

  on the application of a snapshot is to be able to return to exactly the State of the virtual machine in which the snapshot was created. In order to do this, all the (content of the disc, memory,...) must be restored. One of the reasons to come back to a snapshot may be an update that did not work as expected.

  Answer to Q2:

  P2V installs the converter on the source machine agent.

  The Client Plugin is no longer necessary. It was part of the vCenter Converter Server which was provided as a plugin for vCenter Server. With vSpehre 5 the converter is not supplied with vCenter Server, but provided as a separate application.

  For a P2V conversion, it demanded to have a source and a target to which the source machine is converted as a virtual machine.

  André

• P2V conversion where the Source is on the remote network?

  Hi all

  I am new to this forum and a little new for VSphere 4.

  My company offers off-site data protection and storage services, and has recently begun branching out in recovery of virtual network. In a Word, virtualize us network services essential to the customer on our ESX 4.0 host servers and make them available for access secure site-level disaster. Until recently we have used a re-usable restore starting from active state backups online system on servers as our means of conversion model VM P2V. It worked pretty well with one notable exception - a Windows SBS 2003 server.

  As a work around the BMR virtual conversion, we would like to perform a 'traditional' system P2V conversion. The challenge? The source system is physically located miles on the customer's network.

  So far, we have installed the VMWare Converter Stand alone on the source system (stand alone seems to be something wrong to get the VMWare Infrastructure compatible conversion, you must communicate with the destination ESX Server) and open the necessary ports on our firewall to allow communications with our ESX Server. Everything seems to work properly; However, the destination for the new VMDK cannot be the ESX Server. Since we need all volumes on that server to be cloned, the resulting 200 GB of a value of data transferred over the network will make this process impractical.

  How can convert us this system to a virtual machine that is:

  1. written on a removable unit attached locally for transportation later and later import to our host server VSphere ESX 4.

  2. compatible with VSphere ESX 4.0.1

  Hope for an answer or a 'trick '.

  Some of the VMware machines are available as files of the FVO. If you go into the file menu of the vSphere client you will see "Deploy OVF model". Who can be a URL. I'll see if I can find a deployable unit of the FVO and post the link.

• SQL database Suspect after the p2v conversion.

  When I run my server sql p2v conversion 2000, one of the databases appear as 'suspect' and will not rise? I've been running conversions every day for months without problem, but has added an array with a MSA50 P600 controller and moved databases to the MSA50, and left the logs on the server (placed in a directory). I don't understand why this data appears as a suspect after the change. I can't knock the sql services since this is a production server. I run on VMware server 2.0 p2v conversion.

  You should try using the version converter 4.0 beta because we made some improvements to solve these problems (some changes in the way which we snapshot). Also use Converter 4.0 beta, you can choose to stop SQL services before taking snapshots, so ensuring consistency of the database.

• RHEL 5 P2V converter server to support static IP address problem

  Hello!

  I am doing an internship where I set up a VMware ESXi 5.1 environment, and I have to P2V a couple of servers RHEL (5 and 6).

  So now I'm looking for how the VMware vCenter Converter Standalone Client 5.0.1. I've done a few P2V, successfully!

  But it seems that whenever I want to do a P2V, I have to use a different static IP address by using the converter server because otherwise the converter stops at 1% and tries to connect using the converter server.

  What I don't understand, is that I'm only a P2V both, and so the IP addresses I use are reserved and are not of any other machine.

  Does anyone know what is the problem? Because if I have to make a couple more P2V, I'm out of IP addresses I use...

  Thanks in advance!

  Hello

  We were able to identify the problem and it is not in the converter itself, but rather related to the physical infrastructure. The problem is in the ARP cache on the bridge of the target network. After the first conversion, he has cached an ARP entry for the IP address for assistance. When you start the second conversion, the new virtual machine that is created has a new network card with a new MAC address, but the entry door is not aware of this change when Converter Server tries to connect to the help, the gateway sends IP packets to the wrong MAC address and finally they are deleted. When the cache ARP on the bridge which expires - that the problem be resolved automatically (in our environment by default, it is 15 minutes, but it depends on the material specifc and configuration).

  A possible workaround is to generate network traffic coming from within the VM assistance program (e.g. a ping to the IP address of default gateway) which generate an ARP traffic and update the gateway ARP cache. Instructions how to connect using VM are available at http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&externalId=1036746. Once you sign in, you can test anything (same IP invalid target does the job) and the conversion should proceed immediately.

  HTH,

  Ivan

• P2V conversion error

  Hi all

  The conversion of P2V of Windows 2008 R2 machine, I get error "destination doesn't support EFI firmware.

  Please give me the solution to resolve the error.

  Thanks in advance.

  Sennthilk

  Hello

  Yes. This is not support on esxi 4.0, support since version 4.1U1 esxi.

  Thanks Plamen

  Sennthilk

• P2V conversion for Windows 3.1 box

  I have a client who we would like to P2V Windows 3.1 sound box because of some old, * but still useful *, applications out there, he is a candidate.  I looked at the specs for the vCenter Converter, and Windows 3.1 is not a supported operating system to do this, while VMware does support Windows 3.1.  How can I go on the conversion of this machine to a virtual machine?

  Thank you!

  Wow - someone who still uses Win3.1 in production? -cool

  I volunteered to help remotely if necessary

  Anyway-, here is the procedure...
  Forget the converter - it won't help.

  Plan A: requires a Ghost or Acronis LiveCD

  Start the Win 3.1 machine in the LiveCD and create a full disk image and store it in the network
  Then, create a new virtual machine with a slightly larger than the original IDE drive
  Start new virtual machine in Ghost or Acronis LiveCD and restore the image via the network

  the next time you start, make sure the disc starts the disk and cross your fingers

  
  Plan B: requires a Knoppix LiveCD or a BartPE live CD or similar

  Start the Win 3.1 machine in the LiveCD and create a zip of the bootdrive content and store it in the network
  Then, create a new virtual machine with a slightly larger than the original IDE drive
  Start the new virtual machine in an image disk BACK
  Run fdisk to partition the drive - restart
  format C: and sys C: execution to make the bootable disc
  then start in LiveCD and unpack the archive that you have created before - copy archive network

  the next time you start, make sure the disc starts the disk and cross your fingers

  Plan C: remove the hard drive and attach it inside a USB box to a computer that is running VMware Workstation or VMplayer 3

  This is the way with the best chances, but it requires a few steps...
  I explain when you decide to try this road

• A general system error occurred after the P2V conversion

  Hello

  I have trouble starting a virtual machine right after P2V with VMWare Converter4.3 conversion.

  My infrastructure is ESXi-4,1 to connect using vSphereClient.

  The material is: Dell Power Edge T310 - 64-bit; 4 GB of Ram; CPU intel Xeon 2.4 GHz 4 cores per socket.

  Already running 2 VMs - MS Server 2 K 8 64-bit, DC and File server.

  Just added one more VM workstation XP Pro 32-bit and the cant restart it. Error I get is: a general error occurred: the virtual machine could not be started.

  any help with it?

  It uses IDE or SCSI controller?  If IDE, I'd do the conversion again and move the SCSI controller

  See also

  http://KB.VMware.com/kb/1033243

• P2V conversion for a remote source of Debian Linux

  I tried to convert (P2V) my server physical linux (debian), but I can't.

  I use a stand-alone server of vConverter4.

  The conversion always stop on "connection to the server for assistance on the VM converter target."

  I can access the virtual machine to help but I don't know what to do.

  Help me please!

  Then, you should try to make your help-VM to pings. Starting conversion, change the setting of VM for assistance, check the virtual network card adapter/device is "connected". If it is already connected, disconnect and then reconnect the back and now try to ping your IP VM Wizard.

  vcbMC - 1.0.6 Beta

  Lite vcbMC - 1.0.7

  http://www.no-x.org

• VMware Converter standalone 4.0.1 gets 97% error: impossible to reconfigure the virtual target computer. Linux P2V conversion

  I have 97% then it goes down. I'm conversion server Ubuntu 9.10. I will attach the logs. "GrubInstaller::InstallGrub: /usr/lib/vmware-converter/installGrub.sh failed with return code: 127 and message:

  /VMware - updateGrub.sh: 38: grub: not found

  GRUB runtime error

  Vmware runtime error - updateGrub.sh through chroot into/mnt/p2v-src-root

  22/10/09 discovered Ubuntu 9.10 uses Grub2 is the problem and can it work with Grub2?

  Let me know if you can help.

  OKI I did the P2V and after it failed to 97%,

  I started the virtual machine with the LiveCD mode help, connected root to/dev/sda1, installed grub2 and finally ran "upgrade-from-grub-legacy".

  After the reboot, everything works fine.

  So no need to replace your UUID and all that. That should be enough.

  Thank again for this band of working capital.

  Bragi - of Iceland

• P2V conversion but who want to leave the physical Box Live

  We have recently installed a VSphere 4 server in our environment for testing purposes. We wanted to go some of our test servers to a VM platform, then we can switch as required. One of the servers that I have is to be a pain with conversion due to a bad network card. What I want to do is take our 'live' server and run the conversion of a VM but change name of computer, IP info, etc but that let the direct physical server. I know that I need a time out for the live system at some point, but I just want to be sure I'm not missing something or VM adds any information that may cause it to fail. Ideas, thoughts or suggestions?

  For Windows 2003 itself, it's name change, but given the need for a back-end system app would make it harder, IMO.

  Unless you P2V'ed that too, ofc...

  I do nothing on ubiquitous, but the idea of an app duplicated in a BONE duplicated hit a back-end server, would be a no-no for me...

  Sorry, can not help more than that... Good luck...

  / Rubeck

• MS Windows SBS 2008 P2V conversion

  Hello

  I want to convert MS Windows 2008 Small Business Server Premium (DC, Exchange, SQL, etc.) to the virtual machine under ESX 4.0.

  I can't do cold because of the software RAID migration.

  Is it possible to stop most services (including the AD) and 'own conversion' to the VM?

  What kind of problems I have to wait?

  Best regards

  Nanyo

  It is never good practice of a P2V one domain controller.

  Build a new VM DC...