Hello,

My auditor requests me to fix vulnerabilities CVE-2019-5518 and CVE-2019-5519 discovered on ESXi after execution recently the IVA (internal vulnerability assessments) sacn.

I already have the last build 15256549 for ESXi 6.5.0 and the last build 15160138 for ESXi 6.7.0 that normally fixes all of those CVE since April 2019 from older build at that moment.

My update manger indicate also that I have the last compliant patches.

Please, how can I insure that all of those vulnerabilities are fixed ? and if no, does this mean that I should do some setting on VMs under ESXi?  

Kind Regards,

2020-01-21T12:57:48.558Z cpu1:67919)MemSched: 14635: Admission failure in path: adaptec_storage/sfcb-ProviderMa.67917/uw.67917

2020-01-21T12:57:48.558Z cpu1:67919)MemSched: 14642: uw.67917 (13087) extraMin/extraFromParent: 736/736, adaptec_storage (11922) childEmin/eMinLimit: 17730/17920

2020-01-21T12:57:48.558Z cpu1:67919)MemSched: 14635: Admission failure in path: adaptec_storage/sfcb-ProviderMa.67917/uw.67917

2020-01-21T12:57:48.558Z cpu1:67919)MemSched: 14642: uw.67917 (13087) extraMin/extraFromParent: 768/768, adaptec_storage (11922) childEmin/eMinLimit: 17730/17920

2020-01-21T12:57:48.558Z cpu1:67919)MemSched: 14635: Admission failure in path: adaptec_storage/sfcb-ProviderMa.67917/uw.67917

2020-01-21T12:57:48.558Z cpu1:67919)MemSched: 14642: uw.67917 (13087) extraMin/extraFromParent: 768/768, adaptec_storage (11922) childEmin/eMinLimit: 17730/17920

2020-01-21T12:57:58.567Z cpu6:67919)MemSched: 14635: Admission failure in path: adaptec_storage/sfcb-ProviderMa.67917/uw.67917

2020-01-21T12:57:58.567Z cpu6:67919)MemSched: 14642: uw.67917 (13087) extraMin/extraFromParent: 736/736, adaptec_storage (11922) childEmin/eMinLimit: 17730/17920

2020-01-21T12:57:58.567Z cpu6:67919)MemSched: 14635: Admission failure in path: adaptec_storage/sfcb-ProviderMa.67917/uw.67917

2020-01-21T12:57:58.567Z cpu6:67919)MemSched: 14642: uw.67917 (13087) extraMin/extraFromParent: 768/768, adaptec_storage (11922) childEmin/eMinLimit: 17730/17920

2020-01-21T12:57:58.567Z cpu6:67919)MemSched: 14635: Admission failure in path: adaptec_storage/sfcb-ProviderMa.67917/uw.67917

2020-01-21T12:57:58.567Z cpu6:67919)MemSched: 14642: uw.67917 (13087) extraMin/extraFromParent: 768/768, adaptec_storage (11922) childEmin/eMinLimit: 17730/17920

2020-01-21T12:57:58.567Z cpu6:67919)MemSched: 14635: Admission failure in path: adaptec_storage/sfcb-ProviderMa.67917/uw.67917

2020-01-21T12:57:58.567Z cpu6:67919)MemSched: 14642: uw.67917 (13087) extraMin/extraFromParent: 736/736, adaptec_storage (11922) childEmin/eMinLimit: 17730/17920

2020-01-21T12:57:58.567Z cpu6:67919)MemSched: 14635: Admission failure in path: adaptec_storage/sfcb-ProviderMa.67917/uw.67917

2020-01-21T12:57:58.567Z cpu6:67919)MemSched: 14642: uw.67917 (13087) extraMin/extraFromParent: 768/768, adaptec_storage (11922) childEmin/eMinLimit: 17730/17920

2020-01-21T12:57:58.567Z cpu6:67919)MemSched: 14635: Admission failure in path: adaptec_storage/sfcb-ProviderMa.67917/uw.67917

2020-01-21T12:57:58.567Z cpu6:67919)MemSched: 14642: uw.67917 (13087) extraMin/extraFromParent: 768/768, adaptec_storage (11922) childEmin/eMinLimit: 17730/17920

I am not sure where this is coming from but my vmkernel.log is flooded with this info, currently at 650MB and keep writing every few seconds.

Not sure hot to read this?

