VMware Cloud Community
Rennes
Contributor
Contributor
‎06-11-2009 09:48 AM

ESXi 4.0 : Ubuntu 8.04.2 LTS doesn't seem to recognize VMXNET 3 adapters (VMware tools installed)

Hello,

I'm using an ESXi 4.0 platform. I'm trying to use a VMXnet 3 adapter in an ubuntu 8.04.2 LTS.

According to this link Ubuntu should recognize VMXNET 3 adapters.

However, when I insert such an adapter, my ubuntu (VMware tools installed) doesnt recognize it. Did someone manage to use this type of adapter with ubuntu 8.04 LTS ?

Does anyone have an idea ?

Thanks,

Nicolas

0 Kudos
8 Replies
pthakkar
Contributor
Contributor
‎06-11-2009 11:31 AM

Can you post the output of lspci and relevant dmesg? You may want to reconfigure the tools to make sure you have the right kernel module for vmxnet3.

0 Kudos
Rennes
Contributor
Contributor
‎06-12-2009 12:34 AM

Hello,

Thanks for your answer !

Here is the output of lspci :

-

00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 01)



00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 01)



00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 08)



00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)



00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 08)



00:07.7 System peripheral: VMware Inc Virtual Machine Communication Interface (rev 10)



00:0f.0 VGA compatible controller: VMware Inc Abstract SVGA II Adapter



00:10.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 01)



00:11.0 PCI bridge: VMware Inc Unknown device 0790 (rev 02)



00:15.0 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)



00:15.1 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)



00:15.2 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)



00:15.3 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)



00:15.4 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)



00:15.5 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)



00:15.6 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)



00:15.7 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)



00:16.0 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)



00:16.1 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)



00:16.2 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)



00:16.3 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)



00:16.4 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)



00:16.5 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)



00:16.6 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)



00:16.7 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)



00:17.0 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)



00:17.1 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)



00:17.2 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)



00:17.3 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)



00:17.4 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)



00:17.5 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)



00:17.6 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)



00:17.7 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)



00:18.0 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)



00:18.1 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)



00:18.2 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)



00:18.3 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)



00:18.4 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)



00:18.5 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)



00:18.6 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)



00:18.7 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)



02:01.0 Memory controller: VMware Inc Virtual Machine Interface (rev 01)



03:00.0 Ethernet controller: VMware Inc Unknown device 07b0 (rev 01)

-

And here is the output of dmesg :

-

