Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 258290

Re: Vagrant/Virtualbox Migrated machine doesn't work: Error: Unknown Error

$
0
0

Unfortunately that isn't it. I checked the .vmx and I don't have any shared folder entries at all -- they seem to be added at run time by vagrant perhaps?

 

Regardless of vagrant however, when I just run the 'vmrun' commmand without vagrant I still get the error.

 

I've also logged into the VM and re-ran vmware-config-tools and that ran without errors..

 

Looking at my vmware.log file during the boot up process I see this:

 

2019-02-07T14:06:40.421-05:00| vmx| I125: GuestRpcSendTimedOut: message to toolbox timed out.

2019-02-07T14:06:50.334-05:00| vcpu-1| I125: Guest: toolbox: Version: build-562307

2019-02-07T14:06:50.334-05:00| vcpu-1| W115: GuestRpc: application toolbox, changing channel 65535 -> 0

2019-02-07T14:06:50.334-05:00| vcpu-1| I125: GuestRpc: Channel 0, guest application toolbox.

2019-02-07T14:06:50.334-05:00| vcpu-1| I125: DEPLOYPKG: ToolsDeployPkg_Begin: state=0 err=0, msg=null

2019-02-07T14:06:50.334-05:00| vcpu-1| I125: Tools: [AppStatus] Last heartbeat value 0 (never received)

2019-02-07T14:06:50.368-05:00| vcpu-1| I125: Tools: Changing running status: 0 => 2.

2019-02-07T14:06:50.368-05:00| vcpu-1| I125: Tools: [RunningStatus] Last heartbeat value 0 (never received)

2019-02-07T14:06:50.368-05:00| vcpu-1| I125: Tools: Removing Tools inactivity timer.

2019-02-07T14:06:50.369-05:00| vcpu-1| I125: TOOLS Received tools.set.version rpc call, version = TOOLS_VERSION_UNMANAGED, type is unknown

2019-02-07T14:06:50.369-05:00| vcpu-1| I125: TOOLS Setting toolsVersionStatus = TOOLS_STATUS_UNMANAGED

2019-02-07T14:06:50.369-05:00| vcpu-1| I125: Tools_SetVersionAndType did nothing; new tools version (2147483647) and type (0) match old Tools version and type

2019-02-07T14:06:50.385-05:00| vcpu-10| I125: TOOLS state change 3 returned status 1

2019-02-07T14:06:50.385-05:00| vcpu-10| I125: Vix: [mainDispatch.c:4150]: VMAutomationReportPowerStateChange: Reporting power state change (opcode=2, err=0).

2019-02-07T14:06:50.385-05:00| vcpu-10| I125: Tools: Changing running status: 2 => 1.

2019-02-07T14:06:50.385-05:00| vcpu-10| I125: Tools: [RunningStatus] Last heartbeat value 0 (never received)

2019-02-07T14:06:50.385-05:00| vmx| I125: SOCKET 36 (254) recv detected client closed connection

2019-02-07T14:06:50.385-05:00| vmx| I125: Vix: [mainDispatch.c:2828]: VMAutomation: Connection Error (4) on connection 33.

2019-02-07T14:06:52.589-05:00| vmx| I125: SOCKET 37 (255) recv detected client closed connection

2019-02-07T14:06:52.589-05:00| vmx| I125: Vix: [mainDispatch.c:2828]: VMAutomation: Connection Error (4) on connection 34.

2019-02-07T14:06:54.799-05:00| vmx| I125: SOCKET 38 (256) recv detected client closed connection

2019-02-07T14:06:54.799-05:00| vmx| I125: Vix: [mainDispatch.c:2828]: VMAutomation: Connection Error (4) on connection 35.


Viewing all articles
Browse latest Browse all 258290

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>