Connecting Cloud Innovators: Building Community at .NEXT 2024
I think the cause of the problem I posted is probably "Network interface is not in promiscuous mode". Although ESXi handles packets addressed to AHV, which is a virtual server of ESXi, packets destined for grandchild virtual servers such as CVM in AHV, if the physical interface is not set to promiscuous mode, It does not seem to receive it. In the environment we built this time, ESXi is not under my control, I am borrowing that virtual environment. Likewise, I think that it is impossible for many people borrowing a virtual environment to change the current environment only for me. So, unfortunately we can not confirm whether the above idea is correct, but my idea is probably not wrong. By the way, we were able to confirm only that the mode of the physical interface is "set promiscuous mode off."
I thought that I could solve it by specifying "E1000" made by Intel, but I could not connect other than arrowhead AHV.
I specified "VMXNET 3" for the network adapter. I re-installed Intel's "E1000" and reinstalled it, CVM can now communicate well.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.