sudo LD_LIBRARY_PATH=. ./vmware-sysinfo
Re: trying to convert P2V from RedHat 4.x to virtual but get error "Unable to query the live Linux source machine. "
Re: Standalone Converter P 2 V job is hanging at 1% in Linux
you can see above the output of netstat -nr
Re: trying to convert P2V from RedHat 4.x to virtual but get error "Unable to query the live Linux source machine. "
[root@EduService tmp]# sudo LD_LIBRARY_PATH=. ./vmware-sysinfo
Segmentation fault
Re: Standalone Converter P 2 V job is hanging at 1% in Linux
There is a switch in converter-worker.xml: useSourcePasswordInHelperVm - change it to true, (look at option powerOffHelperVm too) restart service and restart conversion.
As result you can log in helper vm as user in source machine.
Then do ping, traceroute, etc...
HTH
Re: Standalone Converter P 2 V job is hanging at 1% in Linux
where this helper VM reside it this an other VM or my source or my destination
really not getting any hint to proceed
Re: Standalone Converter P 2 V job is hanging at 1% in Linux
Please read the documentation about process overview VMware vCenter Converter Standalone User Guide
probably some question will not arrives after.
Re: trying to convert P2V from RedHat 4.x to virtual but get error "Unable to query the live Linux source machine. "
try this one: sudo LD_LIBRARY_PATH=. strace ./vmware-sysinfo
Re: trying to convert P2V from RedHat 4.x to virtual but get error "Unable to query the live Linux source machine. "
Also please check two things:
- if vmware-sysinfo.log exists - share its content (the finished tasks will help us to identify what task probably crashes)
- ensure you are using converter 6.2 and its components (because in the first your message converter 5.0 is mentioned)
Re: trying to convert P2V from RedHat 4.x to virtual but get error "Unable to query the live Linux source machine. "
its 6.2
added the vmware-sysinfo.log
Re: Standalone Converter P 2 V job is hanging at 1% in Linux
- Browse for the
converter-worker.xml
file.
Note: By default, the converter-worker.xml file is located at:- Windows 7 and 2008 Server – C:\ProgramData\VMware\VMware vCenter Converter Standalone
- Windows Vista, XP and 2003 Server – %ALLUSERSPROFILE%\VMware\VMware vCenter Converter Standalone
- In older Windows versions – %ALLUSERSPROFILE%\Application Data\VMware\VMware vCenter Converter Standalone
- Open the
converter-worker.xml
file in a text editor and change theuseSourcePasswordInHelperVm
flag fromfalse
totrue
. - Change the powerOffHelperVm flag from true to false .
- Save and close the converter-worker.xml file.
- Restart Converter Standalone Worker service.
I did all this but could not log in to the helper VM
I tried
root / password but not getting in the helper VM
even I assigned a new unique IP to helper VM but cloud not reach to default gateway even.
Re: trying to convert P2V from RedHat 4.x to virtual but get error "Unable to query the live Linux source machine. "
Very extreme case - in fact sysinfo crashes while attempt to enumerate network interfaces.
There is a good news - one of attempts succeeded and its output could be used to avoid problem with crashing.
The workaround is to strip successful output in separate XML file (sysinfo.xml for example), then add this file to vmware-sysinfo-lin32.tar.gz and also modify vmware-sysinfo.sh file - change the last line with: cat "$libdir"/sysinfo.xml Will be good to make a copy of original tar.gz file because your modified file must be with exact name "vmware-sysinfo-lin32.tar.gz" but will works only for this concrete machine. After you finish conversion restore the original file.
HTH
Re: Standalone Converter P 2 V job is hanging at 1% in Linux
The helper VM is the destination VM. How did you connect to it? Is it using vSphere client? I suppose you retried the conversion after restarting worker service. What is the the helper message when you try to login with root?
Re: Standalone Converter P 2 V job is hanging at 1% in Linux
I am able to connect to helper vm, I used the root user and password the same source machine has it
I am able to get inside now but when I assigned the IP address to helper VM I can't even login to default gateway
The physical linux i'm trying to convert use 10.200.24.33
My Converter server is 10.0.21.158
My ESX host is 10.200.24.101
vcenter is 10.0.22.147
I assigned IP to helper VM as
IP : 10.200.24.4
Mask " 255.255.255.0
Default Gateway 10.200.24.1
but when I login to Helper VM I can't even ping Default Gateway
Re: Standalone Converter P 2 V job is hanging at 1% in Linux
Are you sure set correct vLan for vM Helper ?
Re: Standalone Converter P 2 V job is hanging at 1% in Linux
Check the virtual network the helper VM is on. Does it have an uplink or Is it isolated? What is its VLAN? Where is the gateway and is it routed to that virtual network? Things like that.
If I understand correctly, the issue is not converter related.
Re: Standalone Converter P 2 V job is hanging at 1% in Linux
ok let me know what you want to know more about it so I can provide you, to get it done
Re: Standalone Converter P 2 V job is hanging at 1% in Linux
That's not what I mean. You need to provide connectivity from the destination VM to the source (SSH connection to be more specific).
How exactly the network is configured and what prevents the connection is not something easily done remotely (if at all). Better work with the network administrator of your datacenter (or whoever happens to perform that role).
Re: Cold Clone CD?
Hey Axel, not sure if you were able to solve this issue, but I was able to clone a super old baremetal Linux server using Clonezilla.
- Booted from CloneZilla to clone the baremetal drive to an image, which I transferred to a USB drive.
- Created a new VM in VMware.
- Booted that VM from CloneZilla, and used the restore mode to restore the image in the VM.
Worked like a charm. Couple issues you may or may not run into:
- "VFS: Cannot open root device "LABEL=/" or unknown-block(0,0)" during startup.
- I was able to overcome this by changing the virtual disk's adapter type within VMware from SCSI to IDE.
- "can't get IP address" during startup.
- I overcame this by changing the network adapter type within VMware from "Flexible" to "E1000".
Good luck!
Re: Cold Clone CD?
One more thing:
I had another issue with the VM booted from CloneZIlla not detecting the USB drive mounted on my own machine, most likely since CloneZilla's lack of VMware Tools prevents that abstraction from working. I was able to get the VM to see the image by transferring my image to an NFS share, and luckily CloneZilla provided an option to browse an NFS share for images.
Re: VMConvertor fails at approx 97%
I am also having the same problem, fails at 97%
OS - Windows 2008 R2
VMconverter version - 6.5
Pointing directly to esxi host
Ran chkdsk /r /f
Tried removing the nics and replicate
re-registered vss
Tried pointing to different esxi hosts
Everytime, it fails exactly at 97%.......
Here is the error what i found....
Converter::Server::Scheduler::SimpleScheduler::Run(void) ("d:/build/ob/bora-8466193/bora/sysimage/ufad/server/scheduler/simpleScheduler.cpp:109")
2018-11-25T20:43:16.776-06:00 info vmware-converter-server[03816] [Originator@6876 sub=Default] Connecting to host 10.100.34.50 on port 443
2018-11-25T20:43:16.776-06:00 info vmware-converter-server[03816] [Originator@6876 sub=Default] localVersion is: vim.version.version10
2018-11-25T20:43:16.792-06:00 info vmware-converter-server[03816] [Originator@6876 sub=Default] Remote version is: unrecognized
2018-11-25T20:43:16.792-06:00 info vmware-converter-server[03816] [Originator@6876 sub=Default] Authenticating user administrator@hanon.seo
2018-11-25T20:43:16.870-06:00 info vmware-converter-server[03816] [Originator@6876 sub=Default] ComputeResource for vim.HostSystem:host-35 is vim.ClusterComputeResource:domain-c561
2018-11-25T20:43:16.870-06:00 info vmware-converter-server[03816] [Originator@6876 sub=Default] ResourcePool for vim.ComputeResource:domain-c561 is vim.ResourcePool:resgroup-562
2018-11-25T20:43:16.870-06:00 info vmware-converter-server[03816] [Originator@6876 sub=Default] Reusing existing VIM connection to 10.100.34.50
2018-11-25T20:43:16.885-06:00 info vmware-converter-server[03816] [Originator@6876 sub=Default] Scheduled timer canceled, StopKeepAlive succeeds
2018-11-25T20:43:16.901-06:00 info vmware-converter-server[01724] [Originator@6876 sub=ThreadPool] Thread enlisted
2018-11-25T20:43:16.901-06:00 info vmware-converter-server[03816] [Originator@6876 sub=Default] Started task "task-145" for job="job-35", item ="151" -- void __thiscall Converter::Server::Job::JobProcessorImpl::StartProcessingJobs(void) ("d:/build/ob/bora-8466193/bora/sysimage/lib/converter/server/job/jobProcessorImpl.cpp:384")
2018-11-25T20:43:16.901-06:00 info vmware-converter-server[03848] [Originator@6876 sub=Libs] [ADS] GetTokenInformation failed: 1312
2018-11-25T20:43:16.917-06:00 info vmware-converter-server[01724] [Originator@6876 sub=Default] [task,338] [task-145] -- BEGIN -- Convert
2018-11-25T20:43:17.213-06:00 info vmware-converter-server[01724] [Originator@6876 sub=Default] [taskSpec,620] [task-145] [TaskMap] task-145:task-52
2018-11-25T20:52:53.674-06:00 error vmware-converter-server[01724] [Originator@6876 sub=Default] [task,350] [LRO] Unexpected Exception: vmodl.fault.SystemError
2018-11-25T20:52:53.674-06:00 info vmware-converter-server[01724] [Originator@6876 sub=Default] [task,379] [task-145] -- ERROR -- Convert: vmodl.fault.SystemError
--> (vmodl.fault.SystemError) {
--> faultCause = (vmodl.MethodFault) null,
--> reason = "InternalError",
--> msg = ""
--> }
2018-11-25T20:52:53.674-06:00 info vmware-converter-server[01724] [Originator@6876 sub=Default] [diagnosticManager,265] Retrieved taskInfo for "converter.task.Task:task-145" mapping it to "converter.task.Task:task-145".
2018-11-25T20:52:53.674-06:00 info vmware-converter-server[01724] [Originator@6876 sub=Default] [diagnosticManager,305] The task with id = "task-145" was found to be a "recent" task.
2018-11-25T20:52:53.674-06:00 info vmware-converter-server[01724] [Originator@6876 sub=Default] [diagnosticManager,319] No existing log bundle found for task with id = "task-145". The task is still "recent" so a log bundle will now be generated for it.
2018-11-25T20:52:53.674-06:00 info vmware-converter-server[01724] [Originator@6876 sub=Default] [diagnosticManager,1097] Retrieving task related diagnostics for server task with id = "task-145".
2018-11-25T20:52:53.674-06:00 info vmware-converter-server[03940] [Originator@6876 sub=Default] Run 7 of job "job-35" finished with an error. -- struct Converter::Server::Job::JobExecutor::SchedulerUpdateSpec __thiscall Converter::Server::Conversion::ConversionJobExecutorImpl::UpdateJob(class Converter::Server::Job::InternalJob &,bool,const class Converter::Server::Scheduler::SchedulerItemStatistics &,const class Converter::Task::TaskInfo &) ("d:/build/ob/bora-8466193/bora/sysimage/lib/converter/server/conversion/conversionJobExecutorImpl.cpp:405")
2018-11-25T20:52:53.690-06:00 info vmware-converter-server[03940] [Originator@6876 sub=Default].h Removing scheduler item (151) for job (job-35) -- void __thiscall Converter::Server::Job::JobProcessorImpl::ProcessJobUpdateCommand(const struct Converter::Server::Job::JobExecutor::SchedulerUpdateSpec &,const class Vmacore::Ref<class Converter::Server::Job::InternalJob> &,class Converter::Server::Scheduler::SchedulerItem &,const int &,class Converter::VdbConnection &) ("d:/build/ob/bora-8466193/bora/sysimage/lib/converter/server/job/jobProcessorImpl.cpp:1330")
Not able to find any help on this..... logged a case with vmware as well, but still no proper update from them as its been 1 month now.....