B
Brant
·Posted in ctrlX WORKS

Virtual Core could not start correctly.

A customer is trying to run the virtual core on his laptop but all failed. Every time he press the start button and about 10 seconds later, the virtual core will shut down and remind with error message:

"-monitor tcp: 127.0.0.1: 65000, server, nowait: Failed to bind socket: Input/output error"

 

Other information:

1. The ctrlX Works in installed directly in the laptop, not vertual machine.

2. The ctrlX Works version is 1.20.4.

3. Different Hardware Accsleration all tried but all could not start up. The virtual core will shut down in 10 seconds and with error message.

 

 

 

 

Best reply by FooFighter

Hello,

we recommend using the "Windows Hypervisor Platform" for Hardware Acceleration, because Intel does not support the HAXM Feature any more.

To turn on the "Windows Hypervisor Platform" run the command "optionalfeatures" in a cmd window and select the option "Windows Hypervisor Platform". Restart of the PC is needed.

The above mentioned error about the socket binding may be caused by a still running qemu process. To be shure not process is still running, try to stop all "qemu-system-x86_64.exe" (task manager /details). Then try to restart the virtual control.

Regards,

Oliver

View original
6 replies