We've been having lots of issues with our HP Proliant's (Various Generations) loosing the path to the 8 GB internal SD cards where ESXi is loaded. Typically a reboot will correct this condition and sometime it requires re-seating the internal SD cards.

Once the host is rebooted it will typically pick up the SD card where ESXi is loaded and boot without issues. If not, we usually have our NOC reseat the SD cards.

When this happens the bootbank vmfs volume where ESXi resides becomes unavailable and shows up in red when running ls -la /bootbank

lrwxrwxrwx    1 root     root            49 Apr 10  2019 bootbank -> /vmfs/volumes/a7caa3ee-95aa4a08-2db1-7b6495be01fc

Here's our current ESXi info:

[root@vmesx004:/dev/disks] vmware -vl

VMware ESXi 6.5.0 build-8294253

VMware ESXi 6.5.0 Update 2

I've reviewed this KB2144283 and have updated the iLO from 2.3 to 2.61 but the same condition exist

VMware Knowledge Base

The only thing that changes is the iLO now shows this condition for the internal SD card.

At login screen: iLO Self-Test reports a problem with: Embedded Flash/SD-CARD. View details on Diagnostics page.

Controller firmware revision 2.09.00 Embedded media manager failed initialization

The above error points to this article: https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c04996097

As I mentioned I already updated the iLO to 2.61 and we usually never have to perform a NAND format. The reboot usually gets SD back online.

I've tried stopping and restarting USB arbitration service and then rescanning adapters but this didn't help.

Here's some output from the last few lines of vmkernel.log

Line 90: 2020-01-19T20:19:45.778Z cpu26:65897)ScsiPath: 6787: Path vmhba32:C0:T0:L0 could not be unclaimed from plugin, status Busy. Continue path unclaiming

Line 90: 2020-01-19T20:19:45.778Z cpu26:65897)ScsiPath: 6787: Path vmhba32:C0:T0:L0 could not be unclaimed from plugin, status Busy. Continue path unclaiming

Line 90: 2020-01-19T20:19:45.778Z cpu26:65897)ScsiPath: 6787: Path vmhba32:C0:T0:L0 could not be unclaimed from plugin, status Busy. Continue path unclaiming

Line 91: 2020-01-19T20:19:45.779Z cpu26:65897)WARNING: ScsiScan: 1925: Could not delete path vmhba32:C0:T0:L0

Here's some additional output if that helps.

[root@vmesx004:/dev/disks] ls -l ./mpx*

-rw-------    1 root     root     2008023040 Jan 21 22:32 ./mpx.vmhba32:C0:T0:L0

-rw-------    1 root     root       4161536 Jan 21 22:32 ./mpx.vmhba32:C0:T0:L0:1

-rw-------    1 root     root     262127616 Jan 21 22:32 ./mpx.vmhba32:C0:T0:L0:5

-rw-------    1 root     root     262127616 Jan 21 22:32 ./mpx.vmhba32:C0:T0:L0:6

-rw-------    1 root     root     115326976 Jan 21 22:32 ./mpx.vmhba32:C0:T0:L0:7

-rw-------    1 root     root     299876352 Jan 21 22:32 ./mpx.vmhba32:C0:T0:L0:8

I was debating on trying these commands next but wasn't sure if this would help and I don't want to risk impacting the production environment with running VM's.

esxcli system module set --enabled=false  --module=usb

esxcli system module set --enabled=true  --module=usb

Any ideas on if it's possible to get this vmhba32 dead path condition fixed without rebooting host or re-seating the SD cards?

For some reason this is plaguing a lot of our host and causing issues since we need to get maintenance windows to migrate VM's off to reboot the host.

Seems like we should be able to correct this without rebooting the host...???

Appreciate any insight or suggestions!

If we can find a fix or work-around this would save us a lot of grief!

Hey all,

I am trying to export a VM and everything goes well EXCEPT the .OVF file it has you download is empty.   When I say empty, I mean it is 1KB and contains nothing.  The file is completely empty.

I've done some testing and concluded that you cannot export a VM if the VM has a pcie-passthru.  This causes the .OVF file to be blank every single time.

Steps to replicate:

1. Create a VM
2. Attach a PCIE-Passthru
3. Export VM
4. Open up the .OVF file
5. .OVF file is empty - bug confirmed.

Is there a way we can get this fixed?  Or any fix you know about?

