Can we migrate the SCO unix server from physical server to esx vms?
thanks.
Can we migrate the SCO unix server from physical server to esx vms?
thanks.
Hi All,
Firstly, I am a newbie to VMware so apologies if I appear ignorant on the topic.
I am trying to create a VM of my local machine using VMWare vCenter Converter Standalone v5.0.0
Unfortunately I keep getting to 98% complete and it fails with the following status:
FAILED: Unable to create '\\.\vstor2-mntapi10-shared-31F59A9D00001000000000000F000000\$Reconfig$'
I have no idea what this message means. According to the log highlights it was "processing the reconfiguration datastore" at the time. I have exported the log file as per attached.
Can anyboby point me in the right direction?
Many thanks,
Paul.
Hi,
I am receving 'kernel panic' message after converting a Debian machine to our virtual infrastructure.
I've followed the below post to troubleshoot the kernel panic issue for a Centos machine. But this did not work for Debian.
Can someone please help me with this issue ?
Regards,
Nithin
when i right click a VM, and select export, i get a error as attached, i have install and enable the plugin, my vcenter installation directory is d:, does this matter?
Here is the setup ...
I have an Ubuntu VM's (Ubuntu 18.04 ) on a host called QNAS, that claims to be a VMDK format , we are trying to get our box off this host onto our new vSphere 6.5
When I ty to convert one of the VM it goes to the end and then returns:
FAILED: An error occurred during the conversion: 'GrubInstaller::InstallGrub: /usr/lib/vmware-converter/installGrub.sh failed with return code: 127, and message: FATAL: kernel too old Error running vmware-updateGrub.sh through chroot into /mnt/p2v-src-root Command:
chroot "/mnt/p2v-src-root" /vmware-updateGrub.sh "GRUB2" "(hd0)" "(hd0,1)" /vmware-device.map "grub2-install" '
Can anyone help me with this issue or have suggestions. I tried to manually move the VMDK form this host but VMware says if does nto recognize the VMDK format. QNAS point fingers at VMware of course.
Much obliged!
vmware convertor standalone version: 6.0.0-build 2716716
Source Linux server information:
xxxx:~ # cat /etc/issue
Welcome to openSUSE 13.2 "Harlequin" - Kernel \r (\l).
xxxx:~ # uname -a
Linux xxxx 3.16.7-29-desktop #1 SMP PREEMPT Fri Oct 23 00:46:04 UTC 2015 (6be6a97) x86_64 x86_64 x86_64 GNU/Linux
xxxx:~ # uname -r
3.16.7-29-desktop
xxxx:~ # dmidecode -t system
# dmidecode 2.12
SMBIOS 2.5 present.
Handle 0x0030, DMI type 1, 27 bytes
System Information
Manufacturer: IBM
Product Name: System x3650 M3 -[7945RFR]-
Version: 00
Converting stopped at progress 97% and followed by error and check converter exported logs by attachment:
FAILED: An error occurred during the conversion: 'GrubInstaller::InstallGrub: /usr/lib/vmware-converter/installGrub.sh failed with return code: 127, and message: FATAL: kernel too old Error running vmware-updateGrub.sh through chroot into /mnt/p2v-src-root /usr/lib/vmware-converter/installGrub.sh: line 147: /mnt/p2v-src-root:
Is a directory '
Vmware converter release notes have following statements for converter 6.2
Some Linux distributions have unsupported combinations of Linux kernel and grub loader.
Workaround: None. Use supported distributions only.
at link VMware vCenter Converter Standalone 6.2.0.1 Release Notes
Disscuss :
1 From the error, is it saying that the kenrnel of converter helper is older than source linux system ?
1) check converter helper kernal version: boot a virtual machine from ISO file from compuer on which converter is installed into default location C:\Program Files (x86)\VMware\VMware vCenter Converter Standalone6.0\converter-helper-vm-x64.iso
2) we see that the kernel of converter helper is much older than source linux server. 2.6.38 < 3.16.7
2) can we fix the failed converted linux system by re-install grub with orignal Linux server kernel-version ?
I did following steps but it did not work.
A boot the failed server from a live CD.
B after related file system is mounted and chroot,reinstall the grub2
grub2-mkconfig -o /boot/grub2/grub.cfg
grub2-install /dev/sda
C reboot the vm and vm starts endless circling bettwen "Grub loading" and restarting.
3) the same problem accured and check this aiticle.
4) Same suggestion is posted in Vmware p2v conversion error .
Hi I would like to ask for your assistance to what causes this issue that I encountered.
My Goal for doing this is to shrink the Hard disk size since some of the spaces on the VMWare is not being used and I wanted to used the spaces on that specific VM to other VM instance, I tried looking for a way to do this and found out about this VMware vCenter Converter Standalone. The issue is this one, when I try to perform configure machine and select the instances that I wanted to reconfigure I end up encountering an error "Reconfiguration is not supported for the selected source.
Kindly see the attached file of the issue I encountered. Your feedback will be highly appreciated. Thank you
I am P2Ving some HP machines and have read the posts here on how to remove most of the HP components but I am stuck on how to get rid of the HP network Configuration Utility program which puts the HP Network icon in the system tray. There is a post from Guillermo Musumeci back in 2007 that said using this command:
snetcfg.exe -v -u cq_cpqteam
should do it but I can't find snetcfg.exe on this server.
There is also a post from Jasemccarty in 2007 that said this keymay be the key you have to remove:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\
{4D36E975-E325-11CE-BFC1-08002BE10318}\{FD0FF0D6-4876-4894-9274-258564E35C07}
But that key doesn't appear to be in the registry on this server. Anyone have any ideas on how to remove this last bit of HP centric software from a P2V'd VM?
Anyone know why HP makes it so blasted difficult to remove their drivers and other components?
thanks,
Dan
There have been many complaints about transfer rate degradation in Converter 5.0.
Converter uses NFC (a proprietary VMware protocol) for cloning to managed destination. Security has been enhanced in Converter 5.0 by encrypting the data transfer. Unfortunately this has caused a more severe performance degradation than expected.
Switching off SSL encryption is a way to work around this issue. Here is how it is done:
I.e. it should look like:
... <nfc> <readTimeoutMs>120000</readTimeoutMs> <useSsl>false</useSsl> ...
converter 5.0 will crash when vcenter is upgraded to 5.1. Does anybody know any temp work around or fix? thanks
Hi, I'm on my 7th attempt at converting my second windows 2000 Advanced Server with latest converter 3.0.1 and consistently getting the error (see full log attached):
Image processing task has failed with MethodFault::Exception: sysimage.fault.OsVersionNotFound
I tried some of the usual tricks (the ones that worked on the 16th attempt for my first W2K server) including just convert C: and slightly reduce destination size to force a filewise clone (failed 97%)
In each case I end up with a VM on my ESX 3.0.2 server, but it Bluescreens on boot with "unable to find boot device"
thanks for any info/tips,
Fletcher
I'm starting the process of migrating a collection of VMs in a KVM environment to an existing vSphere cluster and am trying to use Converter (5.5) to do a live conversion/migration of an Ubuntu box, but it's failing due to create the virtual disk on one of hosts due to the SSL certificate, and I haven't found any other posts or articles specifically about this (seems like most SSL related items are about improving speed)
From the worker log, I can see that:
2014-08-07T09:35:13.947-07:00 [06620 warning 'Default'] [,0] SSL_IsVerifyEnabled: failed to read registry value. Falling back to default behavior: verification on. LastError = 0
2014-08-07T09:35:13.947-07:00 [06620 warning 'Default'] [,0] SSL: Unknown SSL Error
2014-08-07T09:35:13.947-07:00 [06620 warning 'Default'] [,0] SSL: connect failed
2014-08-07T09:35:13.947-07:00 [06620 warning 'Default'] [,0] [NFC ERROR] NfcNewAuthdConnectionEx: Failed to connect to peer. Error: The remote host certificate has these problems:
-->
--> * The host certificate chain is incomplete.
-->
--> * unable to get local issuer certificate
2014-08-07T09:35:13.947-07:00 [06620 info 'Default'] Sysimgbase_DiskLib_OpenWithPassPhrase failed with 'NBD_ERR_NETWORK_CONNECT' (error code:2338)
Is it possible to simply disable the certificate validation for this process? From the log, it sounds like there's a registry key that would control it, but I haven't found any information on it (or guessed it correctly). Or can I import that cert to the local Windows system running Converter to get around it (I haven't been successful with that approach yet either)
It's actually not clear to me which system is doing the validation. While the worker log states it connecting to the vSphere host, there is no such line indicating it's connecting to the host where the target VM is located, and it looks like that's the host with the certificate that is deemed invalid. Is the validation not happening on my local system that is running Converter? (the vCenter server settings shows that the "vCenter requires verified host SSL certificates" checkbox is unchecked already)
Thanks,
Scott
Hello VMware Community,
I need help with P2V Conversion.
I am running VCenter Converter Standalone 6.0 on My admin Windows 7 64 bit PC which is aVirtual machine. I am trying to convert a Physical machine on the Network. This PC is Windows 7 32 bit. I have done the following.
1. Disable UAC
2. Disable Firewall
3. Create a QWORD (64-bit) called LocalAccountTokenFilterPolicy, that worked for me when the DWORD would not allow access to my 64-bit machine. Set to 1 (number one).
4. Tried to Run VCenter in Administrator Mode
5. Verified under gpedit.msc that User Account Control: Run all administrator in admin approval mode is disabled.
The agent does install on the physical computer but I get the error of " Unable to obtain hardware information for selected machine." I removed the agent and tried to install the Converter locally on the physical machine and got the same error when trying to convert. I have also used 5.5.3 which gave the same error as well in both scenarios.
Attached are the log files. Please help.
Hi,
We need to migrate windows 2008 R2(64 bit) to vmware environment ,source VM is located in Xenserver.
While converting the process its shows as "Unable to obtain hardware information for the selected machine".I herewith attached diagnostic log for reference.
Kindly check and let me know what i will do for further proceed.
Version Details are given below
1.Vmware standalone conerter version is 6.0
2.VMware standard Edition 5.5 (Target Host)
3.Xenserver version 6.0.2 (Source Host)
Note : Previously i have converted MS Exchange server without any issues in same environment.
I have a brand new ESX server. Newest version of Vmware Converter. I ran the converter on my server (Windows 2003 standard sp1) which is my primary domain controller, DNS, DHCP, and file server. The conversion took about 3 hours and I had no errors. When I came in this morning I shut off the physical machine and started the VM. Active Directory would not load, it complained about SAM issues. I spent a couple hours and it rebuilt the AD indices 3 or 4 times and kept rebooting. Finally I was able to get it to boot and it installed a driver and rebooted. All went well after that but then the clients could not talk to the server. The time was off. I restarted the time service and the client's could browse network shares but they could not talk to our Exchange server. After 4 hours of down time they made me shut down the VM and hook up the physical server so they could work. Any ideas what I did wrong? I need to try to do this again tonight so we can finish this project.
Thanks for any help!
Lucas
Hi all,
We are using Vmware Converter Enterprise to migrate all the VMs on a standalone ESX 3.0.2 to an ESX 3.5 cluster, we got "unknown error" and in review the log, it said certificate is not valid.
When log on to VC, it was prompting that the cert is not valid:
**************
An untrusted SSL certificate is installed on "xxx.xx.xxx.xx" and secure
communicate cannot be guaranteed. Depending on your security policy, this
issue might not represent a security concern. You may need to install a
trusted SSL certificate on your server to prevent this warning from appearing.
The certificate received from "xxx.xx.xxx.xx" was issued for "unknown
hostname". Secure communication with "xxxx.xx.xxx.xx" cannot be guaranteed.
Ensure that the fully-qualified domain name on the certificate maches the
address of the server you are trying to connect to.
*************
Would this issue cause the conversion failure?
Could someone please help to explain and suggest a solution. Thanks.
I'm trying to convert a running linux vm to a vmware workstation vm.
I found out that i need a ESX Host. I installed a ESX Server.
While trying to connect to the ESX Host (from the VMware Converter) at the Step Target System (VMware Infrastructure-Server) I get an "SSL Exception: Unexpected EOF" error.
I tried already disableing SSL for the converter worker process.
Is there another way to convert a running linux vm to a vmware workstation vm?
If not, how can i fix the SSL error?
Regards
Christof
I have 2 file servers to convert. 1 is Win 2008 R2, one is Win 2012 R2. I've been asked to estimate the amount of time it will take to convert, and i have no way how to do that. I have the sizes of the machines to convert (1 is 500G, the other is a bit over 600G).
How would I make such an estimate? The standalone converted is block-based, right? Has nothing to do with the number or size of files on the servers, only the total size of the disks.
Each server would have 2x1G Ethernet NICs, teamed.
Anyone have any pointers on how to make such an estimate? 4 hours?
Converter v6.2, destination ESXi 5.5 U3b. ESXi has 2x10G NICs for VM traffic.
Hi Guys,
I am trying to virtualize Linux server, details below
Physical Linux Server: HP DL360G7
OS: RHEL release 5.7 (Tikanga)
IP Address: 10.88.0.100
It's been migrated to virtual environment, details below
vCenter server: 10.30.0.100
vCenter standalone server: 10.0.30.101
Firewall rules allow 10.0.33.101 to connect to port 22 on 10.88.0.100
I started the P2V process and it did started creating VM on virtual infrastructure. However, the progress kept sitting on 1%
By logging on the web interface of the virtual machine that shows on target vcenter server, it looks like;
Based on going through different forums, I configured the static IPv4 address to be on 10.88.0.* network. The physical server was able to communicate with the IP address assigned to this temp machine.
However with more than an hour in this process, it still shows progress as 1%.
Any ideas of what could be missing here or is this normal behaviour??
I am running Converter on Windows 7 ans trying to make a virtual machine of the current installation to upgrade to Windows 10.
Whenever I start to use the converter I get this error message "Unable to complete Converter agent installation on Dell-9020. Another version of this product is already installed.
I have looked around the machine and the only one I can find is the current installation.
Anyone any ideas. Thanks