Your message dated Sun, 18 Dec 2016 22:27:49 +0100
with message-id <[email protected]>
and subject line Re: udev: broken vmware eth numbering with vmxnet3 devices
has caused the Debian Bug report #750413,
regarding udev: broken vmware eth numbering with vmxnet3 devices
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
750413: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750413
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: udev
Severity: important
Version: 175-7.2

Hi,

due to 75-persistent-net-generator.rules ignoring vmware ethernet
cards, eth device numbering is broken for vmxnet3 devices as the
PCI bus id is not sorted for them.

Depending on the type of your scsi/sas controller (yay!), the
pci bus ids of the vmxnet3 cards either start at 03:00.0 or
0b:00.0. Unfortunately the 4th (if starting with 0b:00.0)
or the 5th vmxnet3 network interface is assigned a pci id
smaller than the first interface... 

Looking at my vmxnet rules might make it easier to understand
the problem than trying to understand my explanation. Rules
are rolled out by puppet, depending on the pci id of the
scsi/sas controller (or if there is a vmxnet device with
/03:00.0/).

So with
03:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS1068 
PCI-X Fusion-MPT SAS (rev 01)

we have


    SUBSYSTEM=="net", ACTION=="add", KERNELS=="0000:0b:00.0" 
DRIVERS=="vmxnet3", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
    SUBSYSTEM=="net", ACTION=="add", KERNELS=="0000:13:00.0" 
DRIVERS=="vmxnet3", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
    SUBSYSTEM=="net", ACTION=="add", KERNELS=="0000:1b:00.0" 
DRIVERS=="vmxnet3", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"
    SUBSYSTEM=="net", ACTION=="add", KERNELS=="0000:04:00.0" 
DRIVERS=="vmxnet3", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3"
    SUBSYSTEM=="net", ACTION=="add", KERNELS=="0000:0c:00.0" 
DRIVERS=="vmxnet3", ATTR{type}=="1", KERNEL=="eth*", NAME="eth4"
    SUBSYSTEM=="net", ACTION=="add", KERNELS=="0000:14:00.0" 
DRIVERS=="vmxnet3", ATTR{type}=="1", KERNEL=="eth*", NAME="eth5"
    SUBSYSTEM=="net", ACTION=="add", KERNELS=="0000:1c:00.0" 
DRIVERS=="vmxnet3", ATTR{type}=="1", KERNEL=="eth*", NAME="eth6"
    SUBSYSTEM=="net", ACTION=="add", KERNELS=="0000:05:00.0" 
DRIVERS=="vmxnet3", ATTR{type}=="1", KERNEL=="eth*", NAME="eth7"

and if there is no sas controller on 03:00.0, we have

    SUBSYSTEM=="net", ACTION=="add", KERNELS=="0000:03:00.0" 
DRIVERS=="vmxnet3", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
    SUBSYSTEM=="net", ACTION=="add", KERNELS=="0000:0b:00.0" 
DRIVERS=="vmxnet3", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
    SUBSYSTEM=="net", ACTION=="add", KERNELS=="0000:13:00.0" 
DRIVERS=="vmxnet3", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"
    SUBSYSTEM=="net", ACTION=="add", KERNELS=="0000:1b:00.0" 
DRIVERS=="vmxnet3", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3"
    SUBSYSTEM=="net", ACTION=="add", KERNELS=="0000:04:00.0" 
DRIVERS=="vmxnet3", ATTR{type}=="1", KERNEL=="eth*", NAME="eth4"
    SUBSYSTEM=="net", ACTION=="add", KERNELS=="0000:0c:00.0" 
DRIVERS=="vmxnet3", ATTR{type}=="1", KERNEL=="eth*", NAME="eth5"
    SUBSYSTEM=="net", ACTION=="add", KERNELS=="0000:14:00.0" 
DRIVERS=="vmxnet3", ATTR{type}=="1", KERNEL=="eth*", NAME="eth6"
    SUBSYSTEM=="net", ACTION=="add", KERNELS=="0000:1c:00.0" 
DRIVERS=="vmxnet3", ATTR{type}=="1", KERNEL=="eth*", NAME="eth7"
    SUBSYSTEM=="net", ACTION=="add", KERNELS=="0000:05:00.0" 
DRIVERS=="vmxnet3", ATTR{type}=="1", KERNEL=="eth*", NAME="eth8"


That works as expected, assuming that there was
a puppet run after adding the first network interface.
Not that nice...



e1000 and the old vmxnet works as expected.

A fix would be nice..


thanks,

bernd


-- 
Mit freundlichen Grüßen


Bernd Zeimetz
Systems Engineer
Debian Developer

conova communications GmbH
Web    | http://www.conova.com/
E-Mail | [email protected]

Zentrale Salzburg
Karolingerstraße 36A
5020 Salzburg

Tel | +43 (0) 662 22 00 - 313
Fax | +43 (0) 662 22 00 - 209

Es gelten die Allgemeinen Geschäftsbedingungen der
conova communications GmbH, http://www.conova.com/de/agb/

Attachment: smime.p7s
Description: S/MIME cryptographic signature


--- End Message ---
--- Begin Message ---
Version: 220-7

On Tue, 3 Jun 2014 10:57:39 +0200 Bernd Zeimetz <[email protected]>
wrote:
> Package: udev
> Severity: important
> Version: 175-7.2
> 
> Hi,
> 
> due to 75-persistent-net-generator.rules ignoring vmware ethernet
> cards, eth device numbering is broken for vmxnet3 devices as the
> PCI bus id is not sorted for them.

The old, 75-persistent-net-generator.rules has been removed in 220-7,
making this bug report obsolete. So closing it for that version.

Regards,
Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to