You can use older Converter, should not be a problem with RHEL7. (If you experience such problem of course, you need to test)
There is no general solution for this - some *nix complains about empty statement i.e. just comment, others complains about empty operator i.e. colon..
Unfortunately some combinations of kernel version and grub version produces this result. That's why we lists "supported OS".
There is no solution currently and you need to convert your Linux manually.
HTH
Do you happen to know where's the list of supported combinations? And which kernel is too old? On the source system?
Do you have /tmp folder with enough rights?
It's about kernel of HelperVM and your grub version.
Thanks.
I see there's no SLES 12 on the list, only SLES 10 and 11.
SLES12 was released in 2014 while SP1 was end of 2015 so it is not that new...
Okay, thanks for the help. I appreciate it.
Hello all,
I am having trouble converting some old hyper-v virtual machines to our new vcenter 6.5. ( offline V2V )
First issue I encountered:
[NFC ERROR] NfcNetTcpWrite: bWritten: -1
[NFC ERROR] NfcSendMessage: send failed: NFC_NETWORK_ERROR
[NFC ERROR] NfcFssrvr_Close: failed to send close message
[NFC ERROR] NfcNetTcpWrite: bWritten: -1
[NFC ERROR] NfcSendMessage: send failed: NFC_NETWORK_ERROR
At first I thought this was network related, but after some googling I found out this is rather a problem that occurs when trying to migrate VMs with multiple disks. I also have to mention I have already migrated 2 Hyper-V VMs successfully, so it can't be network related.
I have already done several things:
- Trying to convert disk per disk
- Trying to do file level cloning instead of block level cloning by taking a destination disk with a little less space
- ran chkdsk /f on the disks I wanted to convert, to make sure the .vhd's were not faulty
- Installed the Converter agent on the Hyper-V server aswell as on the source machines
- Other minor stuff
When chosing block level cloning the conversion always stops at 1%:
BlockLevelVolumeCloneMgr::CloneVolume: failed with exception BlockLevelVolumeCloneMgr::CloneVolume: Detected a write error during the cloning of volume >)63060.0000056000000000. Error: 37409 (type: 1, code: 2338)
---> SEE LOGS ATTACHED vmware-converter-agent-1.log
When I go for file level cloning disk per disk I get to 38% tot 39% and there under Conversion Status I get the following:
"FAILED: A general system occured: Can not connect because the destination computer has actively refused the connection" ( this is a translation from dutch, since I am receiving the message in dutch )"
It seems like at this stage the the connection gets lost, also on my Hyper-V Server I can see the VMWare Converter Agent service has stopped , can also see this in event viewer --> Service Terminated unexpectedly.
I can see messages like this in the vmware-converter-server logs:
Failed to read request; stream: <io_obj p:0x01396dbc, h:-1, <pipe '\\.\pipe\vmware-converter-server-soap'>, <pipe '\\.\pipe\vmware-converter-server-soap'>>, error: class Vmacore::TimeoutException(Operation timed out)
--> SEE LOGS ATTACHED: vmware-converter-server-3.log
Please advise, I need to migrate these servers for a customer and have already lost countless days before coming here.
Kind regards,
Toon
Check if port 443 of vCenter is reachable from workstation you are running converter on. That is required if your'e setting vCenter as a target.
Hello vijayrana,
Thanks for quick response. I can telnet from the workstation to the vcenter over port 443
Two things: if agent is crashed then dmp file could be found in logs folder - could you upload it? Next - what's the difference with your successful conversions? version, destination, source, etc.
From the log - all looks like network error. By the way in 6.5 only TLS1.1 & TLS1.2 protocols are supported, and this could be the problem with connections (just a wild guess).
Hello POCEH,
Can not find a seperate dump file when I export the logs from the VMware Converter job. Or should I look somewhere else?
Now that I'm thinking, the 2 succesfull conversions happened on the same Hyper-V host. The other ones, which failed, are indeed located on another server.
--> However I do not see any differences between the two net work wise.
For dmp files look in %ALLUSERSPROFILE%\VMware\VMware vCenter Converter Standalone\logs folder.
Something must be different between HyperV hosts, the networking is very complex area. Also I see McAfee running, could you stop and check again, and ensure your user xxx\administrator is also an administrator in HyperV host.
HTH
Hi Poceh,
Unfortunately, also no dmp files found in there. I am running the tests with the Domain Admin account, which is ofcourse also in the Administrator groups on all Hyper-V hosts. I will try running again with McAfee stopped.
Could it be of any help if I post the ipconfig /all of the working + non-working Hyper-V host + Network settings in Hyper-V?
Could you just search vmware-*.dmp on your system disk?
The ip settings will not help me for problem identification unfortunately, also there could be some problem, like switch or similar, between two points of connection (HyperV <-> ESX)
Try to compare settings between working and not working environment by yourself.
HTH
vijayrabha were you able to perform your P2V while using Windows Server 2008 R2 with VMware Converter on a Domain Controller after? How did you fix the error you were experiencing with VSS?
FAILED: Unable to create a VSS snapshot of the source volume(s). Error code: 2147754753 (0x80042301)
Hello All,
I am trying to migrate Redhat 6 from Physical to VMWare 6.5 using P2V tool.
But, Migration gets to 97% complete, and fails with the following error;
FAILED: An error occurred during the conversion: 'KeepOneBootEntry:
There is no matching kernel modules for kernel /tboot.gz'
Please suggest me.
Hi,
Try the steps in the attached link and hopefully it will fix your issue.
P2V - Convert Linux with RAID to VM - My Tech Notes and Projects
Hi!
I am trying to convert a physical 18.04 ubuntu server into a vm running on my single esxi 6.7 host (free license). I am, like a lot of people, running into problems when the converter reaches 97% and fails to install the GRUB boot loader.
I tried reading a lot of posts and tried configuring the GRUB boot loader, mount points in fstab and initrd by myself after the failed conversion, but I am not that tech savvy and it didn't turn out great.
Converting ubuntu 16.04 works great, and the Converter seems like a great tool. I am wondering if there are any plans or maybe people are working at this moment to support newer versions of linux, like ubuntu 18.04?
//Gustav
There are a couple folks from the Converter team that may see this and respond, but generally I ask the question: Why are you installing OSs of modern vintage only to turn around and convert them later? At this point in the game, that should probably be unnecessary and conversion is really just a legacy concept and only for corner cases.
Sorry, by "OSs of modern vintage", do you mean installing a modern OS on a physical machine? I received an old NUC from a friend and decided to run a web- and ftpserver on it, and now I want to move that machine to a more modern solution.