[http://...|http://...]

[http://831846.342979|http://831846.342979] VMware vmxnet virtual NIC driver
[http://831846.350794|http://831846.350794] fuse init (API version 7.9)
[http://831846.365888|http://831846.365888] ACPI: Processor [CPU0] (supports 8 throttling states)
[http://831846.599923|http://831846.599923] SCSI subsystem initialized
[http://831846.621701|http://831846.621701] libata version 3.00 loaded.
[http://831846.625199|http://831846.625199] Fusion MPT base driver 3.04.06
[http://831846.625201|http://831846.625201] Copyright (c) 1999-2007 LSI Corporation
[http://831846.634605|http://831846.634605] Fusion MPT SPI Host driver 3.04.06
[http://831846.634761|http://831846.634761] ACPI: PCI Interrupt 0000:00:10.0[A] -> GSI 17 (level, low) -> IRQ 16
[http://831846.634883|http://831846.634883] mptbase: ioc0: Initiating bringup
[http://831846.704129|http://831846.704129] ioc0: LSI53C1030 B0: Capabilities={Initiator}
[http://831846.806528|http://831846.806528] Floppy drive(s): fd0 is 1.44M
[http://831846.820258|http://831846.820258] FDC 0 is a post-1991 82077
[http://831846.833305|http://831846.833305] scsi0 : ioc0: LSI53C1030 B0, FwRev=01032920h, Ports=1, MaxQ=128, IRQ=16
[http://831846.943154|http://831846.943154] scsi 0:0:0:0: Direct-Access     VMware   Virtual disk     1.0  PQ: 0 ANSI: 2
[http://831846.943185|http://831846.943185]  target0:0:0: Beginning Domain Validation
[http://831846.944379|http://831846.944379]  target0:0:0: Domain Validation skipping write tests
[http://831846.944382|http://831846.944382]  target0:0:0: Ending Domain Validation
[http://831846.944455|http://831846.944455]  target0:0:0: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 127)
[http://831846.949489|http://831846.949489] ata_piix 0000:00:07.1: version 2.12
[http://831846.950342|http://831846.950342] scsi1 : ata_piix
[http://831846.951016|http://831846.951016] scsi2 : ata_piix
[http://831846.951048|http://831846.951048] ata1: PATA max UDMA/33 cmd 0x1f0 ctl 0x3f6 bmdma 0x10c0 irq 14
[http://831846.951050|http://831846.951050] ata2: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0x10c8 irq 15
[http://831847.204598|http://831847.204598] Driver 'sd' needs updating - please use bus_type methods
[http://831847.204784|http://831847.204784] sd 0:0:0:0: [sda] 1048576000 512-byte hardware sectors (536871 MB)
[http://831847.204963|http://831847.204963] sd 0:0:0:0: [sda] Test WP failed, assume Write Enabled
[http://831847.205022|http://831847.205022] sd 0:0:0:0: [sda] Cache data unavailable
[http://831847.205024|http://831847.205024] sd 0:0:0:0: [sda] Assuming drive cache: write through
[http://831847.205773|http://831847.205773] sd 0:0:0:0: [sda] 1048576000 512-byte hardware sectors (536871 MB)
[http://831847.205946|http://831847.205946] sd 0:0:0:0: [sda] Test WP failed, assume Write Enabled
[http://831847.206004|http://831847.206004] sd 0:0:0:0: [sda] Cache data unavailable
[http://831847.206006|http://831847.206006] sd 0:0:0:0: [sda] Assuming drive cache: write through
[http://831847.206935|http://831847.206935]  sda: sda1 sda2 < sda5 sda6 sda7 sda8 sda9 sda10 >
[http://831847.255695|http://831847.255695] sd 0:0:0:0: [sda] Attached SCSI disk
[http://831847.259617|http://831847.259617] sd 0:0:0:0: Attached scsi generic sg0 type 0
[http://831847.286443|http://831847.286443] ata1.00: ATAPI: VMware Virtual IDE CDROM Drive, 00000001, max UDMA/33
[http://831847.441959|http://831847.441959] ata1.00: configured for UDMA/33
[http://831847.442198|http://831847.442198] ata2: port disabled. ignoring.
[http://831847.442535|http://831847.442535] scsi 1:0:0:0: CD-ROM            NECVMWar VMware IDE CDR00 1.00 PQ: 0 ANSI: 5
[http://831847.442592|http://831847.442592] scsi 1:0:0:0: Attached scsi generic sg1 type 5
[http://831847.451810|http://831847.451810] Driver 'sr' needs updating - please use bus_type methods
[http://831847.454368|http://831847.454368] sr0: scsi3-mmc drive: 1x/1x xa/form2 cdda tray
[http://831847.454371|http://831847.454371] Uniform CD-ROM driver Revision: 3.20
[http://831847.454403|http://831847.454403] sr 1:0:0:0: Attached scsi CD-ROM sr0
[http://831847.622895|http://831847.622895] Attempting manual resume
[http://831847.622901|http://831847.622901] swsusp: Resume From Partition 8:10
[http://831847.622902|http://831847.622902] PM: Checking swsusp image.
[http://831847.623099|http://831847.623099] PM: Resume from disk failed.
[http://831847.636421|http://831847.636421] kjournald starting.  Commit interval 5 seconds
[http://831847.636430|http://831847.636430] EXT3-fs: mounted filesystem with ordered data mode.
[http://831849.748002|http://831849.748002] Linux agpgart interface v0.102
[http://831849.816375|http://831849.816375] agpgart: Detected an Intel 440BX Chipset.
[http://831849.817593|http://831849.817593] agpgart: AGP aperture is 256M @ 0x0
[http://831849.830609|http://831849.830609] input: Power Button (FF) as /devices/virtual/input/input1
[http://831849.840197|http://831849.840197] ACPI: Power Button (FF) [PWRF]
[http://831849.840298|http://831849.840298] input: Sleep Button (CM) as /devices/virtual/input/input2
[http://831849.855552|http://831849.855552] piix4_smbus 0000:00:07.3: Found 0000:00:07.3 device
[http://831849.855613|http://831849.855613] piix4_smbus 0000:00:07.3: Host SMBus controller not enabled!
[http://831849.857747|http://831849.857747] ACPI: Sleep Button (CM) [SLPB]
[http://831849.858203|http://831849.858203] ACPI: AC Adapter [ACAD] (on-line)
[http://831850.519852|http://831850.519852] input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input3
[http://831850.520618|http://831850.520618] input: PC Speaker as /devices/platform/pcspkr/input/input4
[http://831850.558785|http://831850.558785] parport_pc 00:08: reported by Plug and Play ACPI
[http://831850.558912|http://831850.558912] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
[http://831852.643399|http://831852.643399] loop: module loaded
[http://831852.650508|http://831852.650508] lp0: using parport0 (interrupt-driven).
[http://831852.787574|http://831852.787574] Adding 987956k swap on /dev/sda10.  Priority:-1 extents:1 across:987956k
[http://831852.900944|http://831852.900944] EXT3 FS on sda5, internal journal
[http://831853.593759|http://831853.593759] kjournald starting.  Commit interval 5 seconds
[http://831853.593922|http://831853.593922] EXT3 FS on sda1, internal journal
[http://831853.593926|http://831853.593926] EXT3-fs: mounted filesystem with ordered data mode.
[http://831853.595094|http://831853.595094] kjournald starting.  Commit interval 5 seconds
[http://831853.595247|http://831853.595247] EXT3 FS on sda9, internal journal
[http://831853.595251|http://831853.595251] EXT3-fs: mounted filesystem with ordered data mode.
[http://831853.596291|http://831853.596291] kjournald starting.  Commit interval 5 seconds
[http://831853.596442|http://831853.596442] EXT3 FS on sda7, internal journal
[http://831853.596445|http://831853.596445] EXT3-fs: mounted filesystem with ordered data mode.
[http://831853.597260|http://831853.597260] kjournald starting.  Commit interval 5 seconds
[http://831853.597393|http://831853.597393] EXT3 FS on sda6, internal journal
[http://831853.597396|http://831853.597396] EXT3-fs: mounted filesystem with ordered data mode.
[http://831853.602980|http://831853.602980] kjournald starting.  Commit interval 5 seconds
[http://831853.610140|http://831853.610140] EXT3 FS on sda8, internal journal
[http://831853.610144|http://831853.610144] EXT3-fs: mounted filesystem with ordered data mode.
[http://831854.119283|http://831854.119283] ip_tables: (C) 2000-2006 Netfilter Core Team
[http://831855.374236|http://831855.374236] NET: Registered protocol family 17
[http://831856.867123|http://831856.867123] NET: Registered protocol family 10
[http://831856.867304|http://831856.867304] lo: Disabled Privacy Extensions
[http://831859.274586|http://831859.274586] VMware memory control driver initialized
[http://831859.274600|http://831859.274600] vmmemctl: started kernel thread pid=4372

0 Kudos
Texiwill
Leadership
Leadership
‎06-17-2009 05:30 AM

Hello,

Moved to the Virtual Machine and Guest OS forum.


Best regards, Edward L. Haletky VMware Communities User Moderator, VMware vExpert 2009
Now Available on Rough-Cuts: 'VMware vSphere(TM) and Virtual Infrastructure Security: Securing ESX and the Virtual Environment'[/url]
Also available 'VMWare ESX Server in the Enterprise'[/url]
[url=http://www.astroarch.com/wiki/index.php/Blog_Roll]SearchVMware Pro[/url]|Blue Gears[/url]|Top Virtualization Security Links[/url]|Virtualization Security Round Table Podcast[/url]

--
Edward L. Haletky
vExpert XIV: 2009-2023,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill
0 Kudos
pthakkar
Contributor
Contributor
‎06-17-2009 02:57 PM

Sorry for the delay in response I got sidetracked.

From lspci you can see that the device is visible.

From the dmesg it seems the driver is not loading "VMware vmxnet virtual NIC driver" corresponds to vmxnet2 driver IIRC. vmxnet3 driver would print vmxnet3 virtual NIC driver. Can you try loading the driver manually by doing a modprobe vmxnet3 and see if that helps?

Rennes
Contributor
Contributor
‎06-23-2009 08:14 AM

Hello,

Sorry for the delay,

Thanks for the info.

I tried that, and it did not work either.

0 Kudos
Rennes
Contributor
Contributor
‎06-23-2009 10:06 AM

I solved the problem Smiley Happy :

The new adapters were assigned eth1, eth2... numbers in /etc/udev/rules.d/70-persistent-net.rules

I just had to clean the file, keeping only the lines referring vmxnet3 and changing the name to eth0.

Now it works.

Thanks everybody for your help.

0 Kudos
LucasAlbers
Expert
Expert
‎09-16-2009 02:38 PM

What exactly did you change for it to detect the vmxnet3 network card?

You edited the rules file or renamed a different resulting file?

0 Kudos
Rennes
Contributor
Contributor
‎09-16-2009 11:42 PM

Hello,

I modified the file.

0 Kudos