Thanks

Hi there,

I have two ESXi hosts (free Version 6.5) up and running for quite some time now. Everything is running smooth.

If SSHd is enabled on the ESXi hosts, I also can connet to then with ssh, there is no issue.

But if I'm already on the ESXi host in a shell, I cannot connect to any other host with ssh or scp.

ssh: connect to host XX.XX.XX.XX port 22: Connection timed out

This behaviour is the same for both of my ESXi hosts. SSHD on the remote hosts (where I want to connect to) is working fine, and I can connect to them from any other machine beside my two ESXi hosts.

Any clue from where this behaviour comes and how to fix it?

Regards,

Claude

Hello

I have several esxi servers in cluster. ESXi's version is 6.0u2.

I'm trying to configure sending syslog messages and faced the situation when it works in case of using udp syslog server and port 514.

I'm havingrsyslog server.

tcp doesn't work.

On the syslog server I can see via tcpdump that client and server can't establish a connection but there is no reason.

At the same time other linux server can send syslog messages to tcp syslog server successfully.

I guess the problem is in the blocked port 514 for incoming connections at the esxi's side, but I'm not sure.

I didn't like the method of adding additional rules to esxi firewall, it is rather complicated.

does anybody faced the same problem?

Hello everyone,

I would like ask you for an advise.

This is only about my home lab, so just simple one esxi host without vcenter.

I am also using Nakivo as backup solution for my lab thats running on QNAP.

So far they were both on same subnet running without issues.

This week I added a 10GB connection to both devices and have just direct cable connection between them.

From esxi and VMs on top of it I can reach the QNAP without problem (NFS, SMB, SSH).

Also from QNAP itself I can SSH to the ESXi host.

All this using the 10GB connection.

But when I add this host with a new IP to Nakivo It all behaves very weird.

I know Nakivo is using ports 902 and 443, but nothing is being blocked on esxi side.

The only message I receive in hostd logs on esxi is

Accepted password for user nakivo from 192.168.168.5

2019-04-09T20:15:32.268Z info hostd[2098603] [Originator@6876 sub=Vimsvc.ha-eventmgr opID=6eee63d1] Event 1208 : User nakivo@192.168.168.5 logged in as Java/1.8.0_181

2019-04-09T20:15:33.068Z info hostd[2098603] [Originator@6876 sub=Vimsvc.ha-eventmgr opID=6eee6459 user=nakivo] Event 1209 : User nakivo@192.168.168.5 logged out (login time: Tuesday, 09 April, 2019 08:12:27 PM, number of API invocations: 0, user agent: Java/1.8.0_181)

2019-04-09T20:15:36.182Z info hostd[2099204] [Originator@6876 sub=Solo.Vmomi opID=6eee636e user=nakivo] Activation [N5Vmomi10ActivationE:0x00000098031a9820] : Invoke done [retrieveContents] on [vmodl.query.PropertyCollector:ha-property-collector]

2019-04-09T20:15:36.182Z verbose hostd[2099204] [Originator@6876 sub=Solo.Vmomi opID=6eee636e user=nakivo] Arg specSet:

--> (vmodl.query.PropertyCollector.FilterSpec) [

-->    (vmodl.query.PropertyCollector.FilterSpec) {

-->       propSet = (vmodl.query.PropertyCollector.PropertySpec) [

-->          (vmodl.query.PropertyCollector.PropertySpec) {

-->             type = "vim.HostSystem",

-->             all = false,

-->             pathSet = (vmodl.PropertyPath) [

-->                "config"

-->             ]

-->          }

-->       ],

-->       objectSet = (vmodl.query.PropertyCollector.ObjectSpec) [

-->          (vmodl.query.PropertyCollector.ObjectSpec) {

-->             obj = 'vim.HostSystem:ha-host',

-->             skip = false,

-->             selectSet = <unset>

-->          }

-->       ],

-->       reportMissingObjectsInResults = <unset>

-->    }

--> ]

2019-04-09T20:15:36.182Z info hostd[2099204] [Originator@6876 sub=Solo.Vmomi opID=6eee636e user=nakivo] Throw vmodl.fault.SystemError

2019-04-09T20:15:36.182Z info hostd[2099204] [Originator@6876 sub=Solo.Vmomi opID=6eee636e user=nakivo] Result:

