NMNeto
Contributor
Contributor

Network card is removed without any user intervention

We are having a problem that the network adapter disappears from the virtual machine. When editing the settings of the machine the NIC is no longer in it.

When we look at the virtual center tasks and events there is no event indicating the removal of the network card. Below I am sending the log.

Oct 27 09:15:44.828: vcpu-0| GuestRpc: Channel 2, conflict: guest application toolbox-dnd tried to register, but it is still registered on channel 1

Oct 27 09:15:44.828: vcpu-0| GuestRpc: Channel 2 reinitialized.

Oct 27 09:15:44.828: vcpu-0| GuestRpc: Channel 2 reinitialized.

Oct 27 09:17:05.564: vcpu-0| TOOLS unified loop capability requested by 'toolbox-dnd'; now sending options via TCLO

Oct 27 09:17:06.159: vcpu-0| GuestRpc: Channel 2, conflict: guest application toolbox-dnd tried to register, but it is still registered on channel 1

Oct 27 09:17:06.160: vcpu-0| GuestRpc: Channel 2 reinitialized.

Oct 27 09:17:06.160: vcpu-0| GuestRpc: Channel 2 reinitialized.

Oct 27 09:17:12.939: vcpu-0| TOOLS unified loop capability requested by 'toolbox-dnd'; now sending options via TCLO

Oct 27 09:17:12.952: vcpu-0| GuestRpc: Channel 2, conflict: guest application toolbox-dnd tried to register, but it is still registered on channel 1

Oct 27 09:17:12.952: vcpu-0| GuestRpc: Channel 2 reinitialized.

Oct 27 09:17:12.952: vcpu-0| GuestRpc: Channel 2 reinitialized.

Oct 27 09:18:15.697: vcpu-0| TOOLS unified loop capability requested by 'toolbox-dnd'; now sending options via TCLO

Oct 27 09:18:15.731: vcpu-0| GuestRpc: Channel 2, conflict: guest application toolbox-dnd tried to register, but it is still registered on channel 1

Oct 27 09:18:15.731: vcpu-0| GuestRpc: Channel 2 reinitialized.

Oct 27 09:18:15.732: vcpu-0| GuestRpc: Channel 2 reinitialized.

Oct 27 09:19:27.023: vcpu-0| TOOLS unified loop capability requested by 'toolbox-dnd'; now sending options via TCLO

Oct 27 09:19:27.024: vcpu-0| GuestRpc: Channel 2, conflict: guest application toolbox-dnd tried to register, but it is still registered on channel 1

Oct 27 09:19:27.024: vcpu-0| GuestRpc: Channel 2 reinitialized.

Oct 27 09:19:27.024: vcpu-0| GuestRpc: Channel 2 reinitialized.

Oct 27 09:20:33.433: vcpu-0| CPT current = 0, requesting 1

Oct 27 09:20:33.433: vcpu-0| Sync monModules(1).

Oct 27 09:20:33.434: vcpu-0| E1000: Syncing with mode 1.

Oct 27 09:20:33.434: vcpu-0| Done Sync monModules(1).

Oct 27 09:20:33.434: vmx| CPT: monitor ACKing mode 1

Oct 27 09:20:33.434: vmx| Destroying virtual dev for scsi0:0 vscsi=8198

Oct 27 09:20:33.434: vmx| VMMon_VSCSIStopVports: No such target on adapter

Oct 27 09:20:33.514: vmx| DISKLIB-VMFS : "/vmfs/volumes/4aae5176-4f8b1d32-51a4-001d09fd4614/corp1101/corp1101-flat.vmdk" : closed.

Oct 27 09:20:33.514: vmx| CPT current = 1, requesting 2

Oct 27 09:20:33.514: vmx| CPT: monitor ACKing mode 2

Oct 27 09:20:33.522: vmx| VMXVmdb_LoadRawConfig: Loading raw config

Oct 27 09:20:33.533: vmx| CPT current = 2, requesting 6

Oct 27 09:20:33.533: vmx| Checkpoint_Unstun: vm stopped for 99795 us

Oct 27 09:20:33.533: vcpu-0| Sync monModules(6).

Oct 27 09:20:33.533: vcpu-0| LSI:Telling vmk to set async to 1(CONT_SYNC)

Oct 27 09:20:33.533: vcpu-0| E1000: Syncing with mode 6.

Oct 27 09:20:33.534: vcpu-0| Done Sync monModules(6).

Oct 27 09:20:33.534: vmx| CPT: monitor ACKing mode 6

Oct 27 09:20:33.667: vmx| DISK: OPEN scsi0:0 '/vmfs/volumes/4aae5176-4f8b1d32-51a4-001d09fd4614/corp1101/corp1101.vmdk' persistent R[]

Oct 27 09:20:33.719: vmx| DISKLIB-VMFS : "/vmfs/volumes/4aae5176-4f8b1d32-51a4-001d09fd4614/corp1101/corp1101-flat.vmdk" : open successful (10) size = 42949672960, hd = 196640. Type 3

Oct 27 09:20:33.719: vmx| DISKLIB-DSCPTR: Opened : "corp1101-flat.vmdk" (0xa)

Oct 27 09:20:33.719: vmx| DISKLIB-LINK : Opened '/vmfs/volumes/4aae5176-4f8b1d32-51a4-001d09fd4614/corp1101/corp1101.vmdk' (0xa): vmfs, 83886080 sectors / 40 GB.

Oct 27 09:20:33.719: vmx| DISKLIB-LIB : Opened "/vmfs/volumes/4aae5176-4f8b1d32-51a4-001d09fd4614/corp1101/corp1101.vmdk" (flags 0xa).

Oct 27 09:20:33.719: vmx| DISK: OPEN '/vmfs/volumes/4aae5176-4f8b1d32-51a4-001d09fd4614/corp1101/corp1101.vmdk' Geo (5221/255/63) BIOS Geo (0/0/0)

Oct 27 09:20:33.720: vmx| Creating virtual dev for scsi0:0

Oct 27 09:20:33.720: vmx| DumpDiskInfo: scsi0:0 createType=11, capacity = 83886080, numLinks = 1, allocationType = 1

Oct 27 09:20:33.721: vmx| SCSIDiskESXPopulateVDevDesc: Using FS backend

Oct 27 09:20:33.791: vmx| Powering off Ethernet0

Oct 27 09:20:33.792: vmx| Hot removal done.

0 Kudos
5 Replies
NMNeto
Contributor
Contributor

Anyone have an idea? the problem occurred again.
0 Kudos
NMNeto
Contributor
Contributor

We have solved this problem. Thanks all.

0 Kudos
jpdicicco
Hot Shot
Hot Shot

NMNeto,

Please post how you resolved this.

Thanks.

Happy virtualizing! JP Please consider awarding points to helpful or correct replies.
0 Kudos
NMNeto
Contributor
Contributor

The problem is not a in VMWARE ESX is in the hot plug technology of the network adapter this device (NIC) can be removed by the user like a usb drive. We are checking now how to prevent this in Windows. I am sending a print scren attached. When you click to remove de NIC the VMWare ESX remove this device from de virtual machine hardware.
0 Kudos
NMNeto
Contributor
Contributor

This thread resolve this problem.

http://communities.vmware.com/thread/227036

0 Kudos