On Tue, 22 Dec 2015 22:41:34 +0200 Shmulik Ladkani
wrote:
> Could it be that various other error codes might be returned from ESXi
> for a VMXNET3_CMD_ACTIVATE_DEV read, depending on device condition?
Thinking this over, the commit takes us one step into a finer device
implementation, and we can
Hi,
On Mon, 21 Dec 2015 22:18:21 -0800 Miao Yan wrote:
> When reading device status, 0 means device is successfully
> activated and 1 means error.
>
> This behavior can be observed by the following steps:
>
> 1) run a Linux distro on esxi server
> 2) modify vmxnet3 Linux driver to give it an in
When reading device status, 0 means device is successfully
activated and 1 means error.
This behavior can be observed by the following steps:
1) run a Linux distro on esxi server
2) modify vmxnet3 Linux driver to give it an invalid
address to 'adapter->shared_pa' which is the
shared memory
