In a 64-bit Windows VM with nesting enabled and operation mode "isolated core" (4 cores in Proxmox, 3 are for Windows and one for TwinCAT) the PLC can be started and runs without problems. However, this is exactly where the problem lies: ![]() 4-core CPU: Windows uses 3 Cores and TwinCAT uses the fourth).Īlso, this method is the only way to run TwinCAT in a 64-bit VM "shared core" is only available on 32-bit VMs. This "isolated" core can then be used exclusively by TwinCAT (e.g. In "isolated core"-mode, Windows is configured to use 1 core less than the CPU provides. With "shared core", TC shares a CPU core with Windows and both alternate in computing times. There are then two modes for operating TwinCAT: "shared core" or "isolated core". ![]() The most important requirement for 64-bit systems is access to the virtualization extension "VT-x". ![]() For those who are not familiar with TwinCAT: "The Windows Control and Automation Technology", TwinCAT, is the leading software for a soft-PLC that makes Windows real-time capable through a kernel extension. I am currently in the process of installing the TwinCAT runtime in a Windows 10-VM. Because these problems do not occur with a different hypervisor (vmware ESX or HyperV), I suspect that the problem is related to Proxmox, KVM and/or their implementation of nesting. I am experiencing some weird problems with TwinCAT (TC) in a Windows-VM.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
September 2023
Categories |