hi
Can I migrate a physical Debian Etch/Lenny server using VMware vCenter Converter Standalone 5.x to ESX/vSpehere?
↧
P2V Debian Etch/Lenny
↧
Agent converter Error ColdClone P2V to ESXI 5.5 server
i am Trying to convert a machine in a coldclone environment, because the current vConverter software does not support the raid system on a machine. Thus, i do not want to disable it. (Cold clone iso 4.1)
The converter stop somewhere in the step 2 where i need to select my datastore. After Choosing it, it goes fine, with a loading circle saying "Checking destination availability...", and then, it hangs a good time (20-30 seconds) at the line "Verifying desitination parameters...".
Afterward, the converter returns an error : unknown error returned by vmware vConverter agent.
Anybody has ideas on the current problem ?
Thanks
↧
↧
Converter and Windows activation
Hi,
I'm running my ESX 3.5 during the 60 days trial mode, and during this period I need to test our main servers in VM mode. For this reason I donloaded VMWare Converter 3.0.2u1 and converted two Win2003 server. But at the en of the job I was unable to login onto the new VMs because windows "must be activated". Is there a way to perform the conversion by exactly cloning the two systems, without asking for activation ? This conversion is for test only, so I cannot dismiss the real server by now. What I would like to do is convert the real server comlletely, keeping the same names, IP, etc, then switch off the real servers, power on the VMs and see if all goes ok. So, I will not run the real and virtual machine at the same time, but I need to keep the real servers ready and activated.
Is there a solution for this issue ? Thanks and bye, Stefano
↧
Unable to connect to the network share '\\localmachine\sharedname'
I'm using VMware vCenter Converter Standalone client, v5.0.0 build-470252, running on a Windows 7 64bit computer, trying to import a running Windows 2008 virtual machine (hosted by VMWare infrastructure) onto my local box.
On starting the converter, I "Connect to a local server"
Specifying the source system goes smoothly, though I ignore the certificate error. The conversion wizard installs its agent and connects to it OK.
For the Destination System I specify:
Destination type: VMware Workstation or other VMware virtual machine
VMware product: VMware Workstation 8.0.x
Virtual machine details:
Name: same as source system, as detected by the converter
Location for the virtual machine: \\localmachine\sharedfoldername
Username & password: my Windows 7 login credentials, with Full Control over \\localmachine\sharedfoldername, both the share and the underlying folder.
When the converter verifies the destination parameters, it reports: Unable to connect to the network share '\\localmachine\sharedfoldername'"
Investigative steps so far:
- Connecting to the share via Windows Explorer works fine; it is possible to write to the share
- I tried specifying the share as "\\localhost\sharedfoldername", but get "The specified network share 'localhost\sharedfoldername' does not exist." This was a bit of a long shot I guess, but the form does work in Windows Explorer.
- Have tried with file and print sharing both on and off - seemed worth a try after looking at other posts on this forum
The Help states "If you are connected to a local Converter Standalone server, provide a network path or a local path to the destination directory." I tried local path "C:\Virtual Machines\sharedfoldername", but got the message "Error: Destination specified as a (local) drive. Please specify a UNC path such as: \\machine\sharename"
The help also states "You do not have to provide user credentials if the destination location is on the local storage of the machine where Converter Standalone server runs." However the Next button is always disabled until credentials are provided.
Can anyone help please?
↧
Converter Hangs at 1%
I've got a machine that I've been tasked to virtualize, but I never get any farther than 1%, which is wierd because a collegue of mine P2Ved this server a couple months ago and it went through. (we had to delete that VM because it wasn't brought online in time.)
The conversion doesn't fail, it just stays at 1%.
Server is a Windows Server 2003 R2 box and it's main role is Raisers Edge. I turned off all the SQL services per another post. I'm not quite sure what else to include, other than the logs.
Thanks.
Message was edited by: Awanogardn Scrubbed the logs.
↧
↧
Preferred P2V solution (vCenter Converter or VEEAM)
So I'm analyzing and getting ready to convert a provided list of physical servers to vmware VMs and wondering what is the best solution to use. Do I use vCenter Converter or VEEAM? I want to know what most people are using out there and any pros and cons with each of them.
Thanks in advance.
↧
P2V Windows Server with multiple logical disks - creates 1 vmdk
Hi - when using VMware Converter what is the reason for creating 1 vmdk file when doing a P2V of a server that has 2 disks? Why doesn't it create two vmdk files?
Do most people just run the converter several times selecting 1 disk at a time??
When I select the C: and D: volumes of the server and resize them - instead of creating 2x15GB vmdk's it creates a 30GB vmdk.
What's best??
↧
Problems virtualizing Windows 8 OEM using VMware Converter 5.1 and Player 5.02
G'day,
I recently purchased a Dell XPS8700 workstation which came with Windows 8 installed.
I want to install Ubuntu (not dual-boot) on it but before doing so I wanted to virtualize Windows 8.
So, I downloaded VMware Converter 5.1 Standalone, and used it to create a VM of Windows 8. So far so good.
I then tried to run this VM in VMware Player 5.02 (both the Windows and Ubuntu versions). Player recognises the VM correctly but when I try to power it on I see a black screen for a few seconds and then it exits. There are no error messages produced in the logs that indicate what the problem is.
Has anyone had success virtualizing Windows 8 for use with VMware Player?
Thanks,
Chris.
↧
converter V5.1.0 fails at 71%, Warning: Unable to read the block at offset '28,243,914,752' on volume 'D:
Hello:
I am converting physical machines to VM sot hat we can consolidate our environment. The converter V5.1.0 Build1087880 fails at 71%, with a Warning:
so far, I have good progress on other physical machines except for this stubborn XP -X64 machine. We need to keep it for legacy reasons until there are replacement apps for all sw running on it (; This machine has SSD drive and no spinning HD
each time the conversion is able to start and complete the first on two drives. The GUI states its fine , but the log shows
2013-08-11T09:00:00.782-04:00 [02748 warning 'Default'] Disk number 1 has been skipped because of errors while reading partition table
2013-08-11T09:00:00.782-04:00 [02748 warning 'Default'] Disk number 1 has been skipped because of errors while reading dynamic disks header or LDM database is corrupted
When it gets to the second drive, I stops as it cant read some sector block.
2013-08-11T09:00:00.782-04:00 [02748 warning 'Default'] Disk number 2 has been skipped because of errors while reading partition table
2013-08-11T09:00:00.782-04:00 [02748 warning 'Default'] Disk number 2 has been skipped because of errors while reading dynamic disks header or LDM database is corrupted
2013-08-11T10:16:13.706-04:00 [04324 error 'task-2'] BlockLevelVolumeCloneMgr::ReadAndSkipBadBlocks():
Error (type: 2, code: 27) reading 223232 bytes starting at 0x000000069377f000 from the source volume D:
2013-08-11T10:16:53.800-04:00 [04324 error 'task-2'] BlockLevelVolumeCloneMgr::ReadAndSkipBadBlocks():
Error (type 2, code: 27), detected bad sector at offset 0x0000000693796000 on the source volume D:
I have run several apps to check and fix the D drive, but none find any issues. the XP-X64 machine has been restated after each test and re run. no issues are found on either drive
I have tried to run the converter without the D drive. It wont let me do so as it states that the D drive Is critical to the conversion and wont proceed without it
I have attached GUI screen shots and two logs files
Can anyone please help?
Is there is a way to find the root problem or proceed?
if windows cant find an issue with the D Drive why does the converter?
↧
↧
Converter 5 does not recognize LVM partition on Oracle Linux 6
I've got two physical servers running Oracle Linux Server release 6.3 64-bit. They each have a /boot partition that is ext4 and the rest on an LVM partition:
/dev/mapper/vg_cleveland-lv_root / ext4 defaults 1 1
UUID=3d37688e-305a-4974-9bb7-f02232b78790 /boot ext4 defaults 1 2
/dev/mapper/vg_cleveland-lv_swap swap swap defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
vCenter Converter is only recognizing the /boot partition in the "Data to copy" section "Select volumes to copy".
If I go forward the conversion fails when trying to reconfigure the VM. I've looked through the user guide and googled a bit but I can't seem to find why the ext4 LVM partition is not being recognized by Converter 5.
↧
P2V Ubuntu 10.04
Hi,
I am trying to P2V a couple of Ubuntu server using the Converter Standalone client 5.1. I have tried to enable sudo to not use passwords, as described in the following KB article VMware KB: Enabling the use of a non-root user for hot cloning of a Linux source machine
I have also tried to just enable the password for the root user per this posting. Ubuntu 8.10 P2V sudo
All with no luck. I have attached the worker log and the server log. It looks like the ubutu server may be activly killing my connection. Any thoughts?
↧
Error: Unable to connect to the Converter helper server on the destination virtual machine.
I keep getting this error and i have checked all the steps with the helper VM and it gets stuck at 1% then errors after about three hours this is with a static IP for the helper address. converter 5.1 is what i'm using
Thanks!
↧
A general system error occurred: unknown internal error
I am trying to convert the two remaining vm's on my Hyper-V 2012 server. I am doing a physical to virtual conversion of a powered on machine since Converter 5.5 doesn't support 2012 Hyper-V. The vm's are both Server 2008 R2, one is an Exchange server and the other is a domain controller.
I have 2 ESXi hosts attached to a vCenter server. I tried removing the ESXi host from vCenter and converting just using IP addresses, that did not work. I have also tried using local admin credentials on one of the servers.
I already converted two other vm's with no issues, so I'm not sure why I am suddenly running into issues with these last two.
Attached are the relevant exported logs. I see where the error occurs, but I can't figure out why it is failing. Other people with similar issues seemed to have firewall, DNS, or disk errors. I don't seem to be getting the same errors I've seen others get.
↧
↧
Error: Unable to clone volume C:
I'm using converter standalone v5.5 build 1362012 and am trying to copy a VM that is presently in Amazon Web Services to my local vSphere environment. I've done it successfully before with this exact same VM as a test, but now I'm actually trying to move the VM and encountering this problem.
The error message is FAILED: An error occurred during the conversion: converter.fault.FileIOFault
At first I was trying to use converter to directly copy the VM from AWS to vSphere. When that failed twice, I tried using converter to convert the VM to a Workstation VM, which I could later import into vCenter and that failed as well.
The VM in question is Win2008R2. It has three disks, each with one basic volume that takes up the entire disk:
C: 30 GB
D: 20 GB
E: 40 GB
I am not trying to resize volumes as part of the conversion. There is plenty of free space on the volume I am writing the VM files to (that folder is on a shared volume on the host running converter).
I've tried running chkdsk on the VM being converted and it did not report any errors. I also tried defragmenting the volumes but it made no difference.
Here is the log bundle from converter:
https://lpga.box.com/s/1e62weqjzq6lkv87eis9
Any suggestions on how I can fix this problem?
↧
P2v fails error "Unable to reconfigure the destination virtual machine."
Hello
i am trying to convert physical windows machine using vcenter converter standalone 5.0 ,it got failed at 98 % & 95% .whats the reason
how ro resolve this iuuse.first time it got failed at 95 % and second time it got failed at 98 % says same error.
↧
After V2V new disk size is not reflecting
Dear team,
To set a new size for vHDD2 I have done the v2v .
Before v2v vhdd2 (d drive) size was 50GB , in v2v set the new size as 60GB ,
after v2v if I check vHDD2 size it show 50GB in my computer and 60GB in disk management , need ur assistance why it showing this discrepancy please help.
regards
Mr VMware
↧
Blue screen 0x0000007B VM boot error with 64-bit Windows 2003
Blue screen 0x0000007B boot error with 64-bit Windows 2003 virtual machine converted from physical machine.
I am running VMWare Converter Starter Edition version 3.0.0 build-39557 installed on a Dell PowerEdge 2950 (a couple of months old) running Windows Server 2003 Enterprise x64 R2 (version 5.2.3790, SP1 with all the latest updates). The server has SCSI RAID drives (2 separate arrays for a physical C: and D: drive).
The physical machine is a new clean installation of 64-bit Windows Server 2003 with no other software installed except for VMWare Server and Converter.
I am attempting to create a virtual machine from this machine to run in VMWare Server (version 1.0.1 build-29996) on the same physical machine. The conversion appears to succeed, but when I attempt to start the new virtual machine, it begins to boot, displays the Windows 2003 startup screen briefly, and then fails with a blue screen with the following error:
STOP: 0x0000007B (0xFFFFFADFD520F3C0, 0xFFFFFFFFC0000034, 0x0000000000000000, 0x0000000000000000)
I understand the "0x0000007B" means that it can't access the boot device for some reason. I have searched these forums and the knowledge base, but haven't found a solution to this problem.
I have been able to successfully convert and boot a 32-bit Windows Server 2003 physical machine as a virtual machine running in this same VMWare Server. I don't have any other 64-bit machines to test this with.
I am logged in directly to the console of the physical machine with the administrator account. I enabled virtualization in the BIOS. I have tried various combinations when building the virtual machine (customizing or not, fixed or variable disk sizes, importing both C: and D: drives or importing only the C: drive, etc). I have the SYSPREP files from the x64 installation disks locally on the server, and I have run SETUPMGR in this folder to create a SYSPREP.INF file. All of these various attempts have failed with the same boot error.
Is it possible to build a 64-bit virtual machine using VMWare Converter Starter Edition? Any suggestions on how to resolve this issue?
↧
↧
P2V Debian Etch/Lenny
hi
Can I migrate a physical Debian Etch/Lenny server using VMware vCenter Converter Standalone 5.x to ESX/vSpehere?
↧
Automating Converter Standalone using Converter-cli.exe
Hi,
I have worked out that this must be possible because of the inclusion of converter-cli.exe with Converter 5.0.1 Build 875114, plus I've got very close but not quite close enough! I have vCenter 5.0 and ESXi 5.0.0 hosts.
I am using the following XML and it's submitting the job to Converter with what looks like to be the correct details but fails straight away with the error:
FAILED: The source configuration file is invalid, corrupted or not recognized.
I've checked logs in the following locations but nothing gives me any clues as to what isn't quite right:
C:\ProgramData\VMware\VMware vCenter Converter Standalone\logs
C:\Users\All Users\VMware\VMware vCenter Converter Standalone\logs
C:\Users\XXAdmin\AppData\Local\VMware\VMware vCenter Converter Standalone Client\Logs
Anywhere else I can look?
My XML file (p2v.xml):
<p2v version="2.2" xmlns="http://www.vmware.com/v2/sysimage/p2v" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.vmware.com/v2/sysimage/p2v p2vJob.xsd" xsi:type="P2VJob">
<source>
<hostedSpec networkPassword="domainpassword" networkUsername="domain\username" path="PHYSICALSERVER"/>
</source>
<dest>
<managedSpec datastore="Datastore XXXX" folder="Temp" host="HOST1" resourcePool="" vmName="NEWVM">
<creds host="VCENTER" port="0" type="sessionId" username="domain\username" password="domainpassword" />
</managedSpec>
</dest>
<importParams diskType="VMFS" preserveHWInfo="true" removeSystemRestore="false" targetProductVersion="PRODUCT_MANAGED">
<nicMappings/>
<diskLocations/>
</importParams>
<postProcessingParams/>
</p2v>
I'm running the command: C:\Program Files (x86)\VMware\VMware vCenter Converter Standalone>converter-cli -s C:\Temp\p2v.xml
I feel sure that this is just a minor issue with the xml input configuration file and if I knew the correct syntax or had an example file I could get it working. I can't find one anywhere. Should the datastore be the name vSphere/ESXi knows it as rather than the name I see in the vSphere Client?
Please help!
Thanks
↧
"Error: Unable to connect to the Converter helper server on the destination virtual machine."
Using vConverter 4.3 unable to complete a P2V conversion, the following message appears: "Error: Unable to connect to the Converter helper server on the destination virtual machine." I set up an ip address manually to the Helper Server, but we did not succeed.
↧