--> (vmodl.fault.SystemError) {

-->    faultCause = (vmodl.MethodFault) null,

-->    faultMessage = <unset>,

-->    reason = "System exception while trasmitting HTTP Response:

--> error id = 32

--> "

-->    msg = ""

--> }

2019-04-09T20:15:36.182Z error hostd[2099204] [Originator@6876 sub=Default opID=6eee636e user=nakivo] Failed to send response to the client: Data already transmitted; cannot reset.

I am sure there is no blocking, network is setup correctly.

The thing I am not sure about is how in general esxi works with 2 management interfaces.

I would be very glad if you have any suggestions.

BR,

Jan

Hello,

I am relatively new to VMWARE.

I have "inherited" a network with 30 VMs, all of them running Windows Server 2016.

One of them is a file server with a 1.4TB pre-allocated disk. I want to extend the disk by 1TB (2.4TB in total) but the "increase capacity" is turned off.

How can I solve this?

TIA for the assistance.

Ariel M

Hello,

I ordered a server yesterday from OVH with the NVME 480GB * 2 SSD option instead of conventional hard drives.

My problem is that I can only create one datastore.

Unable to create a datastore on the disk where ESXI is installed.

Or I can do this by deleting the automatically created VMFS partition, except that the host becomes unstable then.

How then is it possible to use the available space of the two disks?

Thank you in advance for your help.

Hello everyone!

Is there a way to list all VMs (including powered off) directly from the host via ssh? Like "vim-cmd vmsvc/getallvms" or "esxcli vm process list" but for every vm on the host? I know about PowerCLI and its get-vm commandlet but It would be better for me to fetch vms right from the host. Thank you in advance!

I use FreeNAS 11.2 to make iSCSI disk share.

The esxi's version that I use is 6.7 update2.

When I use the FreeNAS iSCSI disk to create VMFS6 datastore,error occured.

This is error details.

Unable to create Filesystem, please see VMkernel log for more details: Failed to create VMFS on device naa.6589cfc00000022d3b9872e459f4b72c:4

However，I use the same FreeNAS iSCSI disk to create VMFS5 datastore，everything is OK.

I really don't know why,please help,thank you.

Is there any way to enable maintenance mode on a standalone esxi host via SOAP/REST call?

I believe I can connect to a powercli host and do do this so I'm thinking there must be a way to do it.

Anyone know the secret?

Hello,

I finally have gotten our new ESXi 6.7 to find the iSCSI target in our network.  It looks like I can create a datastore now, but I'm concerned that the iSCSI target shows the ESXI host's IP address (x.x.x.6) in its connection properties, not the VMKernel NIC IP (x.x.x.47), as I expected.  The iSCSI target is on a Synology NAS box.

There are 4 physical NICs:
vmnic0
vmnic1
vmnic2
vmnic3

There are 2 virtual switches:
vSwitch0 - (Management Network & VM Network) vmnic0, vmnic1

vSwitch1 - (iscsi) vmnic2, vmnic3

There are 2 VMKernel NICs:

vmk0 - Management Network portgroup, x.x.x.6

vmk1 - iscsi portgroup, x.x.x.47

The iSCSI Software Adapter, vmhba64, successfully found the target (x.x.x.80).  It reports "No port bindings."  Is that a problem?

Does anyone know why the iSCSI target is showing the host IP, x.x.x.6 and not the vmk1 IP, x.x.x.47?  Let me know if you need more information.

Thanks,
-Stacey-

Hi!

I have Dell server with 10G interface configured with Nic Teaming with Two HP Flexfabric acting as one via IRF. I am configured Bridge aggregation on HP side.

interface Bridge-Aggregation 20

port link-type trunk

port trunk permit vlan 1 110 321 202

I am specifying VLAN option on VMWARE side to 110. If I remove the VLAN option on Vmware and then change my config to below then I cannot connect to it. I want to have vlan 110 as untagged which I beleive is better way to connect to management VLAN.

interface Bridge-Aggregation 20

port link-type trunk

port trunk permit vlan 1 321 202

port trunk pvid vlan 110

Nic Teaming:

Notify switches

Yes

Policy

Route based on IP hash

Reverse policy

Yes

Failback

Yes

Just want to confirm if this setup is ok or untagging the management vlan is better option and how can I achieve that?

Thanks

Dear VMWare Community,

