I need to convert (physical to virtual) and old Windows 98 box.
I made some tests with VMware Converter with no success.
Should I use an old version (as I made to P2V a Windows 2000 box some times ago, using VMware Converter 3.x)?
If so, where can I locate a very old version of VMware Converter?
Is there any other way to convert my Windows 98 box?
Regards
marius
I have Converter Standalone installed on my notebook, I put in the vCenter IP or name, doesn't matter, enter the administrator account, and still get permission denied to choose the VM to be v2v'd. The administrator login is the same as the domain/local administrator on the vCenter server, and the same login works properly for vCenter Server, it is the only login I ever use. I added the domain admin account to the Local Administrators account on the vCenter server...
What should I do??
Thank you, Tom
Virtual machines created on my old box, with vCenter Converter, fail to boot in VMplayer (on either old or new boxes). I'm seeing a black screen with a frozen cursor in VMplayer. I get this result with file
system/partitions converted with the either the IDE or SCSI settings. (The vCenter Converter Standalone manual refers to a 'SATA' option but it does not appear in the 5.5.0 version I'm using.)
.
I am attempting to create a virtual machine of my old XP Pro 32-bit machine to run on my new 64-bit Win7 box. (If my new machine, with 'Haswell' architecture, supported XP we wouldn't be having this conversation, I
would have just set up a 'dual boot' to go alongside my Linux install.) In a previous job I was a VMware 'end user' (clicked on an icon and launched a vm). I'm working on this project at home. I've no experience in
converting physical machines to virtual. My method has been to create the vm's on my XP machine (only using the system drive as a source) and move the HDD drive to the new Win7 box.
The exception to Vm boot failure is with the 'guest' file created with VMplayer '6' on the new Win7 host system using the 'XP Mode' as the source.
.
My equipment and software versions are as follows;
Virtual machine source system:
XP Pro SP3 32-bit (HAL 5.1.2600.5512), Intel Core2 Duo (3 MHz), ASUS P5-K motherboard (AMI BIOS '0603,' IDE/SATA controllers), 4 GB ram, WD 500 GB IDE/SATA HDD, Samsung IDE CDROM/DVD, ASUS/NVIDIA GeoForce 210 Video (1024
MB), Linksys 1032 v3 Gb LAN.
VMware vCenter Converter Standalone 5.5.0 Build 13602012
.
Host System
i7-4770K, ASUS Z87-Pro motherboard (AMI BIOS '1602,' SATA/AHCI Controllers, Intel 'HD Graphics 4600,' Intel 'I217-V LAN), 8 GB ram, Samsung 250 GB SSD, Western Digital (1TB, this is the drive that moves between machines)
and Seagate (2TB) SATA HDD's, 'Lightscribe' DVD.
Windows 7 Professional, 64-bit 6.1.7601, Service Pack 1 (HAL "6.1.7601.17514")
VMware Player 6.0.1 build-1379776 "Workstation 10.0 Virtual Machine."
.
The visual impression is a failure loading BIOS. I never see a blinking cursor. I could be wrong. The VMware logo pops up quickly followed by the black screen with the frozen cursor. In all cases the VMware.log files
look about the same through the time 'vcpu-0' is started. The virtual disks are discovered and mounted. The VM is powered on. The BIOS-UUID is listed and failure starts for all but the XP-Mode VM created on the host
machine. Just prior to the BIOS call, all of the vm's are referencing vga/svga setup and USB 'discovery.' The failed machines seem to have a lot fewer video references. I've included short log snips from the point
where the vm's fail and a comparison at the same point with the vm that starts:
.
VM's failed (from ASUS P5K MB):
2013-12-03T16:25:10.982-05:00| vcpu-0| I120: PCIBridge7: ISA/VGA decoding enabled (ctrl 0004)
2013-12-03T16:25:10.995-05:00| vcpu-0| I120: VIDE: Curr CHS info cyls: 17475 heads: 15 sects: 63 lba_cap: 195373056
2013-12-03T16:25:11.005-05:00| vcpu-0| I120: BIOS-UUID is 56 4d e5 60 6a 65 8a ea-73 79 a1 62 3e 7e db 9e
2013-12-03T16:25:11.462-05:00| vmx| I120: VUsbUpdateVigorFieldsAndAutoconnect: New set of 3 USB devices
(A lot of USB discovery lines removed for brevity. None had any complaints.)
2013-12-03T16:25:46.137-05:00| vmx| I120: VMXVmdbCbVmVmxExecState: Exec state change requested to state poweredOff without reset, soft, softOptionTimeout: 20000000.
2013-12-03T16:25:46.137-05:00| vmx| I120: Stopping VCPU threads...
2013-12-03T16:25:46.500-05:00| vmx| I120+ OvhdMem: Final (Power Off) Overheads
.
VM boots (from ASUS Z87-Pro MB):
2013-12-03T16:50:34.031-05:00| vcpu-0| I120: PCIBridge7: ISA/VGA decoding enabled (ctrl 0004)
2013-12-03T16:50:34.098-05:00| vcpu-0| I120: VIDE: Curr CHS info cyls: 17475 heads: 15 sects: 63 lba_cap: 266338304
2013-12-03T16:50:34.107-05:00| vcpu-0| I120: BIOS-UUID is 56 4d d8 c4 94 15 ef 4d-14 e5 0f 16 12 ab cf bb
2013-12-03T16:50:34.271-05:00| vcpu-0| I120: Unknown int 10h func 0x2000
2013-12-03T16:50:34.754-05:00| vcpu-0| I120: DDB: "longContentID" = "3167e271130ff9ed89be0d0f3a715cf3" (was "e1a75a0c8ef5fd0bde61e98e8ece8934")
.
In the happy ending vm, a lot more references to 'svga' occur followed by what I take to be gold at 'vcpu-0:guest.'
.
To date I haven't found a problem that matches mine in the forums (I see a lot more information on getting vm's running on fresh OS installs and a lot less on getting old systems virtualized.) My problem seems to exceed
the depth offered in the vCenter Converter and VMplayer User Guides (note; I'm not sure if this issue should be posted in the VMplayer or the vCenter Converter forum). I've also looked for a database or references to
hardware that has been known to work virtualizing a powered on XP Pro 32 installation (Given E-bay and the price of old equipment, building a new 'old' box might be an option!). I have access to a ASRock Z77 Extreme 3
based system. The ASRock MB, with an i5 cpu, supports XP Pro 32-bit in theory. I'm thinking of putting a cloned drive in that machine and upgrading my XP installation to something close to state-of-the-art. (The kid
will never know. I'll do it while he is at work.) I would then uninstall/reload vCenter Converter Standalone and attempt to virtualize the system.
I'm looking for advice on how to proceed or where I might find relavent information.
.
Thanks,
rick shelby
I am new to the community. I have used VM's in the past, but have not created one. I have VM Workstation 8.0 (2011). I have two laptops, Dell E6510 W7x64 and HP 8760W W7x64. I am trying to perform a P2VM of the HP machine to run on my Dell machine. I am using an external hard drive to store the VM. My userID is also part of the administrators group. I have two issues:
1. When I install VMware Converter Standalone 5.5 on the HP, everything appears good. I can make a VM. If I reboot the computer after installation of VM C S, I get to the "Press Cntrl-Alt-Del" screen (to initiate login), but once I continue, the computer goes into "la la" land for several minutes, then comes back to the "Press Cntrl-Alt-Del" and continues to loop/cycle if I try again. I then have to go into safe mode and restore the PC prior to installation of VM C S. HP support was not able to give me any help. Also, the VM I created (prior to re-booting) has the same issue when played (being that it captured that image). If someone has any ideas? I could not find a similar issue in my searching.
Note: the HP PC is a domain computer, but I have two userID's that are part of the local admin group. Something about this PC only is causing the issue.
Note: I have no issue installing VM C S on my Dell machine. I tried it and it worked ok.
2. Having issue 1 above, I tried to create a VM of the HP remotely from my DEll machine using two separate methods:
a. Workstation 8 - P2VM, I can get it started, but it fails within 1-2 minutes, either by "converter.fault.networkshareconnectfault" or "Unable to create VSS snapshot of source volume". It also seems that you cannot configure the VM in Workstation as you can with VM C S only (it does not give options automatically).
b. VM C S, This option allows me to configure the VM, but I am having issues with creation of the "network Share" where the VM will be stored. I am using an external HDD attached to the Dell machine, F:. I tried putting in the correct credentials for the agent on the HP machine to access the drive and "shared" the drive as \F. I then tried putting the HDD on the HP machine, but had similar issues. I am not sure the correct way to make it work.
I thought this would be straight forward, but it appears more troublesome. I would appreciate any help with these issues.
We are trying to convert a Windows Server 2003 x64 SP2 machine and get this error at 98 percent,
"FAILED: Unable to reconfigure the destination virtual machine."
The only reference I see in the log file is,
"2013-07-01T16:56:55.491-04:00 [03224 error 'Default'] [task,350] [LRO] Unexpected Exception: converter.fault.ReconfigurationFault
2013-07-01T16:56:55.538-04:00 [03224 info 'Default'] [task,379] [task-1] -- ERROR -- Convert: converter.fault.ReconfigurationFault
--> (converter.fault.ReconfigurationFault) {
--> dynamicType = <unset>,
--> faultCause = (vmodl.MethodFault) null,
--> description = "converter.fault.FileNotFound",
--> msg = "",
--> }"
I have attached the full log. Any help would be greatly appreciated.
During conversion P2V after 42 minutes 95% the conversion failed as shown in the subject? I tried twice and I obtained the same information at the same time and at the same %
Someone know why it is impossible to create a VSS snapshot at what means the error 2147754776
I attached the log too
Thanks for the help
If I resize my disks and it does a file/file copy on a hot migration. Am I guaranteed every file from the source server will be copied to the desitnation server. What does Converter do if a file is locked by an application or the OS and it cannot copy it? I normally shutdown all the services I can before doing the migration but I'm sure the OS still has files open.
I have tried converting a Windows Server 2003 R2 SP2 32 bit from physical to virtuel with VMWare Converter 5.5.
But every time it fail with "this Unable to update drive letters for the destination volume layout".
I have tried searching for it, but with no luck.
converter-gui-15.log
2013-12-10T19:01:17.911+01:00 [01264 info 'Default'] Connecting to host 192.168.101.12 on port 443
2013-12-10T19:01:17.911+01:00 [01264 info 'Default'] localVersion is: vim.version.version9
2013-12-10T19:01:17.927+01:00 [01264 info 'Default'] Remote version is: vim.version.version9
2013-12-10T19:01:17.927+01:00 [01264 verbose 'Default'] [VimApi] Local and Remote Version are the same. Talking with version vim.version.version9
2013-12-10T19:01:17.942+01:00 [01264 info 'Default'] Authenticating user root
2013-12-10T19:01:17.942+01:00 [01264 verbose 'HttpConnectionPool-000019'] HttpConnectionPoolImpl created. maxPoolConnections = 1; idleTimeout = 900000000; maxOpenConnections = 1; maxConnectionAge = 0
2013-12-10T19:01:18.020+01:00 [01264 verbose 'Default'] VimConnectionStore stopping keepalive
2013-12-10T19:01:18.020+01:00 [01264 info 'Default'] Scheduled timer canceled, StopKeepAlive succeeds
2013-12-10T19:01:18.020+01:00 [01264 info 'vmomi.soapStub[18]'] Resetting stub adapter for server <cs p:03ac8c40, TCP:192.168.101.12:443> : Closed
2013-12-10T19:01:18.020+01:00 [01264 info 'wizardController'] FillPage()
2013-12-10T19:01:18.020+01:00 [04944 info 'ThreadPool'] Thread enlisted
2013-12-10T19:01:39.942+01:00 [01264 verbose 'ManagedMachineDataConnectionLogger'] VimConnectionStore stopping keepalive
2013-12-10T19:01:39.942+01:00 [01264 info 'ManagedMachineDataConnectionLogger'] Scheduled timer canceled, StopKeepAlive succeeds
2013-12-10T19:01:39.942+01:00 [01264 info 'vmomi.soapStub[13]'] Resetting stub adapter for server <cs p:039f4a88, TCP:192.168.101.12:443> : Closed
2013-12-10T19:01:39.973+01:00 [06068 info 'ConverterSession'] Converter::Client::Gui::Common::DiagnosticDataProvider::ClearLastKnownSource - Clearing last known source.
2013-12-10T19:01:39.989+01:00 [06068 info 'vmomi.soapStub[10]'] Resetting stub adapter for server <cs p:03b1fde0, TCP:192.168.101.12:443> : Closed
2013-12-10T19:01:39.989+01:00 [06068 verbose 'wizardController'] VimConnectionStore stopping keepalive
2013-12-10T19:01:39.989+01:00 [06068 info 'wizardController'] Scheduled timer canceled, StopKeepAlive succeeds
2013-12-10T19:01:39.989+01:00 [06068 info 'ConverterSession'] Logging out of the Converter Server. (Session ID = "dbce63e1-5753-cd60-e8df-25bd0d81a4b4")
2013-12-10T19:11:22.235+01:00 [06068 info 'ConverterSession'] Converter data provider created.
2013-12-10T19:11:22.235+01:00 [06068 info 'DiagnosticDataProvider'] Converter::Client::Gui::Common::DiagnosticDataProvider::DownloadTaskDiagnosticFile - Using task converter.task.Task:task-5
2013-12-10T19:11:23.235+01:00 [06068 info 'DiagnosticDataProvider'] Converter::Client::Gui::Common::DiagnosticDataProvider::DoDownloadDiagnosticFile - Received bundle info (converter.DiagnosticManager.TaskLogBundleInfo) {
--> dynamicType = <unset>,
--> key = "task-5-diag-20131210173033-gpxwme.zip",
--> timeCreated = "2013-12-10T17:30:33.032778Z",
--> format = "zip",
--> content = (converter.DiagnosticManager.BundleContent) [
--> "workerLogs",
--> "serverLogs"
--> ],
--> size = 447190,
--> crc = -69986784,
--> }
Just created a from a local machine (Windows 8 ) using Vmware vCenter Converter Standalone 5.5.0 build 1362012 to a VMware Player 6.0.x vmx
But when i try to open it in VMware player 6.0.1 nothing happens, it opens and closes very quickly, with no error message. Any sugggestions ?
Hi Folks,
I am trying to use VMware Converter Standalone 5.5 for use with VMware Player and am not able to select Destination Type of my choice (I'd like to choose "VMware workstation or other VMware virtual machine" from the "Select destination type" drop-down menu.) Please see the image below where the drop-down menu is not there at all. Thanks for your help. Hai
for Linux p2v where these TCP port should be open 22, 443, 902 . In esxi server , vcenter server , Linux power on machine which we want to convert or where our standalone converter is installed . Can anybody help me for this.
We want p2v our Linux based power on physical machine .
Regards
Summary:
I am trying to migrate two VMware virtual machines from Linux VMware server 2.01 to a VMware infrastructure install running VMWare ESXi 5.1.0. When I try and use the Standalone converter to convert the VMware virtual machine to 5.1 I get the error "Unable to Obtain Hardware information for the selected machine". I have followed the various suggestions on how to deal with this issue and am still Unable to import the machines.
More info:
I have a Microsoft Windows Server 2003, Standard Edition (32-bit) server and a Microsoft Windows Server 2008 (32-bit) server VMWARE virtual Machine image I am trying to migrate.
To do this I shut the machines down and copied the entire machine folder from the Linux server to a Windows 2008 R2 enterprise machine.
I have then run the VMWARE standalone converter (by right clicking on it and running as administrator)
I have gone into "convert machine" and selected "VMware Workstation or other VMware virtual machine"
I have gone and selected the vmx file from the machine I wish to import
Upon selecting "View Source Details" and or "next" I get that error: "Unable to Obtain Hardware information for the selected machine"
I COULD run the Stand Alone importer on the machines however I would rather use the offline images. The import process changes all the hardware and the change in hardware means reapplying the windows license keys. Which means "what else is going on in the important software we use if windows is now thinking the hardware has changed THAT much?"
Hi,
I'm in dire need of this tool in order to inject some drivers into the cold clone disk. We have the cold disks from VMware but the ZIP file that contains the petool.exe app is missing and I can't locate it anywhere.
Is there someone out there that has a copy of it that they can pass on to me at all? I just need that small tool from the converter ZIP file, nothing else.
Please help!
Regards,
Hanré
Summary:
I am trying to migrate two VMware virtual machines from Linux VMware server 2.01 to a VMware infrastructure install running VMWare ESXi 5.1.0. When I try and use the Standalone converter to convert the VMware virtual machine to 5.1 I get the error "Unable to Obtain Hardware information for the selected machine". I have followed the various suggestions on how to deal with this issue and am still Unable to import the machines.
More info:
I have a Microsoft Windows Server 2003, Standard Edition (32-bit) server and a Microsoft Windows Server 2008 (32-bit) server VMWARE virtual Machine image I am trying to migrate.
To do this I shut the machines down and copied the entire machine folder from the Linux server to a Windows 2008 R2 enterprise machine.
I have then run the VMWARE standalone converter (by right clicking on it and running as administrator)
I have gone into "convert machine" and selected "VMware Workstation or other VMware virtual machine"
I have gone and selected the vmx file from the machine I wish to import
Upon selecting "View Source Details" and or "next" I get that error: "Unable to Obtain Hardware information for the selected machine"
I COULD run the Stand Alone importer on the machines however I would rather use the offline images. The import process changes all the hardware and the change in hardware means reapplying the windows license keys. Which means "what else is going on in the important software we use if windows is now thinking the hardware has changed THAT much?"
Hi.
I am trying to convert a machine based on CentOS 5.3 , I keep getting "kernel panic" on boot.
mount: could not find filesystem '/dev/root'
setuproot: moving /dev failed: No such file or directory
setuproot: error mounting /proc failed: No such file or directory
setuproot: error mounting /sys failed: No such file or directory
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: Attempted to kill init!-220000
I have followed the instructions on fixing this :
http://blog.edgoad.com/2010/03/vmware-no-volume-groups-found.html
but I still get "Kernel Panic"
I have re-installed the CentOS kernel but that didn't make any difference.
I have tried installing disk labels but that didn't make any difference.
I have tried VMware Standalone converter 5.5 and 5.0 with the same results.
I have confirmed the presence of /dev, /sys and /proc directories.
I have tried this : echo "DMRAID=no" > /etc/sysconfig/mkinitrd/noraid chmod 755 /etc/sysconfig/mkinitrd/noraid as suggested here :
http://tech.lanesnotes.com/2009/05/converting-physical-linux-system-to.html
I was advised to change the disks to IDE , but I can't see anyway to do this in ESXi 5.1 .
I'm at a loss at this point , I'm open to suggestions.
Here are my configs as shown when using a rescue disk and chroot into /mnt/sysimage
[root@localhost /]# cat /boot/grub/grub.conf
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 console=ttyS0,9600n8 console=tty0
# initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=5
#splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
# (removed by Converter) title Memtest86+ (1.65)
# (removed by Converter) root (hd0,0)
# (removed by Converter) kernel /memtest86+-1.65 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
title CentOS (2.6.18-128.7.1.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-128.7.1.el5 ro root=/dev/sdb1 rhgb quiet
# kernel /vmlinuz-2.6.18-128.7.1.el5 ro root=LABEL=/
initrd /initrd-2.6.18-128.7.1.el5.img
#title CustomKernel (2.6.18-128.7.1.el5)
# root (hd0,0)
# kernel /vmlinuz-2.6.18-128.7.1.el5 ro root=/dev/sdb1 rhgb quiet
# initrd /initrd-2.6.18-128.7.1.el5.img
[root@localhost /]#
[root@localhost /]# cat /boot/grub/device.map
(hd0) /dev/sda
(hd1) /dev/sdb
[root@localhost /]#
[root@localhost /]# cat /etc/fstab
/dev/sdb1 / ext3 defaults,noatime 1 2
#LABEL=/ / ext3 defaults,noatime 1 2
LABEL=/boot /boot ext3 defaults 1 2
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
[root@localhost /]#
[root@localhost /]# fdisk -l /dev/sda
Disk /dev/sda: 108 MB, 108134400 bytes
4 heads, 32 sectors/track, 1650 cylinders
Units = cylinders of 128 * 512 = 65536 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 2 1633 104448 83 Linux
[root@localhost /]# fdisk -l /dev/sdb
Disk /dev/sdb: 159.9 GB, 159921602560 bytes
143 heads, 28 sectors/track, 78008 cylinders
Units = cylinders of 4004 * 512 = 2050048 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 1 78009 156172288 83 Linux
[root@localhost /]#
[root@localhost /]# mount
/dev/sdb1 on / type ext3 (rw,noatime)
/dev/sda1 on /boot type ext3 (rw)
devpts on /dev/pts type devpts (rw)
tmpfs on /dev/shm type tmpfs (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
[root@localhost /]#
Thank you.
Hello everybody,
we are currently planning to move our VMs from our old Virtualisation Citrix XenServer to VMWare ESXi.
Under XenServer we have different types of machines running.
There are some Windows Server (which don't cause any trouble moving) and different Linux distributions.
There are some Debian (even Debian 4) and some Ubuntu 12.04 LTS.
We were able to migrate some of the Microsoft Machines without having trouble with VMWare Converter.
But migrating the linux machines we are having big issues.
Is there a guideline for doing that?
Does anyone have experiences in that topic?
Regards,
Christoph Borchert
I'm converting physical server to vSphere Hypervisor. It said: "Error: An error occurred during reconfiguration." after transfered all data.
I attached the Converter log file here and hope someone can help me to resolve this problem.
Hi folks,
when we try to install (as administrator) the actual converter on our windows 2003 std. 32 bit server (domain controller, 1 nic, fully ms patched) we always receive the following error:
Microsoft Visual C++ Runtime Error: program: ... vmware vcenter converter\vmware-converter.exe. The application has requested the Runtime to terminate it in an unusal way.
The eventlog says:
Product: VMware vCenter Converter Standalone -- Error 1920.Service VMware vCenter Converter Server (vmware-converter-server) failed to start. Verify that you have sufficient privileges to start system services.
We have tried to change temp / tmp enviroment, older converter versions, different installation path, changed service account, deleted tmp / registry entries ... Nothing helps !
Anyone got a solution for that ?
Best regards
Frank
I am trying to convert a windows 2003 32-bit server, I have done this many times before but this is the first time I'm having troubles.
Already tried 4 different converter versions (4.0, 4.3, 5.1, 5.5) but I keep having this problem:
I launch "convert machine", choose "this powered on machine", but when I try to proceed, after a couple of seconds it says "Unable to obtain hardware information".
I have attached the logs and viewed them myself, but I can't seem to discover what the problem is.
Already tried rebooting, restarting the services. I am logged on as administrator and also launched it "as administrator".
This is a local installation.
I have an old laptop running Ubuntu that I wish to convert to a virtual machine. I am running vCenter Converter Standalone version 5.5 on a Windows 8 physical machine.
Both the machines can ping each other, and I can effectively run a putty session with root privileges from the Window host. However I cannot get past the first page of the conversion wizard because when I press "next" button or "viev source details" i get a "operation not permitted" error message.
I have attached diagnostic export to this post.
Any hints?