I have serious trouble with Windows 2016/2019 VM guests on ESXi 6.7. Every 3,4,5 days several VMs are unresponsible and hang. The only way to bring the VM back to life is the reset. The log is clean. I seems that the VM hangs without any error and the VMWare tools are unavailable.

2019-03-10T19:02:44.185Z| vcpu-3| I125: CDROM: Emulate GET CONFIGURATION RT 1 starting feature 0

2019-03-10T19:32:44.507Z| vcpu-2| I125: CDROM: Emulate GET CONFIGURATION RT 1 starting feature 0

2019-03-10T20:02:44.827Z| vcpu-4| I125: CDROM: Emulate GET CONFIGURATION RT 1 starting feature 0

2019-03-10T20:32:45.146Z| vcpu-2| I125: CDROM: Emulate GET CONFIGURATION RT 1 starting feature 0

2019-03-10T21:02:45.472Z| vcpu-3| I125: CDROM: Emulate GET CONFIGURATION RT 1 starting feature 0

2019-03-10T21:32:45.790Z| vcpu-4| I125: CDROM: Emulate GET CONFIGURATION RT 1 starting feature 0

2019-03-10T21:37:58.652Z| vmx| I125: GuestRpc: Got RPCI vsocket connection 270003, assigned to channel 1.

2019-03-10T21:37:59.654Z| vmx| I125: GuestRpc: Got error for channel 1 connection 270004: Remote disconnected

2019-03-10T21:37:59.654Z| vmx| I125: GuestRpc: Closing channel 1 connection 270004

2019-03-10T21:50:26.983Z| vmx| I125: GuestRpcSendTimedOut: message to toolbox timed out.

2019-03-10T21:50:39.976Z| vcpu-0| I125: Tools: Tools heartbeat timeout.

2019-03-10T21:50:39.976Z| vcpu-0| I125: Tools: Running status rpc handler: 1 => 0.

2019-03-10T21:50:39.976Z| vcpu-0| I125: Tools: Changing running status: 1 => 0.

2019-03-10T21:50:46.987Z| vmx| I125: GuestRpcSendTimedOut: message to toolbox timed out.

2019-03-10T21:50:46.987Z| vmx| I125: GuestRpc: app toolbox's second ping timeout; assuming app is down

2019-03-10T21:50:46.988Z| vmx| I125: GuestRpc: Reinitializing Channel 0(toolbox)

2019-03-10T21:50:46.988Z| vmx| I125: GuestMsg: Channel 0, Cannot unpost because the previous post is already completed

2019-03-11T00:24:50.221Z| vmx| I125: GuestRpc: Got RPCI vsocket connection 280003, assigned to channel 1.

2019-03-11T00:24:51.221Z| vmx| I125: GuestRpc: Got error for channel 1 connection 280004: Remote disconnected

2019-03-11T00:24:51.221Z| vmx| I125: GuestRpc: Closing channel 1 connection 280004

2019-03-11T03:11:43.674Z| vmx| I125: GuestRpc: Got RPCI vsocket connection 290003, assigned to channel 1.

2019-03-11T03:11:44.675Z| vmx| I125: GuestRpc: Got error for channel 1 connection 290004: Remote disconnected

2019-03-11T03:11:44.675Z| vmx| I125: GuestRpc: Closing channel 1 connection 290004

2019-03-11T05:58:39.366Z| vmx| I125: GuestRpc: Got RPCI vsocket connection 300003, assigned to channel 1.

2019-03-11T05:58:40.366Z| vmx| I125: GuestRpc: Got error for channel 1 connection 300004: Remote disconnected

2019-03-11T05:58:40.366Z| vmx| I125: GuestRpc: Closing channel 1 connection 300004

This problem occurs on several ESXi machines. The configuration is similiar.

Intel S2600 Board (with newest firmware)

LSI Megaraid Controller (with newest firmware)

Intel Xeon Processors

ESXi 6.7.0 Update 1 (Build 11675023)

Am I the only one having this problem? :-)

Any ideas?

Thanks in advance

Greets from Germany

Hey guys,

I just spent 4 hours trying to solve this problem and turns out it's a bug so I thought i'd share it here

Steps to reproduce:

1 - create a VM and setup its dvd player to use an ISO file in a datastore as boot device for installing

2 - after install is done the dvd player is automatically disconnected from the connected devices to avoid booting on it again.

3 - delete the ISO file in the datastore or through SSH.

4 - try to export the VM through any mean: web client, ovftools, anything... All fails, especially the web client which just shows a progress bar with no errors.

When you check the logs, you find this in hostd.log:

2020-01-25T22:46:28.314Z info hostd[2098582] [Originator@6876 sub=Solo.Vmomi opID=esxui-2b6c-039b user=root] Activation [N5Vmomi10ActivationE:0x00000063e4b18730] : Invoke done [exportVm] on [vim.VirtualMachine:6]

2020-01-25T22:46:28.314Z info hostd[2098582] [Originator@6876 sub=Solo.Vmomi opID=esxui-2b6c-039b user=root] Throw vim.fault.FileNotFound

2020-01-25T22:46:28.314Z info hostd[2098582] [Originator@6876 sub=Solo.Vmomi opID=esxui-2b6c-039b user=root] Result:

--> (vim.fault.FileNotFound) {

-->    faultCause = (vmodl.MethodFault) null,

-->    faultMessage = <unset>,

-->    file = "/vmfs/volumes/5e2335a6-78aef506-d442-28f10e01eeaf/ISO/debian-10.2.0-amd64-DVD-1.iso"

So even when the dvd player of a VM is disconnected if it was previously set to an ISO file which has been later removed from a datastore it prevents any regular VM export command through any mean and without clear error message.

This shouldn't provoke a blocking to export a VM, and if it does the corresponding action should display "failed because of missing ISO file..." and not just show an infinite progress bar with no errors.

Thanks for your time

Struggling to get VLANs to work.

I have a couple of different LAB environments I want to set up on a singlw ESXi server.

I have set up the following:

Assigned uplinks 1,2,3 for use for LABS

Here are the physical NICs:

I then setup a Port Group as follows:

On the Ubiquiti Controller I have set the following Network up for VLAN 4:

When I assign port group LAB - ALPINE to the VM there is no network connection at all and no suggestion VLAN ID is being used. I can set a static IP of 10.0.0.1/24 but the VM is not physically bound to this network.

vmnic1, vmnic2, vmnic3 are plugged in to a 24 Port switch with the 3 ports aggregated but not assigned to any particular network.

Any help on what to do here. I've used pfsense in the past to achieve something similar however would rather not use pfsense this time unless I need to.

I have the following outputs:

[root@localhost:~] esxcli software vib list | grep INT

igbn                           1.4.10-1OEM.670.0.0.8169922           INT     VMwareCertified   2020-01-26

[root@localhost:~]

[root@localhost:~] lspci -v | grep -A1 -i ethernet

0000:00:19.0 Network controller Ethernet controller: Intel Corporation 82579V Gigabit Network Connection [vmnic0]

     Class 0200: 8086:1503

[root@localhost:~]

I cannot get my 4 port nic to work even though it is on the approved HW list. I input the driver and rebooted with:

[root@localhost:/vmfs/volumes/5e2cf5a1-b40da3ec-4195-888888888788/NIC_Drivers] esxcli software vib install -v /v

mfs/volumes/5e2cf5a1-b40da3ec-4195-888888888788/NIC_Drivers/INT_bootbank_igbn_1.4.10-1OEM.670.0.0.8169922.vib

Installation Result

   Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.

   Reboot Required: true

   VIBs Installed: INT_bootbank_igbn_1.4.10-1OEM.670.0.0.8169922

   VIBs Removed: VMW_bootbank_igbn_0.1.1.0-5vmw.670.3.73.14320388

   VIBs Skipped:

[root@localhost:/vmfs/volumes/5e2cf5a1-b40da3ec-4195-888888888788/NIC_Drivers] reboot

[root@localhost:/vmfs/volumes/5e2cf5a1-b40da3ec-4195-888888888788/NIC_Drivers]

Trying to get Cisco VIRL to have it's own port into my lab NW. This is my first weekend ever with esxi as I have normally used workstation player. I come from pure NW background FYI

Hi

I have faced new issue today .

My vm's OS is linux I did scp (copy a file between two linux vm) my speed transfer was too slow about 2MB/s but after a connect/disconnect network for that vm speed transfer improved and increase to 250MB/S

My network configure is LACP and my pnic is 10G

I cannot connect my VM to the network/ When I select device status : Connected.

It fails and gives an error

Failed to connect virtual device ethernet0

The nic is e1000